← Back to Dashboard
277
Pages Scanned
112
Pages Flagged
277
Changed Pages
40.4%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06 Scan started

Scan Information

Started At: 2026-02-27 00:00:06

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

112 issues found
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 page for Azure Service Fabric reverse proxy clearly states that the reverse proxy is not available for Linux clusters, and all examples and configuration guidance are implicitly Windows-centric. There are no Linux-specific instructions or parity examples, and the guidance for containers and developer environments references Windows-only features and links.
Recommendations
  • Clarify early in the document that reverse proxy is Windows-only, and provide alternative guidance or links for Linux clusters if possible.
  • Add a prominent note or section for Linux users explaining the lack of reverse proxy support and suggesting supported communication patterns or alternatives.
  • Where container usage is discussed, explicitly state Windows container requirements and mention that Linux containers are not supported with reverse proxy.
  • Update 'Next steps' to include Linux-specific resources or a statement about the absence of reverse proxy support for Linux clusters.
GitHub Create Pull Request
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows-specific images (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows shell commands (cmd, type, ping -t). There are no Linux container examples, and the only scenario described is for Windows containers. The text and examples assume a Windows environment throughout.
Recommendations
  • Add parallel examples for Linux containers, using Linux-compatible images (e.g., mcr.microsoft.com/ubuntu or other Linux base images), Linux file paths (/workspace/log.txt), and shell commands (sh, cat, tail, etc.).
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance and examples for Linux scenarios.
  • If Initializer CodePackages are not supported for Linux containers, explicitly state this limitation at the top of the article to avoid confusion for non-Windows users.
  • When providing examples, either alternate between Windows and Linux or present both side-by-side to ensure parity.
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
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation page exclusively describes Windows Server as a supported operating system for standalone clusters. All security and configuration guidance is Windows-centric, with no Linux-specific instructions, examples, or mention of Linux tools or patterns. The 'Supported operating systems' section explicitly states that Linux isn't yet supported, contradicting the initial claim.
Recommendations
  • Clarify the Linux support status at the top of the page to avoid confusion.
  • Remove or revise the description to accurately reflect current Linux support for standalone clusters.
  • Add Linux-specific guidance, examples, and supported OS information if/when Linux support becomes available.
  • If Linux support is planned, provide a roadmap or links to relevant Linux documentation.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. Although there are references to Linux custom image creation and Azure CLI usage, the main focus and examples are Windows-centric, and the PowerShell command for role assignment is given without a Linux/CLI equivalent.
Recommendations
  • Provide Azure CLI examples for role assignments alongside PowerShell.
  • Clarify if Linux VM images are supported for Service Fabric Managed Clusters and, if so, include Linux-specific guidance and examples.
  • Balance the order and prominence of Windows and Linux instructions, ensuring Linux users can easily follow the process.
  • Explicitly state any platform limitations (e.g., if only Windows node types are supported) to avoid confusion.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for managing Service Fabric resources, and provides PowerShell examples and links before mentioning or providing Azure CLI equivalents. While Azure CLI is referenced for deleting applications, PowerShell is emphasized for most operations, and no explicit Linux/macOS-friendly examples or guidance are given.
Recommendations
  • Include Azure CLI examples for all operations, not just application deletion, to ensure parity for Linux/macOS users.
  • Mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Where PowerShell is referenced, clarify if the cmdlet is available in Azure Cloud Shell (which supports Linux/macOS) or if there are CLI alternatives.
  • Add explicit notes or examples for Linux/macOS users to avoid confusion.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner overall, but the Management subsystem section specifically mentions 'PowerShell cmdlets' as the primary tooling for provisioning, deploying, patching, upgrading, and de-provisioning applications. No equivalent Linux/macOS tooling (such as CLI commands, REST APIs, or Bash scripts) is mentioned. Additionally, Windows security is referenced as an option for securing communication, but Linux alternatives are not discussed.
Recommendations
  • Mention cross-platform management tools such as Azure CLI, REST APIs, or Bash scripts alongside PowerShell cmdlets.
  • Clarify whether the management subsystem can be accessed and managed from Linux/macOS environments, and provide examples or references.
  • When referencing security mechanisms, note Linux-compatible options (e.g., X509 certificates, Kerberos, etc.) where applicable.
  • Ensure that examples and tooling references are platform-neutral or include both Windows and Linux/macOS options.
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 examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, DSC) are often mentioned first or exclusively, and Windows-centric guidance (e.g., security baselines, Defender exclusions) is more detailed. Linux equivalents are present for encryption but less emphasized overall, and some sections (Windows Defender, DSC) are Windows-only without Linux alternatives or parity notes.
Recommendations
  • Ensure Linux examples are given equal prominence and detail, especially in sections where Windows examples are shown first.
  • Add Linux security baseline recommendations (e.g., CIS benchmarks, OS-specific hardening guides) alongside Windows baselines.
  • For Windows Defender/DSC sections, explicitly mention Linux alternatives (e.g., ClamAV, auditd, Ansible/Chef/Puppet for configuration management) or clarify if no direct equivalent exists.
  • Where Windows tools (PowerShell, DSC) are referenced, provide Linux command-line or scripting alternatives (bash, Python, etc.) where possible.
  • Consider a summary table contrasting Windows and Linux approaches for common security tasks in Service Fabric clusters.
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. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI (such as Azure CLI or REST API) examples are provided. PowerShell examples are consistently shown alongside C# code, with no mention of 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 examples for each placement policy, as Azure CLI is cross-platform and widely used.
  • Mention REST API options for configuring placement policies, with example requests.
  • Clarify whether PowerShell examples are only applicable to Windows clusters, and provide guidance for Linux-based clusters.
  • Consider referencing Service Fabric CLI (sfctl), which is cross-platform, if applicable.
  • Ensure that documentation sections do not assume PowerShell as the default tool for all users.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any mention of Azure CLI equivalents or Linux/macOS-friendly workflows. Application packaging is described via Visual Studio, a Windows-centric tool, and no alternative methods (e.g., dotnet CLI or cross-platform tools) are provided. The examples and screenshots consistently reference Windows paths and tools, with no Linux/macOS parity.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks (e.g., az deployment group create, az resource delete).
  • Provide instructions for packaging applications using cross-platform tools such as the dotnet CLI or Service Fabric SDK commands, rather than relying solely on Visual Studio.
  • Include Linux/macOS file path examples and clarify that the procedures are applicable across platforms.
  • Mention that PowerShell Core is available on Linux/macOS, but highlight Azure CLI as the preferred cross-platform tool.
  • Add a note or section for Linux/macOS users outlining any differences or additional requirements.
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 page primarily references PowerShell for deployment/removal tasks and links to PowerShell-specific resources. There is an implicit assumption of Windows usage, as seen in the 'Next steps' section and the linked example for downloading a ServicePackage in advance, which points to a PowerShell module. No Linux or cross-platform CLI examples or references are provided, and Linux tooling is not mentioned.
Recommendations
  • Add equivalent Linux/bash examples for deployment and removal tasks, using Azure CLI or Service Fabric CLI where available.
  • Include links to Linux/macOS documentation or tools for Service Fabric operations.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Mention any limitations or differences for Linux nodes in Service Fabric clusters, if applicable.
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 on 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/macOS examples or mentions of equivalent tooling or patterns for non-Windows Service Fabric clusters, and Windows-specific tools are discussed first and most prominently.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including references to Linux-compatible logging mechanisms (e.g., stdout/stderr, syslog, Azure Monitor integration for Linux).
  • Provide examples or links for configuring diagnostics and event collection on Linux-based Service Fabric clusters.
  • Mention cross-platform tools and APIs (such as EventStore REST APIs) earlier and more prominently to emphasize parity.
  • Clarify which event access methods are Windows-only and which are cross-platform, to help users understand applicability.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux coverage in the CLI and API sections, but exhibits some Windows bias in several areas: PowerShell is given equal prominence to the cross-platform Azure CLI, ARM template examples default to Windows images, and some parameter descriptions and allowed values are Windows-specific. Linux-specific examples (e.g., ARM template for Linux VMs) are missing, and Windows terminology and tools are often mentioned first or exclusively.
Recommendations
  • Add explicit Linux VM examples in ARM template sections (e.g., provide an 'imageReference' for a popular Linux distribution such as Ubuntu).
  • In ARM template parameters, include allowedValues and descriptions for common Linux images alongside Windows ones.
  • When showing tabbed examples, alternate the order or clarify that both Windows and Linux are supported, and provide Linux-specific notes where relevant.
  • Where PowerShell is used, clarify that it is primarily for Windows users, and highlight cross-platform alternatives (Azure CLI, REST API) for Linux/macOS users.
  • Review parameter descriptions and default values to ensure Linux parity (e.g., adminPassword vs. SSH keys, port 3389 vs. 22).
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI examples use Windows VM images (e.g., 'Win2016Datacenter') and do not show Linux VM deployment or disk attachment. PowerShell examples are inherently Windows-centric. There are no explicit Linux VM examples, nor are Linux-specific considerations or commands provided. The portal instructions are generic, but the scripting sections are Windows-focused.
Recommendations
  • Add Azure CLI examples that deploy and attach Premium SSD v2 disks to Linux VMs (e.g., using 'UbuntuLTS' or other Linux images).
  • Include Linux-specific notes or considerations, such as disk formatting or mounting steps for Linux VMs.
  • Ensure variable names and instructions are not Windows-centric (e.g., avoid only referencing Windows images or admin credentials).
  • Provide parity in scripting examples for both Linux and Windows VM scenarios.
GitHub Create Pull Request
Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.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 PowerShell and Azure CLI examples for creating encrypted image versions, but the PowerShell section is presented first and is more detailed, including additional VM creation steps and parameter explanations. The CLI section is present and functional, but less verbose. There is a reference to Windows cryptographic modules (CNG) in the introduction, but the overall feature is cross-platform. No Linux-specific examples or shell scripts are provided, and PowerShell is emphasized, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Expand CLI examples to match the detail and completeness of the PowerShell section, including VM creation steps and parameter explanations.
  • Add Bash shell scripting examples for common tasks, especially for Linux users.
  • Clarify that PowerShell examples are cross-platform (if true), or note any limitations for Linux/macOS users.
  • Where possible, avoid referencing Windows-specific cryptographic APIs unless they are relevant to Linux users.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.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 extensive Azure PowerShell examples and scripts, with detailed walkthroughs for enabling Write Accelerator using PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced for installing armclient, and installation instructions are Windows-centric. While Azure CLI and REST API methods are covered, PowerShell is presented first and in greater detail. Linux is mentioned as supported, but Linux-native installation methods and shell examples are missing.
Recommendations
  • Add Linux/macOS instructions for installing armclient (e.g., via Homebrew or manual download), including bash/zsh shell commands.
  • Provide examples using bash or Azure CLI for common tasks, and ensure parity with PowerShell scripts.
  • Reorder sections so Azure CLI examples appear before or alongside PowerShell, or clearly state both are equally supported.
  • Explicitly mention cross-platform compatibility for all tools and commands, and highlight any OS-specific limitations.
  • Include troubleshooting or configuration notes for Linux users (e.g., permissions, disk manager integration).
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker or Corosync), nor are Linux-specific limitations or guidance provided. Windows clustering is mentioned as a limitation for all disk types, and the proximity placement group link is Windows-specific. This creates a Windows-first impression and omits Linux parity.
Recommendations
  • Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
  • Include links to relevant Linux documentation or guidance for configuring shared disks in Linux clusters.
  • Clarify whether the 'basic disks' limitation applies to Linux clusters, or if there are different requirements.
  • Provide parity in proximity placement group documentation for Linux VMs, or clarify if this feature is Windows-only.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.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 a Windows-centric example for uploading a VHD using AzCopy.exe, referencing a Windows file path and executable, but does not offer a Linux/macOS equivalent. The AzCopy upload command is shown only for Windows, and the CLI script for copying disks uses Bash syntax, which is Linux-friendly, but the initial upload example is Windows-first and lacks parity for Linux/macOS users.
Recommendations
  • Add a Linux/macOS AzCopy example, using the appropriate executable (e.g., ./azcopy or azcopy) and a Unix-style file path (e.g., /home/user/mydisk.vhd).
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Where possible, show both Windows and Linux/macOS commands side-by-side, or note differences in syntax and paths.
  • Explicitly mention that the Bash script for copying disks is suitable for Linux/macOS environments, and provide a PowerShell equivalent for Windows users if desired.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VMs and provides extensive Azure CLI examples, but PowerShell examples are also heavily featured. Several PowerShell commands and notes reference Windows-specific tools and patterns (e.g., 'New-AzStorageBlobSASToken', 'ipconfig', 'myscript.ps1'), and in some cases, Windows terminology or instructions are presented before or alongside Linux equivalents. REST API and ARM template examples sometimes use Windows-style scripts (PowerShell) or refer to '.ps1' files, even in Linux contexts.
Recommendations
  • Ensure all script examples in REST API and ARM template sections use Linux shell scripts (e.g., '.sh') instead of PowerShell scripts ('.ps1') when targeting Linux VMs.
  • Clarify when PowerShell commands are applicable to Linux VMs, and avoid referencing Windows-specific tools or patterns unless necessary.
  • Provide Linux-specific instructions and examples before or alongside any Windows-related notes, especially in sections about parameters, script URIs, and command IDs.
  • Review notes and examples for unnecessary references to Windows tools (e.g., 'ipconfig' instead of 'ifconfig', 'myscript.ps1' instead of 'myscript.sh').
  • Where PowerShell is used, explicitly state its cross-platform support or recommend Azure CLI for Linux users.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.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 Linux and Windows coverage for Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell examples and references to Windows tools (such as Get-FileHash, Invoke-AzResourceAction, and Sysprep) are frequently given, sometimes before or instead of Linux equivalents. In some sections, Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less emphasized or missing (e.g., no Linux restart customizer). SHA256 checksum generation is shown with PowerShell first, and troubleshooting links often reference Windows-centric solutions. However, Linux support is present and described, and Linux examples are included, especially for shell customizers and validations.
Recommendations
  • Ensure Linux and macOS examples are always provided alongside Windows/PowerShell examples, especially for checksum generation, image build/cancel commands, and troubleshooting.
  • Present Linux (shell/bash) and Windows (PowerShell) examples in parallel, rather than Windows first.
  • Add Linux-specific troubleshooting guidance and links where only Windows solutions are referenced.
  • Clarify limitations (such as lack of Linux restart customizer) and suggest Linux workarounds (e.g., using shell scripts for reboot).
  • Where PowerShell tools are referenced (e.g., Get-FileHash), provide equivalent Linux/macOS commands (e.g., sha256sum) with equal prominence.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ minor_missing_linux_example
Summary
The documentation covers both Linux and Windows VMs for Azure backup and disaster recovery, but there are several instances where Windows tools and patterns (such as PowerShell, Volume Shadow Service, and Windows-specific backup mechanisms) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. PowerShell is frequently cited for automation and recovery, while Linux CLI or scripting options are less detailed. Some links and examples (e.g., incremental snapshots) point to Windows-specific pages, and Linux-specific instructions are sometimes relegated to 'see also' or 'for Linux, see...' notes.
Recommendations
  • Ensure Linux CLI (Azure CLI, Bash, etc.) examples are given equal prominence to PowerShell throughout the document, especially in automation and recovery sections.
  • When referencing tools like Volume Shadow Service for Windows, provide parallel explanations and examples for Linux (e.g., fsfreeze, application-consistent backup methods) directly in the main text, not just as links.
  • Where links point to Windows-specific guides (e.g., incremental snapshots), ensure Linux equivalents are linked with equal visibility.
  • Add explicit Linux scripting examples for snapshot management, backup, and restore, not just references to Azure CLI.
  • Review tables and summary sections to ensure Linux and Windows parity in tool recommendations and workflow descriptions.
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 ⚠ī¸ powershell_heavy
Summary
The documentation provides a thorough conceptual overview of X.509 certificate-based authentication in Service Fabric clusters, with configuration examples in XML. However, there is a notable Windows bias in troubleshooting and tool references: Windows certificate store paths ('LocalMachine\My') are mentioned first and most often, Windows event log channels are referenced for troubleshooting, and Windows-specific tools (CAPI2 logging, Win32 CryptoAPI) are discussed in detail. Linux equivalents are mentioned briefly (e.g., '*var/lib/sfcerts*'), but not explained or exemplified. No Linux-specific troubleshooting guidance or tool references are provided.
Recommendations
  • Add explicit Linux certificate store paths and explain how Service Fabric nodes on Linux locate and load certificates.
  • Provide Linux-specific troubleshooting steps, including relevant log file locations and commands (e.g., journalctl, syslog, Service Fabric logs).
  • Reference Linux tools for certificate validation and troubleshooting (e.g., openssl, certtool, systemd logs) alongside Windows tools.
  • Include examples of cluster manifest configuration and certificate management for Linux environments.
  • Clarify any differences in certificate handling or error codes between Windows and Linux nodes.
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_tools ⚠ī¸ windows_first
Summary
The documentation page 'Manage certificates in a Service Fabric cluster' demonstrates a moderate Windows bias. PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is discussed exclusively in the context of Windows. The extension's schema and behaviors are described as Windows-specific, and there is no mention of Linux equivalents or cross-platform alternatives for certificate provisioning or automation. Windows tools and patterns (such as S-channel and certificate linking) are explained in detail, while Linux-specific mechanisms (e.g., Azure Key Vault extension for Linux, certificate handling on Linux nodes) are absent. Additionally, Windows-centric terminology and examples appear first and dominate the technical walkthroughs.
Recommendations
  • Add Linux-specific examples for certificate provisioning and automation, such as using Azure CLI or Bash scripts instead of only PowerShell.
  • Document the Key Vault VM extension for Linux, or clarify its availability and limitations for Linux VM/VMSS nodes.
  • Provide guidance for managing certificates in Service Fabric clusters running on Linux, including certificate store locations and access control.
  • Explicitly state which features or steps are Windows-only, and offer alternatives or workarounds for Linux/macOS users.
  • Include cross-platform sample templates and scripts, or link to relevant Linux documentation.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. While ARM templates and Portal are cross-platform, all CLI/scripted examples are exclusively in PowerShell, with no mention of Azure CLI (az) or Bash equivalents. This creates friction for Linux/macOS users who do not have native access to PowerShell or prefer Bash/Azure CLI. There is also an implicit bias toward Windows tooling by only referencing PowerShell for automation and scripting.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all supported operations (add, remove, scale, configure properties, etc.).
  • Explicitly state if certain operations are only possible with PowerShell, and provide guidance for Linux/macOS users (e.g., using Azure Cloud Shell or cross-platform PowerShell).
  • Where possible, provide Bash script snippets or note ARM template usage as the recommended cross-platform automation method.
  • Clarify in each section which tools are supported on which platforms, to help users choose the best approach for their OS.
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-based APIs and modules referenced before Azure CLI or other cross-platform tools. While Azure CLI and ARM/Bicep are mentioned, the explicit examples and links for critical operations (delete, restart, reimage) are PowerShell-centric, potentially creating friction for Linux/macOS users who prefer CLI or scripting alternatives.
Recommendations
  • Add explicit Azure CLI examples and links for NodeType deletion, VMSS restart, and reimage operations, alongside PowerShell examples.
  • Ensure that CLI and PowerShell guidance are presented equally, ideally with CLI examples shown first or in parallel, since CLI is cross-platform.
  • Clarify that Azure PowerShell is available on Linux/macOS, but highlight CLI as the default for cross-platform scenarios.
  • Consider including sample ARM/Bicep template snippets for common operations, not just linking to general ARM documentation.
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 command example for bypassing the Infrastructure Service, without offering a Linux/macOS equivalent or clarifying cross-platform support. Service Fabric Explorer is mentioned, but no CLI or Linux-native tools are referenced. The PowerShell example is presented as the only way to perform the operation, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Clarify whether the PowerShell command is supported on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
  • Provide equivalent instructions or commands for Linux/macOS users, such as using Azure CLI, REST API, or PowerShell Core if available.
  • Mention cross-platform management tools and their usage for the described operations.
  • Explicitly state platform limitations if the operation is Windows-only, to avoid confusion.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.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 provides migration guidance for Azure Service Fabric clusters to availability zone support. While much of the guidance is platform-neutral (focused on Azure Resource Manager templates and JSON), the migration steps for nonmanaged clusters with Basic SKU load balancer and IP resources rely heavily on PowerShell scripts and Windows-specific tooling. PowerShell is used exclusively for cluster management, node disabling/removal, and DNS updates, with no equivalent Bash, Azure CLI, or cross-platform examples. Additionally, sample templates and examples often reference Windows VM configurations before mentioning Linux equivalents, and the only explicit Linux sample is linked but not demonstrated in the migration steps.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell migration steps, especially for cluster management, node disabling/removal, and DNS updates.
  • Explicitly mention and demonstrate Linux VM migration scenarios alongside Windows examples, not just as a linked template.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
  • Add guidance for macOS/Linux users on how to perform Service Fabric cluster operations without PowerShell (e.g., using Azure CLI or REST APIs).
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd.exe). It also provides PowerShell as the only CLI example for querying deployment status, with no mention of Linux containers, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users wishing to use RunToCompletion semantics with Linux containers or query deployment status from non-Windows environments.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide Bash or cross-platform CLI examples for querying deployment status (e.g., using sfctl or REST API).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and guest executables on Linux nodes.
  • Mention any platform limitations explicitly, so users know if Linux scenarios are unsupported.
  • Ensure code samples and manifest snippets are not Windows-specific unless the feature is Windows-only.
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-specific tools and patterns are mentioned first or exclusively, and Linux equivalents are less prominent or missing. Windows tools like Event Viewer, ETW, and Diagnostics Agent are referenced with more detail, while Linux alternatives (such as LTTng, Syslog, and Linux-specific configuration) are mentioned but not explained in depth or with examples. Some tutorials and examples focus on .NET applications, which are cross-platform, but Windows-centric monitoring solutions are often presented first or with more detail.
Recommendations
  • Provide Linux-specific examples and walkthroughs for configuring monitoring, especially for EventStore, Syslog, and performance counters.
  • Ensure that Linux tools (like LTTng and Syslog) are described with the same depth as Windows tools (ETW, Event Viewer).
  • Add links or tutorials for monitoring Service Fabric clusters on Linux, similar to those provided for Windows.
  • When listing monitoring solutions or agents, present Windows and Linux options side-by-side rather than Windows-first.
  • Clarify which features are Windows-only and which are available on Linux, to reduce confusion.
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 provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (e.g., running services under Active Directory domain accounts, gMSA, BitLocker) are mentioned with detailed links and explanations, while Linux equivalents are either missing or referenced only briefly. Examples and guidance for Linux clusters (e.g., disk encryption, user accounts, certificate management) are sparse or absent, and Windows tools/patterns are often described first or exclusively.
Recommendations
  • Add explicit examples and guidance for Linux clusters, including how to run services under Linux user accounts and manage security principals.
  • Provide instructions or links for encrypting disks on Linux clusters, not just Windows/BitLocker.
  • Ensure parity in certificate management and secret handling for Linux, including any differences in procedure or tooling.
  • When mentioning Windows-specific features (e.g., gMSA, BitLocker), clarify if/when Linux equivalents exist and provide links or guidance.
  • Balance the order of examples and explanations so Linux and Windows are treated equally, or clearly indicate when a feature is Windows-only.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples provided exclusively in PowerShell. There are no Bash, CLI, or Linux/macOS-specific instructions or examples. The prerequisite section assumes the use of PowerShell modules, and REST API usage is also demonstrated via PowerShell scripts. There is no mention of Linux/macOS equivalents or guidance for users on those platforms.
Recommendations
  • Add Bash or Azure CLI examples for REST API calls, demonstrating how to trigger backups and track progress from Linux/macOS environments.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide guidance on connecting to Service Fabric clusters from Linux/macOS, including authentication and certificate handling.
  • Explicitly state platform requirements and alternatives for non-Windows users, or link to cross-platform documentation.
  • Consider including sample curl commands for REST API operations.
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 guidance for authoring Service Fabric manifests. It recommends using Visual Studio and a Windows file path to validate XML schema ordering, without mentioning cross-platform alternatives. Additionally, PowerShell is referenced for service creation, but no Linux CLI or scripting equivalents are provided. However, the core manifest concepts and examples are platform-neutral, and Service Fabric supports Linux clusters, so Linux users can complete the task with some friction.
Recommendations
  • Add instructions for validating XML schema ordering using cross-platform tools (e.g., VS Code, xmllint, or other editors available on Linux/macOS).
  • Mention the location of the ServiceFabricServiceModel.xsd schema file on Linux clusters, if applicable.
  • Provide CLI examples for creating services (e.g., using Azure CLI or sfctl) alongside PowerShell references.
  • Ensure that references to Windows tools are accompanied by Linux/macOS alternatives where possible.
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 page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-specific tooling throughout all lifecycle phases (deploy, test, upgrade, remove, maintenance). While REST API and .NET methods are also mentioned, PowerShell examples and references are prominent and often listed first. There is no explicit mention of Linux-native command-line tools or examples (such as Bash, sfctl, or Azure CLI usage), nor is there guidance for Linux/macOS users on equivalent workflows. This creates friction for non-Windows users, as they must infer or locate Linux-compatible instructions elsewhere.
Recommendations
  • Add Linux/macOS-friendly examples using sfctl and Azure CLI for each lifecycle phase alongside PowerShell examples.
  • Explicitly mention cross-platform tools and clarify which commands are available on Windows, Linux, and macOS.
  • Where PowerShell is referenced, provide equivalent Bash or CLI commands and link to relevant documentation.
  • Ensure REST API usage is demonstrated with cross-platform tools (e.g., curl, sfctl) and not just .NET or PowerShell.
  • Consider a table or section summarizing tool parity for Windows and Linux users.
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 heavily relies on PowerShell cmdlets for examples and instructions, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line examples use PowerShell syntax, and references to Service Fabric management are exclusively through PowerShell. There is no guidance for Linux users on how to perform these tasks, nor are Linux tools or patterns mentioned.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Explicitly mention that PowerShell examples are for Windows, and provide alternative instructions for Linux/macOS users.
  • Include links to documentation about managing Service Fabric applications from Linux/macOS environments.
  • Where possible, clarify which features or commands are Windows-only, and which are available cross-platform.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is cross-platform. However, in the 'Next steps' section, Windows-centric tools and workflows (Visual Studio and PowerShell) are mentioned first and exclusively, with no Linux/macOS equivalents or CLI alternatives provided. The main content is platform-neutral, but the upgrade guidance is Windows-biased.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux and macOS.
  • Include guidance for non-Windows environments, such as using VS Code or command-line tools for application upgrades.
  • Clarify if PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide Bash equivalents.
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 workflows first, with detailed tables and explanations. SFCTL (Service Fabric CLI), which is cross-platform and especially relevant for Linux users, is covered later and with less detail. The examples and parameter tables are heavily PowerShell-centric, and Linux-specific workflows (SFCTL) are not given equal prominence or example depth. There are no Linux-specific examples or explicit parity checks for Linux/macOS users.
Recommendations
  • Reorder sections so that SFCTL (Service Fabric CLI) parameters and workflows appear before or alongside PowerShell/Visual Studio, emphasizing cross-platform usage.
  • Provide example command invocations for SFCTL, similar to the PowerShell examples, including sample JSON parameter files.
  • Add a comparison table showing parameter mappings between PowerShell, Visual Studio, and SFCTL to clarify parity.
  • Explicitly mention Linux/macOS compatibility for SFCTL and highlight any differences or caveats.
  • Include a brief note at the start clarifying that all upgrade modes and parameters are available via SFCTL on Linux/macOS, not just Windows tools.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrades demonstrates notable Windows bias. The only example provided for preserving application parameters during an upgrade uses PowerShell, with no equivalent CLI or Linux/macOS example. References to Windows-specific tools (PowerShell, http.sys, Windows HTTP Server API) are made without mentioning cross-platform alternatives or clarifying platform limitations. The 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both Windows-centric, and lacks guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify which steps or tools are Windows-only and provide Linux/macOS alternatives where possible.
  • Include explicit guidance or links for Linux/macOS users, such as using sfctl or REST APIs.
  • Mention platform limitations (e.g., http.sys and Windows HTTP Server API) and suggest Linux/macOS-compatible approaches.
  • Balance 'Next steps' with tutorials for Linux/macOS environments.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides PowerShell-based manual scaling instructions and references Windows-centric tooling (e.g., PowerShell cmdlets like Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform guidance. Windows/PowerShell examples are presented first and exclusively in step-by-step procedures, creating friction for Linux users. However, the page does mention Linux clusters and is not strictly Windows-only.
Recommendations
  • Add equivalent Linux CLI instructions (e.g., using sfctl or REST API) for manual scaling operations alongside PowerShell examples.
  • Explicitly note which commands are Windows-only and provide cross-platform alternatives where possible.
  • Consider including bash or sfctl examples in parallel with PowerShell for all cluster management tasks.
  • Clarify any limitations for Linux clusters and link to Linux-specific guidance when relevant.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and additional upgrade examples are only shown in PowerShell. Windows-specific registry and OS configuration steps are described in detail, while equivalent Linux instructions are missing. The order of presentation and example coverage subtly favors Windows users, and Linux users may need to infer or research equivalent steps.
Recommendations
  • Provide Bash or shell script examples for manual cluster upgrade steps, especially where PowerShell is used.
  • Include Linux-specific instructions for disabling automatic updates (e.g., using systemd or apt/yum configuration) alongside Windows registry and OS profile settings.
  • When discussing VM scale set configuration, mention both 'windowsConfiguration' and 'linuxConfiguration' blocks in ARM templates.
  • Where PowerShell cmdlets are used for Service Fabric management, reference or link to equivalent Linux tools or CLI commands if available.
  • Present cross-platform examples in parallel or alternate between Windows and Linux to avoid the perception of Windows-first bias.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All code examples use PowerShell, including REST API calls, and require installation of the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation assumes the user is on Windows, and does not mention alternative approaches for non-Windows environments.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, showing how to trigger backup/restore and track progress from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any OS.
  • Mention any cross-platform CLI tools (such as Azure CLI) that can be used for these tasks, or explicitly state if only PowerShell is supported.
  • Provide guidance for Linux/macOS users on authentication (e.g., certificate handling) and connecting to Service Fabric clusters.
  • If PowerShell is required, note that PowerShell Core is available cross-platform and provide installation instructions for Linux/macOS.
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 ⚠ī¸ minor_windows_examples
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there is a noticeable Windows bias. PowerShell and Windows-specific tools are referenced more frequently and often appear before Linux equivalents. Some examples and links are Windows-centric, and certain explanations (such as port usage and DevOps tasks) focus on Windows/PowerShell scenarios. Linux is supported and mentioned, but parity in examples and tool references could be improved.
Recommendations
  • Ensure Linux CLI examples are provided alongside PowerShell examples, especially in sections referencing PowerShell APIs or tasks.
  • When referencing tools (e.g., 'netsh'), include Linux equivalents (e.g., 'ss', 'netstat', or 'lsof') for port range checks.
  • Balance the order of Windows and Linux guidance—avoid consistently listing Windows first.
  • Expand Linux-specific guidance for DevOps and operational tasks, not just mention ARM templates.
  • Where possible, clarify which features or steps are identical or different between Windows and Linux clusters.
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 covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there are several signs of Windows bias: Windows terminology and tools (e.g., certificate store names like 'My', references to NTLM authentication, and links to Windows-specific documentation such as CertGetCertificateChain on MSDN) appear throughout. Windows-centric language and defaults (e.g., 'LocalMachine', 'MY', 'FindByThumbprint') are used in parameters, sometimes without clear Linux equivalents or guidance. While Linux is mentioned in some settings (e.g., ContainerNetworkSetup, LinuxExternalExecutablePath), Windows patterns are often presented first or exclusively, and references to Windows-only features (like Windows Update, NTLM, and log file settings) are not always clearly marked as platform-specific. There are also references to Windows-specific concepts (e.g., 'Windows Fabric Replicator', 'fabric.exe', 'ServiceFabricAdministrators' group) without Linux alternatives or parity notes.
Recommendations
  • For each parameter or feature that is Windows-specific, clearly mark it as such and provide Linux/macOS equivalents or guidance where possible.
  • When referencing certificate stores, clarify Linux equivalents (e.g., file system paths, openssl usage) and provide examples for both platforms.
  • Where Windows terminology (e.g., 'MY', 'LocalMachine', 'FindByThumbprint') is used, add Linux-specific instructions or mapping.
  • For authentication mechanisms (e.g., NTLM), explicitly state platform limitations and provide Linux alternatives if available.
  • When linking to external documentation (e.g., MSDN), provide Linux-relevant links or explanations.
  • Ensure that Linux/macOS settings and patterns are presented alongside Windows, not after or omitted.
  • Add explicit notes or tables indicating which settings are cross-platform and which are platform-specific.
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 ⚠ī¸ windows_tools
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, with some evidence of Windows bias. The JSON snippet uses a Windows-style file path (D:\\SvcFab) as the default example for the 'dataPath' property, and the 'Next steps' section links primarily to PowerShell scripts for Windows-specific tasks (changing RDP port range, admin username/password), without Linux equivalents or guidance. Windows terminology and tools (RDP, PowerShell) are mentioned first or exclusively, even though Service Fabric supports both Windows and Linux nodes.
Recommendations
  • Provide Linux-specific examples for 'dataPath' (e.g., /var/svcfab) alongside Windows paths.
  • Add links or instructions for performing cluster VM management tasks (such as changing SSH port/user/password) on Linux nodes, not just Windows (RDP/PowerShell).
  • Clarify which tasks are Windows-only and which are cross-platform, and offer Linux/macOS alternatives where possible.
  • Balance examples and guidance so that Linux users can easily follow and complete the same tasks.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation provides example code for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is presented as the only scripting option, and there is no mention of Linux-native tools or commands for managing Service Fabric auto scaling. The documentation does note that resource monitoring is supported for containerized applications on Linux, but practical Linux usage examples are missing.
Recommendations
  • Add Bash or Linux CLI examples for configuring scaling policies, using Service Fabric CLI (sfctl) or REST APIs.
  • Explicitly mention cross-platform tools and workflows for Linux/macOS users.
  • Clarify which PowerShell commands are available on PowerShell Core (cross-platform) vs. Windows PowerShell.
  • Provide guidance or links for Linux users to achieve the same tasks as shown in PowerShell examples.
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 provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no mention of Linux-compatible CLI tools or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users, as Service Fabric also supports Linux clusters. There is no guidance or parity for Linux users on how to perform these operations.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal), as Azure CLI is cross-platform.
  • If Service Fabric supports Bash scripts or REST API for these operations, provide those examples.
  • Explicitly mention any differences or limitations for Linux clusters, if applicable.
  • Include a note clarifying which tools are supported on Linux and how Linux users can achieve the same tasks.
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 ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying cluster health, but does not offer equivalent Linux/macOS CLI or REST API examples. This creates friction for non-Windows users, as Service Fabric supports cross-platform management but only Windows tooling is demonstrated.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API sample calls for health queries, as these are platform-agnostic.
  • Mention that PowerShell is one option, but highlight cross-platform alternatives for cluster management tasks.
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 examples for both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json, Template.json) configurations. However, Windows-specific XML examples and PowerShell commands are presented first and more frequently, with no Linux shell or CLI equivalents. The use of WindowsServer in the XML example and PowerShell for service management may create friction for Linux users, though JSON-based configuration is also covered. No critical Linux functionality is missing, but parity in examples and tooling is lacking.
Recommendations
  • Add examples for Linux-based Service Fabric clusters, such as referencing Linux node configuration in ClusterManifest.xml or ClusterConfig.json.
  • Provide Azure CLI or REST API examples for service creation and updates, alongside PowerShell and C#.
  • Clarify that PowerShell commands are Windows-specific and suggest cross-platform alternatives where available.
  • Include explicit notes or sections for Linux/macOS users, highlighting any differences or limitations.
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 provides both C# and PowerShell examples for managing Service Fabric metrics, but only PowerShell is used for command-line/service creation examples. There are no Linux CLI (e.g., Bash, Azure CLI) or cross-platform alternatives shown, and PowerShell is presented before any mention of Linux-compatible tooling. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters and Azure CLI, but the documentation does not reflect this.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention and link to Linux-specific Service Fabric tools (e.g., sfctl) where relevant.
  • Clarify which PowerShell commands are available on Linux (PowerShell Core) and which are Windows-only.
  • Present cross-platform CLI examples (Azure CLI, sfctl) before or alongside PowerShell to improve parity.
  • Explicitly note any limitations or differences for Linux clusters in relevant sections.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, with PowerShell (a Windows-centric tool) shown first and no Linux CLI or scripting examples (such as Azure CLI, Bash, or REST API). This may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent Azure CLI or REST API examples for creating and updating services with MoveCost, as these are cross-platform.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported, and provide Bash or shell script alternatives where possible.
  • Explicitly mention if certain operations are only possible via PowerShell or C# SDK, and provide guidance for Linux/macOS users.
  • Consider including a table or section summarizing which tools are supported on which platforms.
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 page provides PowerShell examples for managing node tags and service requirements, but does not offer equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI, or REST API usage). PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The documentation also references PowerShell before C# APIs and omits mention of cross-platform tools or commands.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), and provide installation guidance if relevant.
  • Include Bash or shell script examples where possible, or clarify if certain operations are only possible via PowerShell or C# APIs.
  • Consider referencing cross-platform management tools before or alongside PowerShell to improve parity.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides configuration examples using XML, JSON, PowerShell, and C# APIs. However, all CLI/API examples for dynamic operations use PowerShell cmdlets, which are Windows-centric. There are no examples using cross-platform tools (e.g., Azure CLI, REST API, or Linux-native scripting), nor is it clarified whether Linux users can perform equivalent operations. This creates friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
  • Add equivalent examples using Azure CLI (if available), REST API, or Service Fabric CLI (sfctl), which are cross-platform.
  • Explicitly state if certain operations (e.g., PowerShell cmdlets) are only available on Windows, and provide Linux/macOS alternatives or workarounds.
  • Include notes or links to cross-platform management documentation for Service Fabric.
  • If PowerShell Core (pwsh) is supported cross-platform for these cmdlets, clarify and provide usage guidance.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the patch orchestration application is described only for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting both Windows and Linux. This creates friction for Linux users seeking parity.
Recommendations
  • Add links and examples for Linux-specific upgrade and configuration procedures, such as 'service-fabric-cluster-upgrade-linux.md' and 'service-fabric-cluster-config-upgrade-linux.md' if available.
  • Clarify which features (like Patch Orchestration Application) are Windows-only, and provide Linux alternatives or explicitly state limitations.
  • Ensure that references to configuration files and procedures are applicable to both Windows and Linux, or provide separate guidance where they differ.
  • Where possible, provide cross-platform examples or note differences in commands/tools between Windows and Linux clusters.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a noticeable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several sections, and Windows terminology (such as Windows services and executables) is used without always providing Linux equivalents. Standalone cluster creation and upgrade instructions are Windows-only, with Linux standalone clusters explicitly unsupported. Some examples and tooling references (e.g., PowerShell cmdlets, Service Fabric Explorer) are Windows-centric, and Linux-specific workflows or examples are often missing or referenced second.
Recommendations
  • Where possible, provide Linux equivalents alongside Windows instructions, especially for cluster management, health monitoring, and lifecycle operations.
  • Mention cross-platform tools (e.g., CLI, REST APIs) before or alongside Windows tools like PowerShell.
  • Add explicit Linux examples for cluster creation, management, and application lifecycle, or clarify when features are Windows-only.
  • Highlight Linux support and parity in programming models and container orchestration.
  • Ensure that references to tooling (e.g., Service Fabric Explorer, Visual Studio) include alternatives for Linux users.
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 on scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and links to Windows Server-specific scaling guides. There are no examples or guidance for Linux-based standalone clusters, nor are Linux tools or commands mentioned.
Recommendations
  • Include examples and instructions for scaling standalone Service Fabric clusters on Linux, if supported.
  • Mention Linux equivalents for cluster manifest querying and configuration upgrades (e.g., using CLI, REST API, or other tools).
  • Add links to Linux-specific documentation or clarify if standalone clusters are Windows-only.
  • If Linux is not supported for standalone clusters, explicitly state this to avoid confusion.
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 frequently references Windows Server clusters and Windows security options, often providing links and examples for Windows scenarios but omitting equivalent Linux guidance. Certificate-based security is described as cross-platform, but explicit Linux instructions, links, or examples are missing. Windows authentication (Kerberos) is discussed, but Linux authentication approaches are not mentioned. The structure and links prioritize Windows clusters, with Linux clusters only briefly referenced.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate generation, installation, and cluster configuration (e.g., using OpenSSL, Linux file paths, and relevant tools).
  • Clarify which security features and recommendations apply equally to Linux clusters, and highlight any differences or limitations.
  • Include parity in 'Next steps' and reference Linux cluster creation and security documentation if available.
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 on upgrading Azure Service Fabric clusters and mentions tools like PowerShell and Azure CLI for management tasks. However, it references Windows-specific upgrade procedures (such as Patch Orchestration Application and patching Windows OS images) and links to a Windows-focused patching guide without mentioning Linux equivalents or providing Linux-specific guidance. Examples and instructions for cluster management (certificates, ports, etc.) mention PowerShell/Azure CLI but do not clarify Linux support or provide Linux-specific examples. The Windows patching topic is discussed before any mention of Linux, and Linux cluster node patching is omitted.
Recommendations
  • Add explicit guidance or links for patching Linux-based Service Fabric clusters, if supported.
  • When referencing PowerShell/Azure CLI, clarify that Azure CLI is cross-platform and provide Linux/macOS command examples where relevant.
  • If Service Fabric supports Linux clusters, include instructions or links for Linux node OS upgrades and management tasks.
  • Ensure parity in examples and tool recommendations 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_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or scripting examples (e.g., Bash, Azure CLI) for scaling Service Fabric services. Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and before any Linux alternatives, and Linux users are not given parity in operational guidance. The only Linux-specific mention is in the 'Choosing a platform' section, which describes implementation differences but does not provide actionable Linux usage examples.
Recommendations
  • Add equivalent Linux/Bash/Azure CLI examples for scaling operations (e.g., creating/removing services, updating instance counts).
  • Mention and link to Linux-compatible tools for Service Fabric management (such as sfctl or Azure CLI).
  • Ensure administrative instructions are not Windows/PowerShell exclusive; provide cross-platform guidance.
  • Where PowerShell is used, clarify if the operation can be performed with Linux tools and provide those examples.
  • Consider restructuring examples so Linux and Windows approaches are presented side-by-side or equally.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets (e.g., New-ServiceFabricService), with no equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or cross-platform tools). All operational instructions reference PowerShell modules, and there is no mention of Linux-native workflows or tools. This creates friction for non-Windows users, who must translate or research equivalent commands themselves.
Recommendations
  • Add Azure CLI examples for all service creation and management operations, as Azure CLI is cross-platform.
  • Explicitly mention if certain operations can only be performed with PowerShell, and provide alternative REST API or SDK examples where possible.
  • Include Bash or shell script examples where appropriate, or clarify the cross-platform compatibility of the Service Fabric tools.
  • Update the 'Next steps' section to reference Linux/macOS-compatible management guides, not just PowerShell.
  • Where PowerShell is referenced, add a note about cross-platform PowerShell Core support, if applicable.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container application manifest examples exhibits Windows bias by referencing Windows Server 2016 Container Sample manifests as the basis for its examples, and by providing Windows-specific instructions (e.g., using 'winver' to get OS build version). There is no explicit mention of Linux container manifest samples, nor are Linux-specific instructions or examples provided. While some sections acknowledge Linux (e.g., certificate handling differences), the overall focus and examples are Windows-centric.
Recommendations
  • Add equivalent Linux container manifest examples or reference Linux container sample manifests.
  • Include instructions for obtaining OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') alongside Windows instructions.
  • Clarify which features and manifest settings are supported on Linux clusters, and note any differences.
  • Provide links to Linux-specific Service Fabric container documentation or samples where available.
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 but does not offer equivalent Linux CLI or scripting examples. Windows deployment and configuration paths (e.g., ApplicationManifest.xml, Visual Studio) are described in detail, while Linux-specific instructions are limited and often mentioned as secondary or with caveats. There are no Linux CLI (e.g., Bash, Azure CLI) examples for enabling or configuring DNS service, and Linux limitations are highlighted without offering workarounds or alternatives.
Recommendations
  • Add Linux-specific examples for configuring DNS service, such as using Azure CLI or Bash scripts.
  • Provide instructions for setting DNS names in Linux deployments (e.g., Docker Compose, YAML manifests) alongside PowerShell and ApplicationManifest.xml.
  • Clarify how Linux users can enable DNS service if portal access is unavailable, including step-by-step guidance for ARM templates or CLI.
  • Include parity in example ordering (Windows and Linux) and tools used.
  • Mention any Linux-specific tools or workflows for Service Fabric management where relevant.
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. While Service Fabric supports cross-platform clusters, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Provide REST API examples for health reporting and querying, as these are platform-agnostic.
  • Explicitly mention that PowerShell is one option and link to documentation for Linux/macOS users.
  • Ensure that all critical workflows are demonstrated for both Windows and Linux environments.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It mentions Visual Studio (a Windows-centric tool) for publishing, and links to PowerShell-based deployment guides as the next step. While .NET and REST are briefly mentioned as alternatives, Windows tools and patterns are presented first and most prominently, with no explicit Linux/macOS command-line examples or tooling references.
Recommendations
  • Add examples and links for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform .NET Core tools to retrieve the cluster manifest and deploy applications.
  • Include guidance for configuring and managing Service Fabric clusters from non-Windows environments.
  • Provide parity in 'Next steps' by linking to documentation for Linux/macOS workflows, not just PowerShell.
  • Mention cross-platform editors (e.g., VS Code) alongside Visual Studio where relevant.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page shows a moderate Windows bias. PowerShell and Visual Studio are mentioned first and in more detail when describing how to pass parameters during application creation. The PowerShell cmdlet is listed before the cross-platform sfctl tool, and Visual Studio (a Windows-centric IDE) is emphasized, including its integration with Azure DevOps and a PowerShell deployment script. Linux/macOS equivalents are mentioned (sfctl, Jenkins), but with less detail and after the Windows tools.
Recommendations
  • Present sfctl (the cross-platform CLI) before PowerShell, or give them equal prominence.
  • Provide example commands for both PowerShell and sfctl, with equivalent detail.
  • Mention cross-platform editors (e.g., VS Code) and deployment workflows, not just Visual Studio.
  • Expand on Jenkins or other non-Windows CI/CD options with concrete examples.
  • Clarify which tools are cross-platform and which are Windows-only.
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
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 for Service Fabric reliable services app manifest examples exhibits mild Windows bias. It references Windows-specific concepts (such as local admin accounts, NetworkService, and Setup.bat), and mentions the ServiceFabric PowerShell module as a way to create service instances, without providing Linux CLI equivalents or examples. Executable examples use Windows file extensions (.exe, .bat), and Windows account types are referenced before any Linux alternatives. No explicit Linux or cross-platform examples are provided.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of .bat files in SetupEntryPoint.
  • Mention Linux account types and how RunAsPolicy maps to Linux user/group management.
  • Provide Azure CLI or Service Fabric CLI (sfctl) examples for creating service instances, alongside PowerShell.
  • Clarify which features are cross-platform and which are Windows-only, especially for security principals and resource governance.
  • Where possible, show both Windows and Linux manifest snippets or highlight differences.
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 extensive PowerShell-based deployment instructions and examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible commands. Windows-centric tools (PowerShell, RDP) are referenced exclusively and appear before any Linux alternatives. There are no Linux/macOS-specific instructions or parity examples for cluster deployment or management, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for template deployment, resource group creation, and querying resources.
  • Include Bash shell command equivalents where applicable, especially for pinging and accessing VMs.
  • Mention SSH as an alternative to RDP for accessing jump boxes or VMs in the virtual network.
  • Clarify that Service Fabric can be managed from Linux/macOS and provide links or examples for cross-platform tooling.
  • Consider reordering examples so that cross-platform methods (Azure CLI, SSH) are presented before or alongside Windows-specific ones.
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 covers 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 (HTTP.sys, netsh, Windows HTTP Server API) are described in detail, often before their Linux equivalents. The HTTP.sys section is Windows-only, and while Kestrel is recommended for Linux, explicit Linux examples, troubleshooting, or environment-specific guidance are missing. Windows-centric configuration steps (e.g., netsh, ServiceManifest.xml for HTTP.sys) are presented without Linux alternatives or clarifications.
Recommendations
  • Add explicit Linux/macOS guidance and examples for Service Fabric Reliable Services with Kestrel, including environment setup, deployment, and troubleshooting.
  • Clearly indicate which sections are Windows-only and which are cross-platform, especially in configuration instructions.
  • Provide Linux-specific notes for ServiceManifest.xml endpoint configuration and port management.
  • Include sample code snippets or references for running Service Fabric Reliable Services on Linux, such as using Kestrel with Linux container images or Service Fabric clusters.
  • Mention any limitations or differences for Linux users (e.g., debugging, certificate management, firewall configuration) and link to relevant documentation.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' consistently references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links only for PowerShell usage. There is no mention of Linux or cross-platform CLI equivalents, nor are FabricClient API examples shown for non-Windows environments. The documentation assumes familiarity with Windows tools and patterns, creating friction for Linux/macOS users who may need to perform these operations using other methods.
Recommendations
  • Add examples for using the FabricClient APIs in .NET Core or other cross-platform SDKs, including code snippets for Linux/macOS environments.
  • Mention or link to any available Service Fabric CLI tools or REST APIs that can be used from Linux/macOS.
  • Clarify whether the PowerShell APIs are available on Linux (via PowerShell Core), and if so, provide guidance; if not, explicitly state the alternatives.
  • Include sample commands or workflows for Linux/macOS users, or note limitations if certain operations are Windows-only.
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_tools ⚠ī¸ windows_first
Summary
The documentation page is generally cross-platform in its XML manifest examples and explanations, but it demonstrates bias by providing only a PowerShell (Windows) example for application deployment, referencing Windows file paths for schema locations, and mentioning the Service Fabric PowerShell module as the way to create service instances. Linux equivalents (such as Azure CLI or sfctl) are not mentioned, and Linux-specific deployment examples are missing.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or sfctl alongside or instead of PowerShell.
  • When referencing file paths (such as schema locations), provide both Windows and Linux paths or clarify platform differences.
  • Mention Linux tools and workflows (e.g., sfctl, Bash scripts) wherever PowerShell or Windows tools are referenced.
  • If the Service Fabric PowerShell module is not available on Linux, explicitly state this and link to Linux alternatives.
  • Consider providing a table or section summarizing platform-specific differences for endpoint and certificate management.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation is heavily oriented toward Windows development workflows, specifically Visual Studio usage. All deployment, editing, and publishing instructions reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-only. There are no examples or guidance for Linux/macOS users or cross-platform tools. The only mention of alternative deployment methods is a brief reference to ARM and PowerShell cmdlets, but no Linux equivalents or CLI examples are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deploy Service Fabric applications without Visual Studio.
  • Provide examples using Azure CLI, Service Fabric CLI (sfctl), or other cross-platform tools for deployment and configuration.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include sample scripts or instructions for editing and deploying StartupServices.xml on Linux/macOS.
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 API (C#) and PowerShell usage, with PowerShell commands shown prominently and exclusively for command-line interaction. There are no examples or mentions of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools), and PowerShell is presented as the primary scripting interface for Service Fabric health reporting. REST API is mentioned, but no concrete Linux/macOS command-line examples (e.g., curl) are given.
Recommendations
  • Add Bash or Azure CLI examples for sending health reports and querying health status, especially for REST API usage (e.g., using curl or az commands).
  • Explicitly mention cross-platform support for Service Fabric health reporting and clarify which tools are available on Linux/macOS.
  • Provide guidance for Linux/macOS users on how to install and use Service Fabric CLI or REST endpoints for health reporting.
  • Reorder sections so that REST and cross-platform methods are presented before or alongside PowerShell, not after.
  • Include notes about PowerShell Core availability on Linux/macOS if relevant, or clarify if the PowerShell commands are Windows-only.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for the Fault Analysis Service overview provides usage instructions primarily for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and ServiceFabric PowerShell module). There are no examples or instructions for Linux/macOS users, such as using CLI tools, Bash scripts, or cross-platform SDKs. The PowerShell example is Windows-centric, and no Linux equivalents (e.g., Azure CLI, Bash, or REST API usage) are mentioned.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS environments, such as via Azure CLI, Bash, or REST API.
  • Mention cross-platform SDKs or tools that can be used to interact with the Fault Analysis Service.
  • Clarify whether the Fault Analysis Service APIs and features are available and supported on Linux-based Service Fabric clusters.
  • If PowerShell is required, note any cross-platform support (e.g., PowerShell Core) or alternatives for Linux 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 tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and step-by-step instructions reference Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools for application upgrades.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using cross-platform tools like Azure CLI or REST API.
  • Mention and link to any available Linux/macOS-compatible tooling for Service Fabric application upgrades.
  • Clarify which steps are Windows-only and provide alternative workflows for Linux/macOS users where possible.
  • Include sample scripts or commands for Linux shells (bash) alongside PowerShell examples.
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 Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but there are no bash or shell script examples. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section. The only CLI example is Azure CLI, but there is no parity for Linux-specific workflows or troubleshooting.
Recommendations
  • Add explicit bash/shell script examples for Linux users alongside PowerShell examples.
  • Ensure Linux package manager scenarios are described with equal prominence as Windows activation and updates.
  • Provide links to Linux-specific migration guides or troubleshooting resources.
  • Mention Azure CLI as cross-platform and clarify that PowerShell is optional for Windows users.
  • Include sample ARM templates or CLI commands that demonstrate Linux VM migration.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.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 Azure CLI and Azure PowerShell examples for deploying ZRS managed disks. However, PowerShell examples are heavily focused on Windows VM creation and use Windows-specific tools and patterns (e.g., Windows image references, Windows admin credentials, ConvertTo-SecureString). PowerShell sections consistently use Windows images and parameters, while Azure CLI examples use Ubuntu images. Resource Manager Template examples are also presented with PowerShell commands and Windows-centric parameters. The PowerShell and template sections are Windows-first and lack parity for Linux VM creation, making it harder for Linux users to follow equivalent workflows using PowerShell or ARM templates.
Recommendations
  • Add PowerShell examples for deploying Linux VMs with ZRS disks, using Linux image references and Linux admin credential patterns.
  • Update Resource Manager Template sections to include Linux VM deployment examples, or clarify how to adapt templates for Linux VMs.
  • Ensure that PowerShell and ARM template instructions are not exclusively Windows-focused, and provide guidance for Linux scenarios.
  • Where possible, use generic admin credential patterns or explain differences for Linux and Windows VM creation.
GitHub Create Pull Request
Virtual Machines Ultra Disks for VMs - Azure Managed Disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation covers Ultra Disks for both Linux and Windows VMs, but consistently uses Windows VM images (Win2016Datacenter) in all CLI and PowerShell examples. No examples are provided for deploying Ultra Disks with Linux VM images, nor are Linux-specific post-deployment instructions (such as partitioning/formatting disks on Linux) included. Windows VM creation is referenced first in portal instructions, and all code samples default to Windows VM images, creating friction for Linux users.
Recommendations
  • Add parallel examples using Linux VM images (e.g., Ubuntu, CentOS) for Azure CLI and PowerShell commands.
  • In portal instructions, reference both Windows and Linux VM creation quickstarts equally, or provide links to Linux VM creation guides.
  • Include post-deployment steps for partitioning and formatting Ultra Disks on Linux (e.g., using fdisk, mkfs, etc.), alongside Windows instructions.
  • Explicitly state that Ultra Disks are supported for both Linux and Windows VMs, and clarify any OS-specific requirements or limitations.
  • Where variables are set (e.g., --image), show both Windows and Linux values, or note how to select the appropriate image for your OS.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows-centric tools (notably Hyper-V and PowerShell's Convert-VHD) as the primary or only method for creating and converting VHDs. It lacks equivalent Linux-native instructions for key steps such as VHD creation and conversion, and Windows tools are mentioned first and most prominently.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or vboxmanage convertfromraw).
  • Provide Linux command-line examples for converting disk images to fixed-size VHD format.
  • Mention KVM, VirtualBox, or other common Linux virtualization solutions alongside Hyper-V, and provide links to their documentation.
  • When referencing PowerShell cmdlets (e.g., Convert-VHD), also reference equivalent Linux commands or tools in the same section.
  • Consider reordering sections so that Linux-native workflows are presented first or at least in parallel with Windows-based ones.
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 primarily focuses on .NET and C# examples, which are cross-platform, but the 'Next steps' section lists Windows-centric tools (Visual Studio and PowerShell) before mentioning any alternatives. There are no Linux-specific examples or references to Linux tooling, but the core serialization content is platform-neutral.
Recommendations
  • Add examples or links for upgrading applications using Linux/macOS tools, such as Azure CLI or Bash scripts.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Clarify that PowerShell is available cross-platform, or provide equivalent Bash/CLI instructions.
  • Ensure that any referenced tutorials or guides include Linux/macOS options where applicable.
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) give PowerShell examples before CLI. Portal instructions are generic, but scripting examples sometimes default to PowerShell first. There are no Windows-only tools or patterns, and Linux parity is generally maintained, but the ordering and emphasis may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell in each section, as CLI is cross-platform.
  • Ensure all PowerShell examples are matched with CLI equivalents.
  • Explicitly note that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
  • Where possible, add Bash shell examples for tasks that can be done outside Azure CLI/PowerShell.
  • Review the ordering of tabbed content to avoid implicit Windows-first bias.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.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 PowerShell and Azure CLI examples, but PowerShell (commonly associated with Windows) is presented before CLI. The PowerShell section is detailed and uses Windows-centric terminology (cmdlets), while the CLI section is also present and complete. There are no Linux-specific examples or explicit mentions of Linux tools, but the CLI commands are cross-platform. The Azure portal instructions are platform-neutral. No critical Linux functionality is missing, but Windows/PowerShell patterns are prioritized.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more widely used on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add a note clarifying that PowerShell is available cross-platform, but CLI is the default on Linux/macOS.
  • Where possible, provide bash shell scripting examples for disk operations.
  • Ensure terminology is neutral (e.g., 'commands' instead of 'cmdlets' when referring to CLI).
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows VMs, and provides both Azure CLI and PowerShell examples. However, the PowerShell example is presented first, which may indicate a minor 'windows_first' bias. No critical sections are Windows-only, and Linux users are able to complete the migration using the Azure CLI example provided.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or alternate their order to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell script examples for Linux users, if relevant.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.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 PowerShell and Azure CLI examples for most tasks, but PowerShell examples are often presented before CLI examples, which may subtly prioritize Windows users. The 'Assign RBAC role' and 'Assign Azure policy' sections link to both PowerShell and CLI guides, but PowerShell is mentioned first. However, Linux parity is generally maintained, and CLI examples are present throughout. The 'Next steps' section includes both Linux and Windows guides for VHD upload/download.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid implicit prioritization.
  • Explicitly state that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where possible, add Bash or shell script examples for disk operations to further support Linux users.
  • Ensure that all screenshots and portal instructions are not Windows-specific (e.g., avoid showing Windows UI elements if not necessary).
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.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 PowerShell references, but links to PowerShell custom role creation first and mentions PowerShell alongside CLI for configuring NetworkAccessPolicy. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is referenced before CLI in the NetworkAccessPolicy section. Linux-specific examples are present (CLI), but Windows tools and patterns are mentioned first or exclusively in some sections.
Recommendations
  • Add links to Linux/CLI-based custom RBAC role creation documentation alongside the PowerShell guide.
  • Ensure CLI and PowerShell examples are presented together, or alternate which is mentioned first.
  • Where possible, provide explicit Linux/macOS command examples for relevant tasks, not just PowerShell.
  • Clarify that both CLI and PowerShell are supported and provide parity in instructions.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is generally cross-platform, with explicit support for both Linux and Windows VMs. However, there are minor instances of Windows-first bias, such as Windows image sizes being described before Linux in the 'Size requirements' section, and PowerShell being mentioned before CLI in the customer-managed key section. Both Linux and Windows examples and tools are referenced, but Windows is sometimes listed first.
Recommendations
  • When describing image sizes or requirements, alternate the order of Linux and Windows examples, or present them together to avoid implicit prioritization.
  • In sections referencing command-line tools (e.g., PowerShell and CLI), list both platforms in parallel or alternate their order.
  • Ensure that any links to how-to guides or scripts for both Linux and Windows are equally prominent and easy to find.
  • If possible, provide explicit Linux/macOS command examples alongside PowerShell, especially in deployment or configuration sections.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM templates. PowerShell is primarily a Windows tool, and its inclusion before Azure CLI may suggest a Windows-first bias. However, all examples and instructions are relevant to Linux VMs, and Linux-specific commands and troubleshooting steps are provided. No critical Linux examples are missing, and Linux tools are adequately covered.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as Azure CLI is more cross-platform and commonly used for Linux.
  • Clarify that PowerShell examples are for users who prefer PowerShell on Windows or cross-platform PowerShell, but Azure CLI is recommended for Linux environments.
  • Consider adding Bash script examples for common deployment scenarios, as Bash is native to Linux.
  • Explicitly state that all PowerShell commands are for managing Azure resources, not for running inside Linux VMs.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Windows and Linux in most sections, including CLI, REST, and portal instructions. However, there is a mild Windows bias: PowerShell examples are shown with Windows as the default OS, and Windows terminology (Sysprep) is mentioned before Linux equivalents in some places. The PowerShell section uses Windows as the primary example and only briefly notes how to switch to Linux. CLI and REST examples use Linux as the default, balancing the bias. No critical Linux gaps are present.
Recommendations
  • In PowerShell examples, provide Linux as the primary example or alternate examples for both OS types.
  • When mentioning OS-specific steps (e.g., Sysprep vs waagent), list Linux first or equally.
  • Add explicit notes that PowerShell can be used for Linux image management, not just Windows.
  • Ensure that all CLI and PowerShell examples show both Linux and Windows usage equally.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.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 major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before CLI equivalents. There are no missing Linux examples, and the CLI is well covered, but the prominence of PowerShell may create friction for Linux users.
Recommendations
  • Where possible, list Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux.
  • Ensure all critical instructions reference both CLI and PowerShell equally, avoiding language that suggests PowerShell is the primary or preferred method.
  • Highlight that Azure CLI is the recommended tool for Linux users, and clarify that PowerShell is optional.
  • Consider adding brief Bash shell scripting examples for disk operations (e.g., mounting disks) where relevant.
  • Review backup instructions to ensure CLI methods are described with equal prominence to PowerShell.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation is highly Linux-focused, providing detailed, distribution-specific instructions for expanding disks on Linux VMs in Azure. However, there is a single section at the end that provides a PowerShell script for checking classic VM SKU support, with no equivalent Bash/Azure CLI example. This is a minor instance of Windows/PowerShell bias in an otherwise Linux-centric guide.
Recommendations
  • For the 'Expand without downtime classic VM SKU support' section, provide an equivalent Azure CLI or Bash script to check VM SKU capabilities, or clarify if PowerShell is the only supported method for this specific check.
  • If possible, add a note explaining why PowerShell is used in this context and whether Linux users can run the script via Azure Cloud Shell or another cross-platform method.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but Windows content and tooling (DISKSPD) are introduced first and in greater detail. Windows tools are mentioned before Linux equivalents, and the Windows section precedes the Linux section, which may create a perception of Windows priority. However, Linux instructions are thorough and parity is generally maintained.
Recommendations
  • Present Linux and Windows tools/examples in parallel or in separate, equally prominent sections.
  • Consider starting with a neutral introduction or alternating which platform is presented first.
  • Explicitly mention that both DISKSPD (Windows) and FIO (Linux) are recommended tools, and clarify their platform compatibility.
  • Add a summary table comparing Windows and Linux benchmarking tools and commands for quick reference.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.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 enabling Azure Disk Encryption for Linux VMs and provides Linux-specific instructions and examples. However, there are minor instances of Windows bias: PowerShell is mentioned alongside Azure CLI in several places, and PowerShell examples/scripts are referenced before or equally with Linux-native tools. The 'Next steps' and introductory quickstart links list both CLI and PowerShell options, with PowerShell sometimes mentioned first. There are no missing Linux examples or exclusive use of Windows tools, and all technical content is Linux-centric.
Recommendations
  • When listing quickstarts or scripts, consistently mention the Azure CLI (Linux-native) option before PowerShell, as the primary audience is Linux administrators.
  • Clarify that PowerShell is cross-platform and can be used on Linux, or provide a brief note to avoid confusion.
  • Where possible, emphasize Linux-native tools (Azure CLI, Bash scripts) over PowerShell for Linux VM management.
  • Ensure that all examples and scripts are available in both Azure CLI and PowerShell, and that Linux-native methods are highlighted as the default.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.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 PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples and instructions are presented before Azure CLI (which is more native to Linux), and the PowerShell section is more detailed and extensive. There is a minor Windows bias in the ordering and depth of PowerShell coverage, but Linux-native CLI and OS-level commands are also included.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more commonly used on Linux.
  • Ensure Azure CLI coverage is as detailed as PowerShell, including all disk scenarios.
  • Explicitly state that PowerShell commands can be run from Azure Cloud Shell or a Linux system with PowerShell installed, to avoid confusion.
  • Consider adding Bash scripting examples for common tasks, since Bash is native to Linux.
  • Review for parity in explanations and screenshots between PowerShell and CLI sections.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V instructions are presented first, and references to Windows tools (such as Hyper-V Manager and PowerShell's convert-vhd cmdlet) appear before Linux alternatives. All Linux hypervisor methods are included and detailed, but Windows tools are sometimes mentioned as the default or primary option.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V/Windows-specific instructions.
  • When mentioning disk conversion tools, list Linux tools (e.g., qemu-img) before Windows tools (e.g., convert-vhd), or present them together.
  • Clarify that Hyper-V Manager and convert-vhd are Windows-only tools, and highlight Linux alternatives for disk conversion and management.
  • Ensure that all instructions for disk conversion, VM preparation, and upload are equally detailed for Linux and Windows environments.
  • Consider adding a summary table or navigation aid to help users quickly find instructions relevant to their platform.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell section is given equal prominence despite PowerShell being primarily a Windows tool. There is no explicit Linux example (e.g., Bash), but the CLI example is cross-platform. The CLI section appears first, which is positive, but the PowerShell section may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples (even if they mirror the CLI usage) to reinforce Linux parity.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, but note its Windows origins.
  • Consider adding a note about the platform compatibility of each tool.
GitHub Create Pull Request
Virtual Machines Overview of Azure Disk Storage ...in/articles/virtual-machines/managed-disks-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_reference
Summary
The documentation is generally cross-platform, explicitly stating applicability to both Linux and Windows VMs. However, there are a few sections where Windows tools, terminology, or references are presented first or exclusively, such as links to Windows documentation before Linux equivalents, and Windows partitioning concepts (MBR/GPT) are emphasized. The 'Upload your VHD or VHDX' section links to both Azure CLI (Linux) and PowerShell (Windows) guides, but the Windows link is listed second. The OS disk section references Windows drive letters and partitioning, with Linux equivalents not always given equal detail.
Recommendations
  • Ensure Linux and Windows examples, tools, and terminology are presented with equal prominence.
  • When discussing disk partitioning (MBR/GPT), include Linux-specific guidance or links alongside Windows references.
  • In sections referencing drive letters or Windows-specific paths, add Linux equivalents (e.g., mount points, device names) for clarity.
  • Where links to platform-specific guides are given, list Linux and Windows options together or alternate their order.
  • Review all references to Windows tools (e.g., PowerShell) and ensure Linux tools (e.g., Azure CLI, Bash) are equally mentioned.
GitHub Create Pull Request
Virtual Machines Azure premium storage: Design for high performance ...ticles/virtual-machines/premium-storage-performance.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 and Windows guidance, but there are several instances where Windows tools (e.g., PerfMon, Storage Spaces, PowerShell) are mentioned first or in more detail, and Windows-specific patterns are described with more depth. Linux equivalents are present but sometimes less emphasized or referenced after Windows. Some sections (e.g., disk striping, performance counters) give more detailed or prominent instructions for Windows users, with Linux instructions present but less detailed or referenced via external links.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
  • When mentioning tools (e.g., PerfMon/iostat, Storage Spaces/MDADM), list both platforms together or alternate which is mentioned first.
  • Expand Linux-specific instructions (e.g., for disk striping, benchmarking, and performance tuning) to match the depth provided for Windows.
  • Where PowerShell is used for Windows, provide equivalent CLI/bash commands for Linux.
  • Add more direct Linux examples inline, rather than primarily referencing external links.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page is generally platform-neutral, focusing on Service Fabric's backup configuration via REST APIs and JSON payloads. However, the only example for file share backup storage uses Windows-style UNC paths (\\StorageServer\BackupStore) and references 'Integrated Windows Authentication', which are Windows-specific concepts. No Linux or SMB/CIFS examples are provided, and Windows authentication is mentioned first. This creates minor friction for Linux users who may want to use SMB/CIFS file shares or need guidance on configuring file share access from non-Windows nodes.
Recommendations
  • Add examples showing how to configure file share backup storage using SMB/CIFS paths compatible with Linux/macOS (e.g., //StorageServer/BackupStore).
  • Include guidance or links for configuring file share access and authentication from Linux-based Service Fabric clusters, such as using mount options or credential management.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide parity in authentication and path examples.
  • Mention any limitations or differences for Linux/macOS clusters regarding file share backup storage.
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 described in more detail, and Windows scenarios (such as IIS lift-and-shift) are highlighted first in the 'Scenarios for using containers' section. Windows tutorials and references are often listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned with more granularity than Linux (which only mentions Docker).
Recommendations
  • Ensure Linux examples and tutorials are listed alongside Windows ones, ideally alternating or grouping by platform.
  • Expand Linux-specific scenarios (e.g., NGINX, Apache, Python apps) in the 'Scenarios for using containers' section to balance the Windows IIS example.
  • Provide more detail about Linux container runtimes and tools (e.g., mention containerd, podman, or Docker alternatives if supported).
  • Clarify parity in feature support between Linux and Windows containers, especially for advanced features (networking modes, resource governance, etc.).
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 Docker Compose deployment. However, PowerShell commands are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples, which are cross-platform, are included but appear after the PowerShell section.
Recommendations
  • Present cross-platform CLI (sfctl) examples before PowerShell to emphasize Linux/macOS parity.
  • Explicitly state that sfctl is supported on Linux/macOS and link to installation instructions for non-Windows users.
  • Ensure that all features described are available via sfctl, and clarify any differences in functionality or limitations between PowerShell and CLI.
  • Consider adding a short note at the start of the examples section highlighting that both Windows (PowerShell) and cross-platform (sfctl) options are available.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced as being installed in a Windows file path, and the example application package structure uses a Windows-style executable (.exe). Visual Studio is mentioned as a packaging tool, which is primarily a Windows application. There are no explicit Linux/macOS examples or references to cross-platform tooling, and Windows terminology appears first or exclusively.
Recommendations
  • Add Linux/macOS equivalent instructions for locating schema files, or clarify if the SDK supports those platforms.
  • Provide examples using cross-platform executables (e.g., .sh, .out, or generic binaries) alongside .exe.
  • Mention or link to cross-platform command-line tools for packaging and deploying guest executables, if available.
  • Clarify Visual Studio alternatives for Linux/macOS users, such as Visual Studio Code or CLI tools.
  • Explicitly state platform support for Service Fabric guest executables and SDK, including any limitations.
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 for each. However, Windows development (with .NET SDK, Visual Studio, and PowerShell) is described before Linux development (with Java SDK, Eclipse, and Yeoman), which is a minor 'windows_first' bias. No Windows-only tools or examples are given exclusively, and Linux equivalents are mentioned. No critical sections are Windows-only.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them side-by-side to emphasize equal support.
  • Consider linking to both Windows and Linux quickstart guides in the 'Next steps' section, rather than only the .NET (Windows) quickstart.
  • Explicitly state Linux/macOS support in introductory sections to reinforce parity.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally platform-neutral, but there are subtle signs of Windows bias. Windows-specific terminology and tools (such as references to 'auto-start Windows service', 'FabricHost.exe', and EXE/DLL files) are mentioned first or exclusively in some sections, even though Service Fabric supports Linux. Linux equivalents or clarifications are not always provided alongside Windows examples. However, the page does acknowledge Linux support and containers, and does not prevent Linux/macOS users from understanding the concepts.
Recommendations
  • When referencing Windows-specific tools or services (e.g., 'FabricHost.exe'), clarify if and how these concepts apply on Linux (e.g., what is the equivalent process/service on Linux nodes?).
  • When mentioning executable formats (EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) or note that Linux executables are supported.
  • Where Windows terminology is used (e.g., 'auto-start Windows service'), add a note about Linux startup mechanisms (e.g., systemd services) if relevant.
  • Ensure that examples and terminology are presented in a platform-neutral way, or provide parallel Linux/macOS information when possible.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.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 Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, Windows-specific extension names (e.g., ApplicationHealthWindows) are used. In tabbed sections, PowerShell is often listed after CLI, but the PowerShell examples are detailed and prominent. There is minor bias in extension naming and the prominence of PowerShell, but Linux users can complete all tasks using Azure CLI or REST API. The documentation does not exclusively favor Windows, but minor friction exists for Linux users.
Recommendations
  • Ensure that Linux-specific extension names (e.g., ApplicationHealthLinux) are used in PowerShell examples when deploying Linux VMSS, or clarify when to use ApplicationHealthWindows vs ApplicationHealthLinux.
  • Add explicit notes or examples for macOS users where CLI usage is relevant.
  • Where PowerShell is used, clarify its cross-platform availability or provide Bash alternatives if possible.
  • Consider listing Azure CLI examples first in tabbed sections to reduce perceived Windows bias.
  • Add a short section explaining which tools are cross-platform and which are Windows-only.
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 parity between Azure CLI and PowerShell for all command-line examples, but PowerShell examples are consistently presented immediately after CLI examples and before ARM template examples. There is no explicit Linux bias, but the ordering and inclusion of PowerShell throughout may subtly prioritize Windows users. However, Azure CLI is cross-platform and all tasks can be completed on Linux/macOS using CLI or ARM templates. No Windows-only tools or patterns are mentioned, and Linux users are not blocked from completing any task.
Recommendations
  • Consider alternating the order of CLI and PowerShell examples, or explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that PowerShell examples are for Windows users, while CLI and ARM templates are suitable for all platforms.
  • Ensure screenshots and UI references are not Windows-specific (currently, portal screenshots are neutral).
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes example commands for Azure CLI, PowerShell, Portal, and ARM templates. The PowerShell section is present and detailed, but the CLI section (az CLI) is also included and is cross-platform. However, the PowerShell example is shown after the CLI, and both are given parity. There is no evidence of Windows-only tools or patterns being mentioned exclusively or before Linux equivalents. The documentation does not provide Linux-specific shell examples (e.g., Bash scripting), but Azure CLI is inherently cross-platform. The bias is minor, mainly in the presence of PowerShell examples, which are more relevant to Windows users, but Linux/macOS users are fully supported via Azure CLI and ARM templates.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash scripting examples for automation on Linux/macOS, if relevant.
  • Clarify that PowerShell examples are optional and primarily for Windows users, while CLI is recommended for cross-platform usage.
  • Ensure that any screenshots or UI references are not Windows-specific (e.g., Azure Portal is platform-agnostic).
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a balanced overview of orchestration modes for Azure Virtual Machine Scale Sets, with clear support for both Linux and Windows VMs. However, there is a minor bias in the 'Azure Site Recovery' feature row, which notes 'Yes (via PowerShell)' for Flexible orchestration mode, implying a Windows-centric tool for backup/recovery. Additionally, the only CLI example provided uses 'az vm create', which is cross-platform, but the documentation does not explicitly show Linux-specific commands or mention Linux tools, and Windows is mentioned first in some places.
Recommendations
  • Clarify that Azure Site Recovery can be used for Linux VMs and provide Linux-specific instructions or alternatives to PowerShell where possible.
  • Add explicit Linux examples or mention Linux compatibility in CLI instructions.
  • Ensure parity in mentioning both Linux and Windows when discussing supported operating systems, tools, and extensions.
  • Where PowerShell is referenced, also mention Bash/Azure CLI alternatives if available.
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 and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets. However, there is a notable Windows bias: PowerShell examples are consistently presented alongside Azure CLI and Bash, and Windows-specific extension types (ApplicationHealthWindows) are referenced before Linux equivalents. In several code snippets and REST examples, Windows extension types are shown as the default, and PowerShell is given equal prominence to Bash, despite Bash being more universally available across platforms. The ordering of examples sometimes puts Windows/PowerShell first or equally, rather than prioritizing cross-platform tools.
Recommendations
  • Ensure Linux and cross-platform examples (Azure CLI, Bash) are presented before Windows/PowerShell examples.
  • In REST and JSON configuration samples, use ApplicationHealthLinux as the default type, or show both Linux and Windows variants.
  • Clarify in each example which OS the extension type applies to, and avoid defaulting to Windows unless the scenario is Windows-specific.
  • Where possible, add macOS-specific notes or highlight that Bash/CLI examples work on macOS.
  • Consider grouping Windows/PowerShell examples in a separate section or tab, after Linux/cross-platform examples.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation generally presents cost optimization practices for Azure virtual machines in a platform-neutral way, but there is a minor bias where Windows-specific guidance (e.g., 'Use at least B2 for Windows machines') is mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No critical sections are Windows-only, and Linux users can follow all recommendations.
Recommendations
  • When mentioning VM sizing recommendations, provide equivalent guidance for Linux (e.g., 'Use at least B2 for Windows machines; for Linux, refer to performance requirements').
  • Present Windows and Linux pricing links together or in parallel, rather than listing Windows first.
  • Where automation or scheduling is discussed, clarify that solutions like Azure Automation and Logic Apps are cross-platform.
  • Ensure examples and recommendations are equally applicable to Linux and Windows, or explicitly note any platform-specific differences.
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 examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized over CLI or Portal. However, the PowerShell example is included alongside CLI and REST, which are cross-platform, but PowerShell is primarily a Windows tool. The CLI examples are shown before PowerShell, and there are no Windows-specific tools or patterns prioritized. No Linux/macOS-specific examples (e.g., Bash scripts) are given, but the CLI commands are cross-platform and suitable for Linux/macOS users. The only minor bias is the inclusion of PowerShell as a separate example, which may be unnecessary for Linux users, but it does not impede their ability to complete the task.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell scripting examples for Linux users, or explicitly mention that PowerShell is Windows-centric.
  • If possible, note that PowerShell Core is available cross-platform, but most users on Linux/macOS will use Azure CLI.
  • Ensure that CLI examples use variables and syntax compatible with Bash as well as Windows CMD.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service for application-consistent snapshots) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced secondarily and with less detail. SQL Server (a Windows-centric example) is highlighted more than Linux database solutions. Overall, Linux is supported, but Windows examples and tools are prioritized.
Recommendations
  • Provide equal detail for Linux tools (e.g., elaborate on fsfreeze usage and limitations, and mention other Linux backup coordination tools such as LVM snapshots or application-specific solutions).
  • Include Linux-first examples in backup scenarios, such as PostgreSQL or MySQL running on Linux VMs, and describe their backup strategies.
  • When discussing application-consistent backups, clarify the limitations for Linux and suggest best practices or third-party solutions for Linux workloads.
  • Balance the mention of Windows and Linux tools/patterns in each section, ensuring Linux solutions are not secondary.
  • Add links to Linux-specific documentation or guides for backup and disaster recovery.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support details before Linux, but provides parity in information for both platforms. No Windows-specific tools, examples, or patterns are prioritized elsewhere, and Linux support is clearly described. No critical sections are Windows-only, and Linux users can fully understand and use VM restore points.
Recommendations
  • Consider listing Linux operating system support before or alongside Windows to avoid implicit prioritization.
  • Ensure future updates maintain parity in detail and clarity for both Windows and Linux sections.
  • If CLI or PowerShell examples are provided elsewhere, ensure Linux shell (bash) examples are also included.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.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 scenarios for Azure Managed Disk encryption, but there is a consistent pattern of Windows/PowerShell examples and links being presented before Linux/CLI equivalents. References to PowerShell are frequent and often appear first in lists, while Linux/CLI links are included but secondary. No critical steps are Windows-only, and Linux parity is generally maintained, but the ordering and emphasis may create friction for Linux users.
Recommendations
  • Alternate the order of Windows/PowerShell and Linux/CLI examples and links so Linux users are not always presented second.
  • Explicitly state that all features and procedures are supported on both Linux and Windows VMs at the start of the article.
  • Where possible, provide combined examples or parallel instructions for both platforms in the same section.
  • Ensure that references to tools (PowerShell, CLI) are balanced and not disproportionately focused on Windows/PowerShell.
  • Consider adding a summary table or section that clearly maps procedures to both Windows and Linux environments.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-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 VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples side-by-side. In several sections, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows-centric tool. In some cases, PowerShell examples are shown before or alongside CLI, which may create friction for Linux users. However, all examples and guidance are applicable to Linux, and Linux-specific tools (Azure CLI, Bash, waagent) are well represented.
Recommendations
  • Consider presenting Azure CLI examples first in each section, as CLI is the primary cross-platform tool for Linux users.
  • Clearly indicate that PowerShell is optional and primarily for users on Windows or those who have installed PowerShell Core on Linux.
  • Add explicit notes or guidance for Linux users about the recommended tooling (Azure CLI, Bash) and clarify PowerShell's cross-platform status.
  • Where possible, minimize PowerShell examples or move them to secondary tabs/sections for Linux-focused documentation.
  • Ensure that troubleshooting and operational guidance always includes Bash/CLI commands as the default for Linux.
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 sync in Azure and provides thorough Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before explaining Linux mechanisms. All configuration and command examples are Linux-centric, and Linux tools (chrony, ntpd, systemd-timesyncd, cloud-init) are covered in detail. The only minor bias is the Windows context and links appearing first, which may confuse readers expecting Linux-only content.
Recommendations
  • Move the Windows Server 2016 discussion and links to a background or 'Azure host infrastructure' section, clarifying that this is context for Azure hosts, not for Linux VM configuration.
  • Add a brief statement at the start explaining that while Azure hosts use Windows Server 2016 for time sync, this page is focused on Linux VM configuration.
  • Ensure Linux-specific guidance is presented before any Windows context to reinforce the Linux focus.
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, but there are minor signs of Windows bias. In several sections, Azure PowerShell deployment instructions and troubleshooting commands are presented before their Azure CLI equivalents, despite CLI being more cross-platform and native to Linux. PowerShell is referenced heavily, and warnings about PowerShell-specific issues are included, even though Linux users are unlikely to use PowerShell. However, all examples and instructions are ultimately Linux-centric, and Linux tools and paths are consistently used.
Recommendations
  • Present Azure CLI instructions before Azure PowerShell in deployment and troubleshooting sections, as CLI is native to Linux.
  • Clarify that PowerShell instructions are optional for Linux users and highlight Azure CLI as the recommended method.
  • Reduce PowerShell-specific warnings or move them to a dedicated section for users who choose PowerShell on Linux.
  • Ensure all troubleshooting and deployment examples are available and prioritized for Azure CLI.
GitHub Create Pull Request