← Back to Dashboard
277
Pages Scanned
111
Pages Flagged
277
Changed Pages
40.1%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-03-06 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

111 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). There is no mention of Linux container support, nor are Linux container examples or equivalent Linux commands provided. The ApplicationManifest and ServiceManifest examples are explicitly named for Windows, and the important note at the start references Windows container applications.
Recommendations
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric. If so, add equivalent Linux container examples using a Linux image (e.g., mcr.microsoft.com/ubuntu) and Linux commands (bash, echo, cat, etc.).
  • If Initializer CodePackages are Windows-only, explicitly state this in the introduction to avoid confusion for Linux users.
  • If Linux containers are supported, provide guidance on path mapping and volume mounts for Linux (e.g., /workspace/log.txt instead of C:\WorkspaceOnContainer\log.txt).
  • Include links or references to Linux container documentation in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples, configuration guidance, and usage instructions are implicitly Windows-centric. There are no Linux-specific examples or guidance, and Linux users are informed that the feature is unavailable to them.
Recommendations
  • Explicitly state early in the documentation that reverse proxy is Windows-only, and provide alternative guidance or links for Linux users.
  • Add a prominent note or section outlining feature parity gaps and suggesting workarounds or alternatives for Linux clusters.
  • If possible, reference any roadmap or plans for Linux support, or link to related Linux Service Fabric documentation.
GitHub Create Pull Request
Service Fabric Deploy and upgrade with Azure Resource Manager ...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for removing Service Fabric application resources and refers to PowerShell before CLI in the 'Next steps' section. There are no equivalent CLI or cross-platform examples for Linux/macOS users, which may create friction for those not using Windows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource removal and management tasks.
  • Explicitly mention that REST API calls can be made using tools like curl or HTTPie, and provide example commands.
  • In 'Next steps', list CLI and PowerShell together or in alternating order to avoid Windows-first bias.
  • Where possible, clarify which tools are cross-platform and recommend them for non-Windows users.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides some Windows-centric examples and references, such as Windows-style file paths (e.g., 'D:\\SvcFab'), mentions of RDP port changes, and PowerShell scripts for post-deployment tasks. While the Service Fabric extension supports both Linux and Windows nodes, the examples and 'Next steps' links focus on Windows tools and workflows, with no Linux-specific guidance or parity in examples.
Recommendations
  • Provide Linux/Unix-style path examples (e.g., '/var/lib/servicefabric') alongside Windows paths in the extension snippet.
  • Include Linux-specific instructions or references for remote connection (e.g., using SSH) in the 'Next steps' section.
  • Add links or scripts for managing Linux VMs (e.g., changing SSH port, updating Linux admin users) similar to the PowerShell/RDP-focused scripts for Windows.
  • Clarify in the documentation when a step or example is Windows-only, and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page primarily references Windows-centric tools and workflows, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented before any Linux/macOS alternatives, and no Linux-native upgrade examples (e.g., CLI or Bash) are provided. The serialization guidance is focused on C#/.NET, which is cross-platform, but the upgrade tooling references are Windows-biased.
Recommendations
  • Add equivalent Linux/macOS upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), and reference them alongside PowerShell and Visual Studio.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) for application upgrades.
  • Ensure that upgrade tutorials and troubleshooting guides include Linux/macOS-compatible commands and examples.
  • Clarify which tools are Windows-only and provide links to Linux/macOS alternatives where available.
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 examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep templates are referenced, the PowerShell examples are highlighted first and in more detail, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell examples, or presenting both together.
  • Add links to relevant Azure CLI documentation for Service Fabric managed clusters.
  • Clarify that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a GUI tool typically used on Windows). No Linux or cross-platform CLI alternatives are mentioned, and Windows-centric patterns (PowerShell cmdlets) are presented without Linux parity.
Recommendations
  • Add equivalent Linux/macOS command-line examples using Azure CLI or REST API, if available.
  • Clarify whether the PowerShell cmdlet is supported on Linux (via PowerShell Core), or provide alternatives.
  • Mention cross-platform tools or interfaces (e.g., Azure Portal, Azure CLI) where possible.
  • If Service Fabric Explorer is Windows-only, recommend any web-based or cross-platform alternatives.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there are several instances of Windows bias. Windows/PowerShell examples and terminology are mentioned first or exclusively (e.g., client API used by PowerShell, classic PowerShell tasks in Azure DevOps, Windows container-specific guidance). Some example links and templates are Windows-focused, and Linux-specific examples or CLI equivalents are less prominent or missing. While Linux is referenced, Windows patterns and tools are often prioritized.
Recommendations
  • Ensure Linux CLI (az, bash) examples are provided alongside PowerShell examples, especially for cluster management and networking tasks.
  • When referencing ARM templates or sample clusters, include both Windows and Linux templates, or clarify applicability.
  • Mention Linux-specific networking considerations and tools (e.g., firewall, port management) where relevant.
  • Balance the order of Windows and Linux guidance so Linux is not always secondary.
  • Clarify when guidance is Windows-only and provide Linux alternatives or links where possible.
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 primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While it mentions 'az resource' for deleting applications, PowerShell examples and terminology are more prominent and appear first. There are no explicit Linux/macOS CLI examples or references to Bash, nor is there guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) commands for all management operations, not just deletions.
  • Provide examples for Bash or cross-platform usage, highlighting that Azure CLI works on Linux/macOS.
  • Clarify when PowerShell is required and when Azure CLI can be used, to help users on non-Windows systems.
  • Consider listing Azure CLI examples before or alongside PowerShell examples for parity.
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 is heavily focused on PowerShell-based workflows, with all CLI examples and module instructions using PowerShell. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools to interact with the REST API. The prerequisite section assumes PowerShell usage and does not mention alternatives for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or curl for REST API calls, suitable for Linux/macOS users.
  • Mention cross-platform tools and workflows in the prerequisites, such as Azure CLI or REST clients.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows/PowerShell users, and provide alternatives for other platforms.
  • Reorder sections or provide parallel examples so Linux/macOS users are not forced to translate PowerShell scripts.
  • Explicitly state platform requirements if certain steps are Windows-only, and link to Linux/macOS guidance where available.
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 provides code examples and administrative patterns primarily using PowerShell, which is a Windows-centric tool. No Linux command-line equivalents (such as Bash, CLI, or REST API) are provided for scaling operations. Windows/PowerShell examples are shown first and exclusively, creating friction for Linux users who may need to perform similar tasks. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences but does not provide Linux-specific operational guidance.
Recommendations
  • Add equivalent Linux command-line examples using Bash, Azure CLI, or REST API for scaling operations (e.g., creating/removing services, updating instance counts).
  • Mention and link to Linux-specific Service Fabric management tools or documentation where applicable.
  • Where PowerShell is referenced, clarify if the operation can be performed via cross-platform tools and provide those alternatives.
  • Ensure examples and administrative patterns are presented for both Windows and Linux, or note any limitations for Linux users.
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 provides manifest examples and explanations for Azure Service Fabric container applications. The examples and narrative are based on the Windows Server 2016 Container Sample, and several sections reference Windows-specific concepts (such as 'winver' for OS build detection and Windows file paths). There are no explicit Linux manifest examples, and Linux-specific patterns or differences are not discussed. While some notes mention Linux (e.g., certificate handling), the overall focus and examples are Windows-centric.
Recommendations
  • Add equivalent Linux-based manifest examples, referencing the Linux container sample repository.
  • Include notes or sections highlighting differences in configuration, file paths, and OS build detection for Linux clusters.
  • Mention Linux-specific Service Fabric container features or limitations where relevant.
  • Provide links to Linux documentation and samples alongside Windows references.
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 tooling. Command-line examples and guidance are exclusively PowerShell, and Windows-centric concepts (such as RDP and Windows directory paths) are used throughout. There are no Linux/macOS equivalents or alternative instructions, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Provide Bash shell command equivalents for template deployments.
  • Mention cross-platform tools (e.g., Azure Cloud Shell) that work on Linux/macOS.
  • Clarify that Service Fabric clusters can be managed from any OS, and provide guidance for Linux/macOS users.
  • Replace or supplement Windows-specific instructions (e.g., RDP, Windows directory paths) with cross-platform alternatives (e.g., SSH, generic paths).
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 (e.g., Bash, Azure CLI) examples. Windows tools and patterns (PowerShell, ApplicationManifest.xml, Visual Studio) are mentioned first or exclusively. Linux support is discussed, but Linux-specific instructions and examples are missing, especially for non-containerized services and for enabling DNS service outside ARM templates.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing services, especially for Linux clusters.
  • Clarify how Linux users can perform tasks currently shown with PowerShell or ApplicationManifest.xml, including any limitations.
  • Provide guidance for enabling DNS service on Linux clusters outside ARM templates, if possible.
  • Explicitly state any tasks that cannot be performed on Linux, and offer alternative approaches or workarounds where feasible.
  • Include editor-agnostic instructions (not just Visual Studio) for ApplicationManifest.xml edits.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and instructions reference Windows tools, with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. This creates friction for Linux/macOS users, as the upgrade process and parameter configuration are described only in the context of Windows environments.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for configuring upgrade parameters and health policies using tools available on Linux/macOS, such as sfctl (Service Fabric CLI).
  • Mention that Visual Studio and PowerShell are Windows-only, and provide links or references to Linux/macOS-compatible workflows.
  • Present cross-platform alternatives before or alongside Windows-specific instructions to improve parity.
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 provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation examples use Windows images (e.g., Win2016Datacenter) and reference Windows-specific quickstarts. There are no Linux VM image examples or Linux-specific guidance, despite the feature supporting both Linux and Windows VMs. This creates friction for Linux users, who must adapt the instructions themselves.
Recommendations
  • Add Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in all CLI and PowerShell sections.
  • Reference Linux VM quickstart documentation in the portal section, not just Windows.
  • Explicitly note any differences or considerations for Linux VMs, such as disk partitioning and formatting steps.
  • Ensure that CLI and PowerShell scripts are generic or provide both Windows and Linux variants where relevant.
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 and prioritizes Windows/Hyper-V tooling (e.g., Hyper-V Manager, Convert-VHD PowerShell cmdlet) for VHD creation and conversion. Instructions for creating and converting VHDs are Windows-centric, with no Linux-native alternatives provided. Linux users are left without guidance for performing critical steps (such as converting disk formats) using Linux tools.
Recommendations
  • Add instructions for creating and converting VHD files using Linux-native tools (e.g., qemu-img, VBoxManage) alongside or in place of Hyper-V/PowerShell steps.
  • Mention Linux virtualization solutions (e.g., KVM, VirtualBox) as alternatives to Hyper-V for VHD creation.
  • Provide Linux command-line examples for extracting, converting, and preparing VHDs, not just referencing Windows tools.
  • Reorder sections or clearly separate Windows-specific and Linux-specific instructions to avoid implying Windows is required.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation shows a moderate Windows bias. While it does mention Linux equivalents in a few places (e.g., Linux certificate path), most operational and troubleshooting guidance is Windows-centric. Examples and troubleshooting steps reference Windows certificate stores, Windows event logs, and Windows-specific APIs (e.g., Win32 CryptoAPI), with Linux alternatives only briefly mentioned or omitted. No Linux/macOS-specific troubleshooting or operational examples are provided.
Recommendations
  • Provide explicit Linux/macOS equivalents for certificate storage and retrieval (e.g., detail how Service Fabric on Linux locates and loads certificates, including file paths and permissions).
  • Add troubleshooting steps for Linux clusters, such as relevant log file locations, commands to inspect certificates (e.g., using openssl or Linux file system paths), and how to check for private key accessibility.
  • When referencing Windows event logs or APIs, include analogous Linux/macOS methods (e.g., syslog, journald, or Service Fabric logs on Linux).
  • Where possible, show both Windows and Linux configuration examples side by side, or clearly indicate when a step is platform-specific.
  • Clarify any differences in certificate provider support or limitations on Linux/macOS (e.g., CAPI1/CNG equivalents, if any).
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash scripting alternatives. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently presented, sometimes before or instead of cross-platform options, indicating a Windows-first bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all operations (add, remove, scale, configure placement properties, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
  • Where possible, provide Bash scripting or REST API examples to further increase platform parity.
  • Review the order of examples to avoid consistently presenting Windows tools first unless there is a technical reason.
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 provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is used exclusively for scripting examples, and the Key Vault VM extension discussed is Windows-specific. The documentation references Windows certificate store concepts and S-channel APIs, and troubleshooting steps are given only in PowerShell. There is no mention of Linux-specific certificate provisioning tools, scripting, or VM extensions, nor are Linux/macOS examples provided. Windows terminology and mechanisms are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS scripting examples (e.g., Bash, Azure CLI) for certificate enrollment and management.
  • Clarify which mechanisms (such as Key Vault VM extension) are Windows-only, and provide Linux alternatives (e.g., Azure CLI, custom scripts, or Linux VM extensions).
  • Mention Linux certificate store locations and how Service Fabric on Linux nodes handles certificate provisioning and autorollover.
  • Include troubleshooting steps for Linux clusters, using relevant tools and commands.
  • Where possible, present cross-platform guidance or explicitly state platform limitations.
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 on Azure Service Fabric Managed Clusters, with Windows terminology and PowerShell examples shown. While Linux is referenced in links and image creation, the main content and examples are Windows-centric, and the PowerShell command for role assignment is provided without a Linux CLI equivalent.
Recommendations
  • Add explicit Linux-focused examples and clarify Linux support for custom images in Service Fabric Managed Clusters.
  • Provide Azure CLI commands for role assignment alongside PowerShell examples.
  • Include ARM template snippets or guidance for deploying Linux-based custom images, if supported.
  • Clarify in the introduction whether Linux node types are supported, and if so, provide parity in instructions and examples.
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_first ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell command examples for migration steps, especially in the 'Basic SKU' scenario, without offering equivalent CLI or Bash examples. The PowerShell examples are presented as the only option for resource deployment and node management, which creates friction for Linux/macOS users. Additionally, the sample template for Ubuntu clusters is referenced, but no Linux-native command-line instructions are given. Windows/PowerShell patterns are mentioned first and exclusively in critical migration steps.
Recommendations
  • Add Azure CLI or Bash script equivalents for all PowerShell examples, especially for resource deployment, node disabling, and removal.
  • Explicitly note that PowerShell commands can be run cross-platform via Azure Cloud Shell, but provide native CLI/Bash alternatives for Linux/macOS users.
  • Where sample templates reference Ubuntu, include Linux-native instructions for deployment and cluster management.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
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 ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for RunToCompletion semantics in Azure Service Fabric presents Windows container examples exclusively, references Windows-specific container images, and uses Windows command syntax (cmd.exe) in all code samples. Querying deployment status is demonstrated only via PowerShell and C# APIs, with no mention of Linux tools or Bash equivalents. There is no guidance or example for Linux containers, Linux command syntax, or querying from Linux environments.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux command syntax (bash/sh) in ServiceManifest.xml.
  • Provide guidance for querying deployment status from Linux environments, such as using Azure CLI, Bash scripts, or REST APIs.
  • Clarify RunToCompletion support for Linux containers and guest executables, including any limitations or differences.
  • Present Linux examples alongside Windows examples, or indicate if RunToCompletion is Windows-only.
  • Include links or references to Linux container documentation for Service Fabric.
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 manifest files. It explicitly recommends opening the Service Fabric XSD schema file in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and does not mention Linux or cross-platform alternatives for schema validation or authoring manifests. The only tool and workflow described for authoring manifests is Windows/Visual Studio-centric, and this guidance appears before any mention of Linux or cross-platform options (which are not mentioned at all).
Recommendations
  • Provide instructions or recommendations for validating and authoring Service Fabric manifest files on Linux/macOS, such as using cross-platform editors (e.g., VS Code with XML extensions) and how to obtain the XSD schema file on non-Windows systems.
  • Clarify where the schema file can be found or downloaded for Linux/macOS environments.
  • Mention cross-platform tools for XML validation and intelli-sense, or link to relevant resources.
  • Ensure that any file paths or tool recommendations are either cross-platform or alternatives are given for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation frequently references PowerShell cmdlets for Service Fabric operations, often listing them before or alongside .NET API and REST options. There is a lack of explicit Linux/CLI examples, and no mention of Linux-specific tools or workflows. While REST and .NET APIs are cross-platform, the prominence of PowerShell and absence of Linux CLI (sfctl) usage or examples creates friction for Linux/macOS users.
Recommendations
  • Add explicit sfctl (Service Fabric CLI) command examples for each major operation (deploy, upgrade, remove, test, etc.), especially in sections currently listing only PowerShell.
  • Where PowerShell is referenced, clarify its Windows-specific nature and provide Linux/macOS alternatives.
  • Reorder examples so that cross-platform tools (REST, sfctl) are listed before or alongside Windows-specific tools.
  • Include links or references to Linux/macOS documentation and workflows for Service Fabric application lifecycle management.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and detail. PowerShell and Visual Studio are discussed first and in greater depth, with SFCTL (the cross-platform CLI) relegated to a later section. Parameter tables and examples are more detailed for PowerShell/Visual Studio, and Windows tools are referenced before Linux equivalents. There are no explicit Linux/macOS command examples or screenshots, and SFCTL/Linux is not given equal prominence.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/REST) are presented before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equivalent parameter tables and usage examples for SFCTL and REST, matching the detail given to PowerShell/Visual Studio.
  • Add explicit Linux/macOS command-line examples and clarify which tools are cross-platform.
  • Where possible, use neutral language (e.g., 'using PowerShell, Visual Studio, or SFCTL') instead of always listing Windows tools first.
  • Ensure that 'Next steps' and tutorial links for Linux/SFCTL are given equal prominence and not listed after Windows tutorials.
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 covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there are several instances where Windows tools, terminology, and examples are presented first or in greater detail. Windows-specific tools (Event Log, ETW, EventStore APIs) are mentioned before Linux equivalents, and Linux configuration details are sometimes referenced only via links. Some sections lack explicit Linux examples or guidance, especially for platform diagnostics and agent setup.
Recommendations
  • Ensure Linux monitoring tools and patterns are described with equal detail and prominence as Windows equivalents.
  • Add explicit Linux-focused examples and walkthroughs for configuring diagnostics, collecting logs, and querying events (not just links to other pages).
  • When mentioning Windows tools (e.g., Event Log, ETW), immediately provide Linux alternatives (e.g., LTTng, Syslog) and clarify differences in workflow.
  • In summary/setup sections, list Linux options alongside Windows, rather than focusing on Windows tools first.
  • Expand Linux agent setup instructions and provide sample queries or troubleshooting steps for Linux clusters.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation covers Azure Service Fabric application security in a generally platform-agnostic manner, but several sections show Windows bias. Windows-specific tools and concepts (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned before or instead of Linux equivalents. Some examples and links are Windows-centric, and Linux guidance is sometimes missing or relegated to brief mentions. Disk encryption for Linux clusters is noted as a TODO, indicating incomplete Linux parity.
Recommendations
  • Add explicit Linux examples and guidance for securing Service Fabric applications, including disk encryption and user account management.
  • Ensure Linux-specific tools and patterns (e.g., Linux user/group management, certificate handling, disk encryption with dm-crypt/LUKS) are documented alongside Windows equivalents.
  • Provide parity in examples, such as showing both Windows and Linux approaches for configuring security principals, running services under different accounts, and managing secrets.
  • Complete the TODO section for 'Encrypt disks on Linux clusters' with concrete instructions.
  • Review all sections for Windows-first ordering and ensure Linux options are presented equally.
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 all upgrade operations, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All code examples and walkthroughs use PowerShell syntax, and references to Visual Studio (a Windows-centric IDE) are prominent. There is no guidance for Linux/macOS users on how to perform these tasks using Azure CLI, REST API, or other cross-platform tools.
Recommendations
  • Add Azure CLI or REST API examples for key operations (creating/upgrading/removing services, application upgrades, rollbacks).
  • Explicitly mention whether PowerShell cmdlets are available cross-platform (e.g., via PowerShell Core) or if alternatives exist for Linux/macOS users.
  • Provide links to documentation for Linux/macOS users, or add a section outlining upgrade workflows for non-Windows environments.
  • Include sample scripts or commands for Bash or Azure CLI where possible.
  • Clarify any Windows-only limitations for Service Fabric management tools, and suggest workarounds or alternatives.
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 a notable Windows bias. PowerShell is the only CLI example provided, and Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are referenced exclusively. There are no Linux or cross-platform CLI examples (such as Azure CLI or Service Fabric CLI), and Windows terminology and tools are mentioned first and throughout. This creates friction for Linux/macOS users, who may not have access to PowerShell or http.sys and may need to find alternative methods.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or Azure CLI for application upgrades.
  • Clearly indicate which features or steps are Windows-only, and provide Linux/macOS alternatives where possible.
  • Include guidance for Linux/macOS users on how to retrieve application parameters and perform upgrades.
  • Mention cross-platform considerations for HTTPS endpoints, such as how certificate management differs on Linux.
  • Balance references to PowerShell with references to other tools or APIs (e.g., REST API, sfctl).
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows environments. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The REST API is only demonstrated via PowerShell scripts, and Windows-specific certificate handling is referenced. No Linux or macOS equivalents are mentioned, and PowerShell is assumed throughout.
Recommendations
  • Add Bash/curl examples for REST API calls, including certificate handling for Linux/macOS.
  • Mention cross-platform alternatives to PowerShell for interacting with Service Fabric APIs.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available or supported on PowerShell Core (pwsh) for Linux/macOS.
  • Provide guidance for Linux/macOS users on connecting to clusters and authenticating (e.g., using OpenSSL, curl, or Azure CLI).
  • Explicitly state if certain steps are Windows-only, and offer Linux/macOS alternatives where possible.
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 ⚠ī¸ missing_linux_example
Summary
The documentation provides several manual scaling instructions that rely exclusively on PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux/macOS equivalents or cross-platform alternatives. There are no CLI or REST API examples for these critical operations, and no guidance for Linux users on how to perform these tasks, which creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell-based instructions, especially for node disablement and removal.
  • Explicitly mention if certain operations must be performed from a Windows environment, and provide workarounds or alternatives for Linux/macOS users.
  • Where possible, reference Service Fabric cross-platform tools (e.g., sfctl) and provide example commands.
  • Clarify platform requirements in each section that uses platform-specific tooling.
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 ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for key security tasks, such as certificate creation and secret encryption, but Windows examples (PowerShell) are often presented first and in greater detail. Windows-specific tools and features (Windows Defender, PowerShell commands, DSC, Windows security baselines) are mentioned exclusively or before Linux equivalents. Some sections (Windows Defender, DSC) are Windows-only by nature, but others (like secret encryption) could improve parity by balancing example order and detail.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate which comes first to avoid 'windows_first' bias.
  • Where possible, provide Linux equivalents for Windows tools (e.g., mention Linux antivirus solutions or baseline tools if relevant).
  • Clarify when sections are Windows-only and provide links to Linux alternatives or note their absence.
  • Ensure Linux examples are as detailed and prominent as Windows examples, especially in critical workflows (e.g., secret encryption).
  • Add explicit notes when a feature or tool is not available on Linux, and suggest best practices for Linux users.
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 consistently provides PowerShell examples for configuring Service Fabric placement policies, but does not offer equivalent Linux/macOS CLI (e.g., sfctl) or REST API examples. All code snippets for service configuration use PowerShell, and PowerShell is presented immediately after C# code, with no mention of Linux-native tools or cross-platform alternatives. This creates friction for Linux/macOS users who cannot use PowerShell natively and must seek out alternative methods.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and supported on Linux/macOS.
  • Include REST API examples for placement policy configuration, as these are platform-agnostic.
  • Clearly indicate which tools are Windows-only and provide guidance for Linux/macOS users on equivalent workflows.
  • Consider reordering examples so that cross-platform methods (sfctl, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page primarily describes Service Fabric's periodic backup configuration in a platform-neutral way, but when discussing file share backup storage, it exclusively references Windows-style file shares (\\StorageServer\BackupStore) and Integrated Windows Authentication. No Linux or SMB/NFS examples or guidance are provided for non-Windows clusters or file share setups. There are no PowerShell or Windows-first command examples, but the file share section assumes a Windows environment.
Recommendations
  • Add guidance or examples for configuring file share backup storage using SMB/NFS on Linux clusters, including path formats and authentication methods.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide Linux-specific instructions.
  • Mention any limitations or alternatives for Linux/macOS users regarding file share storage.
  • If only Windows file shares are supported, explicitly state this to avoid confusion for Linux users.
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 is used for advanced operations (e.g., cluster upgrades) without Linux/bash equivalents. Windows-specific configuration (e.g., registry keys, Windows Update settings) is discussed in detail, while Linux-specific instructions for comparable scenarios are missing. The order of presentation and focus on Windows tools and patterns may create friction for Linux/macOS users.
Recommendations
  • For every PowerShell example, provide a bash/Azure CLI equivalent where possible, especially for advanced operations like cluster upgrades.
  • When discussing OS-specific configuration (e.g., disabling automatic updates), include Linux equivalents (such as disabling unattended-upgrades or using cloud-init for Linux VMs).
  • Clarify when a step or configuration is Windows-only, and provide parallel Linux guidance or explicitly state if not applicable.
  • Balance the order of examples (e.g., alternate between Windows and Linux, or present both together) to avoid a 'Windows-first' impression.
  • Link to Linux-specific documentation or scripts where available, especially for cluster management and upgrades.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. There is no mention of Linux-compatible tools or workflows, which creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API examples for application management tasks, which are platform-agnostic.
  • Explicitly mention whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core) or if they are Windows-only.
  • Provide Bash or shell script examples where applicable.
  • Clarify any platform restrictions for Service Fabric management tools.
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 detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and manifest examples, but there is no mention of Linux-native tooling or cross-platform CLI options. Additionally, PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation does note that resource monitoring is supported for containerized applications on Linux, but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Bash or Azure CLI examples for configuring scaling policies, especially for Linux users.
  • Explicitly mention cross-platform alternatives to PowerShell for managing Service Fabric clusters (e.g., Azure CLI, REST API).
  • Clarify which PowerShell commands are available on Linux (if any), or provide guidance for Linux users.
  • Consider including a note or section for Linux/macOS users outlining recommended tools and workflows.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml with <WindowsServer> and PowerShell examples) and cross-platform (ClusterConfig.json) configuration examples. However, Windows terminology and tools (such as PowerShell and WindowsServer XML blocks) are presented first and more prominently. PowerShell is the only CLI example shown; there are no Linux shell or cross-platform CLI examples. The documentation does not mention Linux-specific Service Fabric node configuration or provide parity for Linux CLI usage.
Recommendations
  • Add explicit Linux configuration examples (e.g., using ClusterManifest.xml with <Linux> blocks or referencing Linux node types if supported).
  • Provide cross-platform CLI examples, such as Azure CLI or Bash equivalents, alongside PowerShell.
  • Clarify which configuration files and approaches are applicable to Linux clusters and which are Windows-only.
  • If Service Fabric supports Linux nodes, include Linux-specific guidance and examples for cluster description and resource management.
  • When showing code samples, alternate the order or explicitly state applicability to Windows or Linux environments.
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 code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. PowerShell commands are presented as the main scripting interface for service creation and metric management, 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 service creation and metric configuration, as Azure CLI is cross-platform.
  • Mention and provide Bash script examples where applicable.
  • Clarify whether PowerShell Core (which is cross-platform) is supported for these commands, and if so, provide guidance.
  • Explicitly state if certain operations are only possible via PowerShell, and suggest workarounds or alternatives for Linux/macOS users.
  • Consider linking to documentation on using Service Fabric tools from Linux/macOS environments.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# API examples are cross-platform, but scripting and command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for managing node tags and service requirements, especially for Linux/macOS users.
  • Clearly indicate whether PowerShell commands are supported on Linux (PowerShell Core), and provide bash alternatives if not.
  • Consider presenting CLI examples before or alongside PowerShell to ensure platform parity.
  • Explicitly mention cross-platform options for cluster management tasks.
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 primarily references Windows tools and PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or providing cross-platform examples. There is an implicit assumption that the user is operating in a Windows environment, and no guidance is given for Linux-based standalone clusters, which Service Fabric supports.
Recommendations
  • Add examples and instructions for scaling standalone clusters on Linux, including relevant CLI commands or scripts.
  • Mention cross-platform tools (such as Service Fabric CLI or REST APIs) where possible, and clarify which steps are Windows-specific.
  • Provide links to Linux-specific documentation or note any limitations for Linux clusters.
  • Where PowerShell is referenced, offer Bash or shell script alternatives for Linux users.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-specific syntax and paths (e.g., 'PS C:\Users\User >'), without offering equivalent Linux/macOS CLI examples or mentioning cross-platform tools. The use of PowerShell and Windows paths is presented as the default method for interacting with Service Fabric, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention that PowerShell is one option, and provide guidance for Linux/macOS users on how to perform the same tasks.
  • Include sample commands for querying partition health using sfctl or REST APIs.
  • Clarify any platform-specific requirements for management tasks, and link to cross-platform tooling documentation.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric MoveCost, but does not include any Linux-native CLI (e.g., Azure CLI, Bash) examples. PowerShell is a Windows-centric tool, and its exclusive use for command-line examples creates friction for Linux/macOS users. There is no mention of Linux equivalents or cross-platform tools for these operations.
Recommendations
  • Add Azure CLI examples for creating and updating Service Fabric services with MoveCost, if supported.
  • If PowerShell is required, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide guidance for non-Windows users.
  • Explicitly mention if certain operations are only possible via PowerShell or C# SDK, and provide alternatives or workarounds for Linux/macOS users if available.
  • Consider including REST API examples, which are platform-agnostic, for service creation and MoveCost updates.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. PowerShell is presented as the primary scripting interface, and there is no reference to cross-platform tools or Azure CLI. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only.
  • Mention and provide guidance for Linux/macOS users, including supported tools and workflows.
  • If PowerShell is required, explicitly state its cross-platform availability or alternatives.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits a Windows bias. References and links are primarily or exclusively to Windows-specific guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md', and 'service-fabric-patch-orchestration-application.md' which is Windows-only). There is no mention of Linux-based standalone clusters, nor are there examples or instructions for Linux users. The patch orchestration application is only described for Windows. This creates friction for users managing Linux-based Service Fabric clusters.
Recommendations
  • Add explicit guidance or links for upgrading and configuring Linux-based standalone clusters, if supported.
  • Clarify in the introduction whether standalone clusters are Windows-only or if Linux is supported, and provide parity in documentation if so.
  • If patch orchestration or other features are Windows-only, clearly state this and provide Linux alternatives or workarounds where possible.
  • Include Linux-specific examples, commands, and configuration file references alongside Windows instructions.
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, but it exhibits Windows bias in several areas. References to PowerShell and Windows-specific tools are made without equal mention of Linux equivalents. For example, certificate management and port opening are described as possible via 'PowerShell/Azure CLI', but PowerShell is listed first and no explicit Linux/bash examples are provided. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node upgrade information. There are no explicit Linux/macOS command examples or guidance, and Windows terminology (e.g., NTLM, FileStoreService) is referenced without clarifying Linux applicability.
Recommendations
  • Provide Linux/bash command examples alongside PowerShell examples for certificate management, port opening, and other cluster operations.
  • Clarify whether features like Patch Orchestration Application (POA) and NTLM settings are Windows-only, and if so, provide equivalent Linux guidance or explicitly state Linux limitations.
  • Add links or sections for upgrading Linux node OS images in Service Fabric clusters, if supported.
  • Use neutral language when referencing tools (e.g., 'Azure CLI or PowerShell') and avoid listing Windows tools first unless Windows is the primary platform.
  • Explicitly state platform applicability for each feature or operation.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for securing an Azure Service Fabric cluster exhibits moderate Windows bias. Windows Server clusters and Windows authentication methods are mentioned explicitly and repeatedly, often before or instead of Linux equivalents. References to Windows certificate services, Windows security, and Windows-specific tools (e.g., MakeCert.exe) are present, while Linux-specific guidance, examples, or tools are largely absent. The concept of Linux clusters is acknowledged, but actionable instructions or links for Linux users are missing.
Recommendations
  • Add explicit guidance and links for securing standalone Service Fabric clusters running on Linux, including certificate management and authentication methods.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL instead of MakeCert.exe).
  • Mention Linux tools and patterns (such as Linux account management or integration with Linux-native identity providers) where relevant.
  • Ensure parity in documentation structure, so Linux instructions are given equal prominence and detail as Windows instructions.
  • Clarify which security scenarios and features are supported on Linux clusters, and highlight any differences or limitations.
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 notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource), with no mention of Azure CLI equivalents or Linux/macOS-friendly instructions. Application packaging is described using Visual Studio, a Windows-centric tool, and directory paths use Windows-style notation. There are no Linux/macOS alternatives or examples provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands) instead of only Visual Studio.
  • Show directory paths in both Windows and Linux/macOS formats.
  • Mention that all steps can be performed from Linux/macOS and link to relevant cross-platform tooling documentation.
  • Consider including screenshots or guidance for non-Windows environments where 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 for Azure Service Fabric Events demonstrates a Windows bias by primarily referencing Windows Event logs, ETW, and the Windows Azure diagnostics agent as the default mechanisms for event access and monitoring. There are no explicit examples or guidance for Linux-based Service Fabric clusters, nor are Linux-native tools or log locations mentioned. Windows-specific tools and patterns are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including log locations and supported monitoring tools.
  • Mention Linux equivalents to ETW/Windows Event logs, such as syslog or other logging mechanisms.
  • Provide examples or links for configuring diagnostics and event collection on Linux clusters.
  • Clarify which instructions are Windows-specific and provide Linux alternatives where possible.
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 is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic.
  • Mention that PowerShell is Windows-specific and provide guidance for Linux/macOS users on alternative tools.
  • Ensure future examples are provided for both Windows and Linux/macOS environments, or reference platform-neutral methods first.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there are several instances where Windows-specific tools, services, and examples are mentioned first or exclusively, such as references to PowerShell cmdlets, Windows services (FabricHost.exe), and standalone cluster creation only for Windows. Linux equivalents are sometimes mentioned, but often after Windows, and some features (like standalone clusters) are not supported on Linux. The documentation does not consistently provide Linux parity in examples or tooling references.
Recommendations
  • Ensure Linux tools and examples (such as Bash, Linux CLI usage) are presented alongside or before Windows/PowerShell equivalents.
  • Clarify which features are Windows-only and which are cross-platform, especially in sections referencing tools or services.
  • Add explicit Linux examples for cluster management, health queries, and lifecycle operations using sfctl or Bash scripts.
  • Highlight Linux support in programming models and container orchestration, with links to Linux-specific guides.
  • Update 'Next steps' to include Linux cluster creation and management resources, or clearly state Linux limitations.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced as being installed in a Windows-specific directory (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd), and examples use .exe file extensions, which are Windows-centric. There are no explicit Linux/macOS packaging examples, directory paths, or tool references. Visual Studio is mentioned as a packaging option, which is primarily Windows-focused, and no Linux alternatives (such as cross-platform CLI tools) are highlighted.
Recommendations
  • Provide Linux/macOS equivalent paths and instructions for locating schema files.
  • Include examples using Linux/macOS executables (e.g., .sh, ELF binaries) alongside .exe.
  • Mention cross-platform command-line tools for packaging and deploying guest executables, and clarify Visual Studio alternatives for non-Windows users.
  • Add explicit notes or sections for Linux/macOS users, including any prerequisites or differences in packaging and deployment.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is generally OS-neutral in its explanations of Service Fabric activation and deactivation. However, the 'Next steps' section only links to PowerShell-based deployment/removal instructions, and the only explicit tooling reference for downloading a ServicePackage in advance points to a PowerShell cmdlet. There are no Linux CLI or cross-platform examples or links, and PowerShell is implicitly presented as the default tool.
Recommendations
  • Add links to equivalent Linux/macOS instructions for deploying and removing applications, such as Azure CLI or Service Fabric CLI (sfctl) guides.
  • When referencing tools for tasks like downloading ServicePackages, include cross-platform alternatives (e.g., sfctl, REST API) alongside PowerShell.
  • In the 'Next steps' section, provide parity by listing both PowerShell and CLI-based documentation.
  • Explicitly state when a tool or example is Windows-only, and suggest alternatives for Linux/macOS users.
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 and Visual Studio as primary tools for interacting with the ImageStoreConnectionString, and links to deployment instructions using PowerShell. While Service Fabric is cross-platform, the examples and guidance focus on Windows-centric tools and workflows, with no explicit mention of Linux/macOS equivalents or command-line tools (e.g., Bash, CLI).
Recommendations
  • Add examples and links for deploying and managing Service Fabric clusters using Azure CLI or Bash scripts, especially for Linux/macOS users.
  • Mention cross-platform tools and workflows where applicable, such as using REST APIs or .NET Core SDK on Linux/macOS.
  • Provide parity in documentation by referencing Linux/macOS development environments and their setup for Service Fabric.
  • Include instructions for retrieving the cluster manifest and configuring ImageStoreConnectionString using Linux/macOS tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but practical examples and tooling references are heavily skewed toward Windows and PowerShell. The only CLI example is a PowerShell command, and all links to operational tasks reference PowerShell modules. There is no mention of Linux-native tools (such as Bash, Azure CLI, or cross-platform Service Fabric CLI), nor are Linux/macOS-specific workflows or examples provided. This creates friction for Linux/macOS users, who must seek out equivalent commands or tools elsewhere.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples alongside PowerShell for service creation and management tasks.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users, including links to relevant documentation.
  • Include references to REST API usage with example curl commands for Linux/macOS users.
  • Ensure operational links (e.g., for querying service status, health, restarting code packages) include both PowerShell and CLI/REST alternatives.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable bias towards Windows/PowerShell workflows. PowerShell is mentioned first and in detail, while Linux/macOS equivalents (sfctl, install.sh) are referenced but not explained as thoroughly. Visual Studio and PowerShell scripts are emphasized, which are primarily Windows-centric tools.
Recommendations
  • Provide explicit Linux/macOS examples alongside PowerShell, such as detailed sfctl and install.sh usage.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Add sample scripts for parameter substitution in Linux environments (e.g., Bash, sed, or jq).
  • Ensure parity in documentation for both Visual Studio (Windows) and VS Code (cross-platform) workflows.
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 health reporting in Service Fabric using PowerShell and C#, but omits equivalent Linux/macOS CLI examples. PowerShell commands are shown prominently, and there is no mention of cross-platform tools (such as Azure CLI or Bash scripts) for health reporting. This creates friction for Linux/macOS users, as Service Fabric supports Linux clusters but the documentation does not demonstrate parity in tooling or examples.
Recommendations
  • Add examples using Azure CLI or Bash scripts for health reporting, where possible.
  • Explicitly mention whether PowerShell commands are available cross-platform (e.g., via PowerShell Core), or provide alternatives for Linux/macOS users.
  • Clarify any limitations or differences in health reporting APIs and tools between Windows and Linux Service Fabric clusters.
  • Provide REST API examples with curl commands, which are universally available on Linux/macOS.
  • Reorder examples so that REST or cross-platform CLI examples are shown before or alongside PowerShell examples.
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, but there are notable signs of Windows bias. The only explicit deployment command example uses PowerShell (New-ServiceFabricApplication) with a Windows-style path, and the Service Fabric SDK schema path is given only as a Windows location. Linux-specific notes are minimal and appear after Windows details. There are no Linux CLI or Bash examples for deploying applications or overriding parameters.
Recommendations
  • Add equivalent Azure CLI or Bash examples for deploying Service Fabric applications and passing parameters, especially for Linux users.
  • Mention the location of the Service Fabric schema file for Linux environments, or clarify if it is not applicable.
  • When referencing tools or commands, provide both Windows (PowerShell) and Linux (CLI/Bash) alternatives where possible.
  • Ensure Linux-specific notes (such as the certificate store path) are given equal prominence and not only as afterthoughts.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric manifest examples and explanations, but exhibits mild Windows bias. Windows concepts (such as local admin accounts, SYSTEM/NETWORKSERVICE accounts, .bat scripts, and references to ServiceFabric PowerShell) are mentioned or shown first, and no explicit Linux-specific examples or guidance are given. The manifest examples use Windows-centric terminology and tools (e.g., Setup.bat, VotingWeb.exe), and the only script example is a .bat file. There is a reference to using the ServiceFabric PowerShell module for service creation, with no mention of Linux CLI equivalents.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of .bat files in SetupEntryPoint.
  • Mention or link to Linux-compatible tools (e.g., Azure CLI, Service Fabric CLI) for application/service creation and management, alongside PowerShell.
  • Clarify which manifest settings and concepts are cross-platform, and which are Windows-specific (e.g., SYSTEM/NETWORKSERVICE accounts).
  • Provide sample manifests or guidance for Linux clusters, including user/group management and endpoint configuration.
  • Where possible, show both Windows and Linux examples side-by-side, or indicate differences in behavior.
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 ⚠ī¸ powershell_heavy
Summary
The documentation provides a balanced overview of both Windows-only (HTTP.sys) and cross-platform (Kestrel) web server options for ASP.NET Core in Service Fabric. However, Windows-specific tools and concepts (such as HTTP.sys, Windows HTTP Server API, netsh, and kernel driver details) are discussed in depth and often before Linux equivalents. Windows-specific configuration steps are prominent, and some examples reference Windows-only features. Kestrel (cross-platform) is recommended for most scenarios, but Windows tools and patterns are described first and in greater detail.
Recommendations
  • Ensure Linux/macOS-specific instructions are equally prominent, especially for port configuration and firewall management.
  • Add explicit notes or examples for Linux users (e.g., how to configure ports/firewall for Kestrel on Linux, troubleshooting tips).
  • Reorder sections so that cross-platform options (Kestrel) are discussed before Windows-only options (HTTP.sys) where possible.
  • Clarify which steps are Windows-only and provide alternative guidance for Linux/macOS users.
  • Include links to Linux/macOS documentation for Service Fabric and ASP.NET Core hosting.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and administrative APIs, with no mention of Linux equivalents or cross-platform CLI usage. All command examples and API references are Windows-centric, and PowerShell is presented as the primary interface for administrative operations. There are no examples or instructions for Linux/macOS users, nor is it clarified whether the APIs are accessible via other tools or languages.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) or REST APIs, which are cross-platform.
  • Clarify whether the administrative operations (remove/restore/query replica) can be performed on Linux clusters and how.
  • Provide equivalent instructions for Linux/macOS users, including sample commands and screenshots.
  • Explicitly state any platform limitations if certain features or APIs are Windows-only.
  • Mention FabricClient usage in languages other than .NET/PowerShell, if supported.
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 ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows and references PowerShell as the CLI example for service creation. There are no examples or guidance for Linux/macOS users, such as using cross-platform tools or CLI alternatives. The instructions and screenshots are all Visual Studio-centric, which is a Windows-only IDE.
Recommendations
  • Add instructions or examples for deploying Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where possible.
  • Clarify which steps are Visual Studio-specific and provide alternative workflows for Linux/macOS users, such as using command-line tools or VS Code.
  • Include sample commands for Linux/macOS environments, or explicitly state if certain features (like StartupServices.xml) are not available outside Visual Studio/Windows.
  • Mention the availability (or lack thereof) of Service Fabric SDK and tooling for Linux/macOS, and link to relevant documentation.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page for the Fault Analysis Service overview provides usage examples for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). No Linux-specific tools, CLI commands, or cross-platform scripting examples are mentioned. The PowerShell example is prominent, and PowerShell is primarily a Windows-centric tool, although it is available on Linux. There is no mention of Linux-native equivalents (such as Bash, Azure CLI, or REST API usage), nor is there guidance for Linux/macOS users.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform.
  • Mention PowerShell Core compatibility and clarify if the PowerShell module works on Linux/macOS.
  • Provide Bash or shell script examples for Linux users, if applicable.
  • Explicitly state platform requirements or limitations for the Fault Analysis Service and its tooling.
  • Ensure parity in documentation for Linux/macOS users by listing cross-platform tools before or alongside Windows-specific tools.
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
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 both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is a notable Windows bias in several areas. PowerShell examples are consistently present alongside CLI and REST, and in some sections (e.g., REST sample payloads), the extension type defaults to 'ApplicationHealthWindows' rather than 'ApplicationHealthLinux'. In the PowerShell section for installing the extension, only the Windows extension is shown, while the CLI example uses the Linux extension. There is no explicit parity table or clear guidance for Linux vs. Windows extension usage, and the PowerShell example is more detailed than the Bash example. Additionally, in some REST payloads, 'ApplicationHealthWindows' is used by default, which may confuse Linux users.
Recommendations
  • Ensure all sample code and REST payloads show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' values, or clarify when to use each.
  • Add explicit Linux (Bash) examples for installing the application health extension, not just for the response server.
  • Balance the detail level between Bash and PowerShell examples, ensuring Linux users have equally comprehensive guidance.
  • In REST and PowerShell sections, provide Linux-specific examples or note how to adapt for Linux VMSS.
  • Consider a parity table or section summarizing differences between Windows and Linux extension usage.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation covers backup and disaster recovery strategies for Azure Managed Disks on both Linux and Windows VMs. While most guidance is platform-neutral, there are instances where Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. The SQL Server backup section is Windows-centric, and application-consistent backup guidance is more detailed for Windows than Linux.
Recommendations
  • Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze, mention LVM snapshots, or other Linux-native solutions for application-consistent backups).
  • Include examples or links for Linux database backup and disaster recovery (e.g., Oracle, PostgreSQL, MySQL) alongside SQL Server.
  • When mentioning Windows tools (like Volume Shadow Service), immediately follow with Linux equivalents and clarify their limitations or differences.
  • Add links to Linux-specific documentation for backup and disaster recovery of common workloads.
  • Ensure parity in guidance for both OS types in tables and comparison sections.
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 ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
While the documentation covers both Windows and Linux VMs, there are several signs of Windows bias: PowerShell examples are always present and often detailed, ARM template and parameter defaults are Windows-centric, and Windows tools and patterns (like PowerShell and Windows image SKUs) are emphasized. Linux-specific details and parity in examples are lacking, especially in ARM templates and parameterization.
Recommendations
  • In ARM template examples, provide both Windows and Linux image options, or show how to parameterize for either OS.
  • When listing allowed values for parameters like OSVersion, include common Linux distributions (e.g., Ubuntu, CentOS) alongside Windows.
  • In PowerShell sections, clarify that PowerShell Core (pwsh) is cross-platform, or provide Bash/Cloud Shell alternatives where possible.
  • Ensure CLI examples use both Windows and Linux images (not just Ubuntu in CLI and Windows in ARM).
  • Add explicit notes or tabs for Linux-specific considerations or differences, if any.
  • Balance the order of examples so that CLI (cross-platform) is shown before PowerShell, or alternate the order.
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, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. Windows/PowerShell examples are shown before Linux equivalents in some sections, and PowerShell commands are used for ARM template deployment and feature registration without Linux/bash alternatives. The CLI examples use Ubuntu images, but the PowerShell examples default to Windows images, and the registration steps are only shown in PowerShell.
Recommendations
  • Add bash or Azure CLI equivalents for feature registration and ARM template deployment steps.
  • Ensure that Linux/CLI examples are presented before or alongside Windows/PowerShell examples in each section.
  • Provide PowerShell examples using Linux VM images, or clarify that PowerShell can be used cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide instructions for those platforms.
  • Add links or notes about using Azure Cloud Shell, which supports both Bash and PowerShell.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major steps, but the CLI examples consistently use Windows-centric defaults (e.g., Win2016Datacenter as the VM image, password authentication, and variable syntax). There are no explicit Linux-specific examples (such as using a Linux VM image or SSH authentication), and PowerShell is given equal prominence to Azure CLI, which may not be as relevant for Linux/macOS users. The documentation does not provide any Bash scripting or Linux-native command-line patterns, and all variable examples and VM creation scripts default to Windows VMs.
Recommendations
  • Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use Ubuntu or CentOS images, SSH authentication).
  • Clarify that Azure CLI commands are cross-platform and provide Bash-friendly variable syntax where appropriate.
  • Include at least one end-to-end example for deploying and attaching a Premium SSD v2 disk to a Linux VM.
  • In the PowerShell sections, clarify that these are primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • In the 'Next steps' section, ensure Linux and Windows parity in links and instructions.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure Managed Disks .../main/articles/virtual-machines/disks-shared-enable.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides parity between Azure CLI and PowerShell for all disk operations, but PowerShell examples are heavily featured and often shown before CLI examples. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. There are no Linux-specific examples or guidance, and PowerShell is referenced as a primary scripting option, which may create friction for Linux/macOS users.
Recommendations
  • Show Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes clarifying that Azure CLI is fully supported on Linux/macOS and is the recommended option for non-Windows users.
  • Include sample bash scripts or Linux shell usage where relevant (e.g., mounting disks, interacting with SCSI PR commands).
  • Consider adding links or references to Linux-specific disk management guidance, especially for clustered applications.
  • Reduce PowerShell-centric language and ensure CLI instructions are equally prominent.
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 for enabling Write Accelerator, with detailed step-by-step instructions and code. Azure CLI is covered, but with much less detail and fewer examples. The REST API section requires installation of 'armclient' via Chocolatey, a Windows-only package manager, and installation instructions are only for Windows (cmd.exe/PowerShell). There are no Linux-specific installation instructions for 'armclient', nor is there mention of Linux package managers or alternatives. Windows tools and patterns (PowerShell, Chocolatey) are mentioned exclusively or before Linux equivalents. However, the feature itself is cross-platform (Linux and Windows VMs), and Azure CLI and REST API methods are documented, so Linux users can complete the task with some friction.
Recommendations
  • Provide parity in example detail for Azure CLI, including full scripts for common scenarios (adding/enabling/disabling Write Accelerator disks).
  • For REST API/armclient, include installation instructions for Linux (e.g., via dotnet, manual download, or Linux package managers if available), or mention cross-platform alternatives.
  • Clarify that PowerShell examples are usable on Linux via Azure PowerShell (if true), or provide Bash/CLI equivalents.
  • Mention that Chocolatey is Windows-only and provide alternative installation methods for Linux/macOS users.
  • Where possible, show CLI examples before or alongside PowerShell to avoid Windows-first bias.
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 PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, the PowerShell example is presented first and in greater detail, and PowerShell is a Windows-centric tool. There is no explicit Bash or Linux shell scripting example, though Azure CLI is cross-platform. References to enabling customer-managed keys and double encryption in the prerequisites section link to PowerShell guides before CLI or Bash equivalents. There are no Linux-specific tools or workflows highlighted.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Add explicit Bash or shell scripting examples where possible, especially for automation scenarios.
  • Ensure that all prerequisite links include Azure CLI or Bash-based guides, not just PowerShell.
  • Clarify in the introduction that both Windows and Linux users can follow the CLI and Portal instructions equally.
  • Where PowerShell is referenced, note that it is available cross-platform, or provide a direct link to Azure CLI/Bash alternatives.
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 as a scenario for shared disks, linking to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA stacks). The proximity placement group link is also Windows-specific, and Windows clustering is mentioned before any Linux alternatives, suggesting a Windows-first bias.
Recommendations
  • Add references and links to Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility with Azure shared disks.
  • Clarify whether shared disks are supported for Linux-based clusters and provide any relevant limitations or guidance.
  • Update proximity placement group documentation links to include Linux VM scenarios, not just Windows.
  • Ensure examples and limitations are presented for both Windows and Linux environments where applicable.
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 (with 'AzCopy.exe' and Windows file paths), but does not offer a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and there is no mention of how to run AzCopy on Linux or macOS, nor are Linux file paths or shell usage demonstrated. The rest of the CLI examples are cross-platform, but the critical upload step is Windows-biased.
Recommendations
  • Add AzCopy command examples for Linux/macOS, using './azcopy' and typical Linux file paths (e.g., '/home/user/mydisk.vhd').
  • Clarify that AzCopy is available for Linux/macOS and provide download/install instructions or a link for those platforms.
  • Mention that the AzCopy syntax is the same across platforms, but file paths and executable names differ.
  • Consider showing both Windows and Linux/macOS examples side-by-side for the upload step.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.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, while focused on Linux VM disk encryption, presents PowerShell examples and tools prominently and extensively, often before or alongside Azure CLI and Linux-native commands. PowerShell is a Windows-centric tool, and its heavy usage may create friction for Linux users. The Azure CLI and OS-level Linux commands are provided, but PowerShell sections are longer, more detailed, and appear before CLI in several cases.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as CLI is more native to Linux environments.
  • Reduce the prominence and length of PowerShell sections, or clearly mark them as optional for users who prefer PowerShell.
  • Expand Linux OS-level command examples (e.g., using bash, lsblk, cryptsetup) to cover more verification scenarios.
  • Add a short note clarifying that PowerShell is optional and that Azure CLI is recommended for Linux users.
  • Where possible, provide parity in detail and output examples for Azure CLI and Linux commands, matching those given for PowerShell.
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_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder, but there is a notable Windows bias. PowerShell commands and Windows-specific tools (e.g., Get-FileHash) are frequently mentioned, often before their Linux equivalents. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but less emphasized. Some sections (e.g., restart customizer) explicitly state there is no Linux equivalent. SHA256 checksum generation is shown with PowerShell first, then Linux. In validation examples, Windows/PowerShell is presented before Linux/Shell. The documentation is usable for Linux users, but Windows patterns and tools are more prominent.
Recommendations
  • Ensure Linux examples and tools (e.g., sha256sum, wget/curl) are presented alongside or before Windows equivalents.
  • Provide more detailed Linux-specific customizer examples, including common patterns for Linux image customization.
  • Balance the order of examples so that Linux and Windows are equally represented, or alternate which comes first.
  • Where a feature is Windows-only (e.g., WindowsRestart customizer), explicitly state alternatives or workarounds for Linux users.
  • Include links to Linux troubleshooting and scripting resources, similar to Windows/PowerShell links.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is focused on running scripts in Azure Linux VMs, but it exhibits several Windows biases. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured and often presented before or alongside Azure CLI examples. Some explanations and sample scripts reference Windows-specific concepts (e.g., 'ipconfig', 'myscript.ps1', 'Secondary Logon' service) without clear Linux equivalents or clarification. REST API and ARM template examples use Windows-style scripts (PowerShell) and file extensions (.ps1) instead of Linux shell scripts (.sh), and there are missing Linux-specific examples for certain advanced scenarios (e.g., parameter passing, blob streaming, sequential execution).
Recommendations
  • Provide Linux shell script (.sh) examples in REST API and ARM template sections instead of or alongside PowerShell (.ps1) scripts.
  • Clarify when a command or parameter is Windows-only, and offer Linux equivalents where possible (e.g., replace 'ipconfig' with 'ifconfig' or 'ip a' for Linux).
  • Use Linux tools and patterns (e.g., az CLI, bash scripting, Linux file extensions) as the default or primary examples, especially since the page is Linux-focused.
  • Add explicit Linux-focused walkthroughs for advanced scenarios (e.g., streaming output to blobs, parameter passing, running as a different user) using Azure CLI and bash.
  • Ensure terminology and instructions are Linux-centric (e.g., referencing Linux user management, not Windows services like 'Secondary Logon').
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page on Service Fabric architecture briefly mentions PowerShell cmdlets and Windows security as part of the management and transport subsystems, respectively. PowerShell is referenced as a primary management tool, and Windows security is mentioned before X509 certificates in the transport subsystem. However, the overall content is conceptual and not focused on OS-specific implementation details.
Recommendations
  • When mentioning management tools, explicitly note Linux/macOS equivalents (e.g., Azure CLI, REST APIs) alongside PowerShell.
  • Clarify that Service Fabric management can be performed using cross-platform tools, not only PowerShell.
  • When discussing security, mention X509 certificates first or equally, and clarify that Linux clusters use X509 certificates for secure communication.
  • Add links or references to documentation for Linux/macOS management and security practices where relevant.
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 is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and no Linux/macOS-specific upgrade instructions or CLI examples are provided.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
  • Mention Visual Studio Code as a cross-platform IDE option alongside Visual Studio.
  • Ensure parity in upgrade tutorials by providing Linux/macOS-specific instructions or references.
  • Consider reordering 'Next steps' to avoid Windows tools appearing first unless they are most widely used.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell examples are included alongside CLI and REST, which is a Windows-centric tool. In most sections, PowerShell is presented after CLI, but its presence may signal a Windows bias. There are no Linux-specific shell examples (e.g., Bash), but the CLI examples are cross-platform. The documentation does not mention Windows tools or patterns exclusively, nor does it omit Linux equivalents for any critical step. However, PowerShell is included as a first-class option, which may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell scripting examples for Linux users, especially for resource group and gallery creation.
  • Explicitly state that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
  • If possible, provide links to Linux/macOS-specific guidance or troubleshooting.
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, with all core examples and instructions using Linux tools and commands. However, a single section at the end provides a PowerShell script for checking classic VM SKU support, without a Linux CLI equivalent. This is a minor instance of Windows bias.
Recommendations
  • Provide an Azure CLI or Bash equivalent for checking classic VM SKU support, or clarify if PowerShell is required for this specific operation.
  • If PowerShell is the only option, explicitly state that this step is Windows-specific and offer guidance for Linux users (e.g., using Azure Cloud Shell or PowerShell Core).
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides step-by-step instructions for configuring RBAC permissions using the Azure portal, which is a graphical interface equally accessible from Windows, Linux, and macOS. However, when mentioning SDKs for checking pool health via the Runtime View API, 'PowerShell' is listed before 'CLI', which may subtly prioritize Windows tools. No explicit PowerShell-only commands or Windows-specific tools are used, and all examples (REST API, Kusto query) are cross-platform.
Recommendations
  • When referencing SDKs, mention Azure CLI before PowerShell or list both equally to avoid subtle Windows prioritization.
  • Add explicit Azure CLI command examples alongside REST API calls for checking pool health, as CLI is widely used on Linux/macOS.
  • Consider including links or brief instructions for role assignment using Azure CLI or ARM templates, not just the portal.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in container image cleanup, and mentions Windows images before Linux equivalents. There are no explicit Linux-specific examples or references to Linux container base images, and the configuration examples focus on Windows-centric patterns.
Recommendations
  • Add examples or references for Linux container base images (e.g., 'mcr.microsoft.com/linux', 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
  • Clarify that the cleanup settings apply equally to Linux containers, if applicable.
  • Provide guidance or examples for Linux users, such as mentioning common Linux container images and any relevant differences in behavior.
  • Ensure parity in documentation by listing Linux and Windows images together, or by providing Linux-first examples where appropriate.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology (e.g., certificate store names like 'My', NTLM authentication, references to Windows Defender Firewall, and default paths like 'd:\svcfab') appear throughout. Windows concepts (such as updating ClusterConfig.json for standalone clusters) are mentioned before Linux equivalents, and some settings (e.g., NTLM, Windows Update, log file paths) are Windows-centric. There are few explicit Linux examples or guidance, and Linux-specific settings are less visible or explained.
Recommendations
  • Add explicit Linux equivalents for settings and paths (e.g., certificate store locations, log/data root directories, firewall configuration).
  • Provide Linux-specific guidance where Windows tools or terminology are used (e.g., clarify how certificate management works on Linux, mention Linux firewall options).
  • When referencing standalone cluster upgrades, mention Linux configuration files and procedures alongside Windows (not just ClusterConfig.json).
  • Ensure Linux settings (such as /var/lib/waagent, /usr/bin/, etc.) are explained and visible in relevant sections.
  • Where Windows-only features are described (e.g., NTLM, Windows Update), clearly state if Linux is not supported, and offer Linux alternatives if available.
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 cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, the PowerShell (Windows) workflow is presented first and in more detail, which may give the impression of a Windows-first bias. The CLI examples are present and sufficient for Linux/macOS users, but are listed after the PowerShell section.
Recommendations
  • Present the cross-platform CLI (sfctl) examples before the PowerShell examples, or clarify that sfctl is recommended for Linux/macOS users.
  • Explicitly state that sfctl is supported on all platforms and provide installation links for Linux/macOS.
  • Ensure parity in the level of detail and explanation between PowerShell and CLI sections.
  • Add a short note at the start of the examples section indicating which tools are cross-platform and which are Windows-only.
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 is a mild bias toward Windows. Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in more detail than Linux (just 'Docker'), and Windows scenarios (IIS lift and shift) are described first in the 'Scenarios for using containers' section. However, Linux quickstarts and tutorials are also prominently linked, and Linux container support is clearly documented.
Recommendations
  • Expand the description of Linux container runtimes beyond just 'Docker' (e.g., mention containerd if relevant).
  • Provide a Linux-specific scenario example in the 'Scenarios for using containers' section, such as migrating an Apache/Nginx web app.
  • Ensure parity in detail between Windows and Linux container support (e.g., repository authentication, networking modes, etc.).
  • Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
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 terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in some sections. For example, the description of nodes references an 'auto-start Windows service, FabricHost.exe', and code packages are described as containing 'EXE/DLL files'. Linux equivalents are not explicitly mentioned or described in parallel. However, the page does acknowledge Linux support in several places, such as mentioning Docker containers on Linux and guest executables running on Windows or Linux.
Recommendations
  • Where Windows-specific tools or terminology are mentioned (e.g., FabricHost.exe, EXE/DLL files), add equivalent Linux information (e.g., Linux service/daemon, ELF binaries).
  • When describing node startup, clarify how Service Fabric runs on Linux nodes (e.g., systemd services, relevant Linux processes).
  • Ensure examples and descriptions consistently reference both Windows and Linux, especially in sections about code packages, executables, and node management.
  • Consider alternating the order of Windows and Linux mentions, or grouping them together to emphasize parity.
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 Azure Service Fabric, and provides parity in describing development environments and SDKs. However, in the 'Any OS, any cloud' section, Windows development is mentioned first, with Visual Studio and PowerShell highlighted, while Linux development is described second. The quickstart link also points to a .NET (likely Windows-centric) guide, rather than a Linux or cross-platform example.
Recommendations
  • Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) development.
  • Explicitly mention cross-platform tools and workflows where possible.
  • Ensure examples and guides are available for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_only
Summary
The documentation explicitly states that Linux is not yet supported for standalone Service Fabric clusters. All supported operating systems listed are Windows Server editions. While the introduction mentions Service Fabric can run on Windows Server and Linux, the rest of the page and the supported OS section clarify that this specific scenario (standalone clusters) is Windows-only.
Recommendations
  • Clarify earlier in the document (e.g., in the introduction) that standalone clusters are currently Windows-only, to avoid confusion from the initial mention of Linux.
  • Once Linux support is available, update the documentation to include Linux-specific instructions, examples, and supported OS listings.
  • If there are alternative Linux deployment options (e.g., managed clusters), provide links or references to those.
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, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and Windows-specific extension names (e.g., ApplicationHealthWindows) are used in PowerShell examples. Portal instructions are platform-neutral, but PowerShell is given equal prominence to CLI, and PowerShell examples use Windows-centric extension types, while CLI examples use Linux-centric types. The ordering of tabs sometimes puts PowerShell before CLI, and Windows tools are referenced throughout.
Recommendations
  • Ensure that Linux and macOS users are equally supported by providing Bash shell examples where relevant, especially for scripting tasks.
  • Clarify that Azure PowerShell can be used cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
  • In PowerShell examples, explain the difference between ApplicationHealthWindows and ApplicationHealthLinux extensions, and provide both where applicable.
  • Consider ordering CLI examples before PowerShell, or explicitly stating that CLI is recommended for Linux/macOS users.
  • Add a note about cross-platform compatibility for Azure CLI and PowerShell, and link to installation guides for Linux/macOS.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally alongside CLI and is referenced in every section. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users, especially since Azure CLI is cross-platform. In some sections, PowerShell is listed after CLI, but its presence throughout the page is notable. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI examples are sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding Bash shell script examples for common operations, or explicitly mention that Azure CLI commands work on Linux/macOS.
  • If PowerShell is included, note that it is available cross-platform (PowerShell Core), but most Linux users will prefer Azure CLI.
  • Ensure that CLI examples are always shown first, or provide a clear parity statement.
  • Add a brief section or note for Linux/macOS users about tool choice and compatibility.
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 examples are often presented before CLI examples, and some sections (such as querying public IPs) give more detailed PowerShell guidance. There is a slight preference for Windows/PowerShell tools, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present CLI and PowerShell examples side-by-side or in a consistent order (e.g., CLI first, then PowerShell) to avoid perceived Windows-first bias.
  • Ensure all PowerShell examples have equivalent CLI examples, especially for querying and managing resources.
  • Explicitly mention that Azure CLI commands work cross-platform (Linux, macOS, Windows) to reinforce parity.
  • Where possible, add Bash shell script examples for advanced scenarios to further support Linux users.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation covers automatic OS image upgrades for Azure Virtual Machine Scale Sets and is intended for both Windows and Linux users. It provides examples for REST API, Azure PowerShell, Azure CLI, ARM templates, and Bicep. However, PowerShell examples are presented before CLI examples throughout, and ARM template snippets default to Windows images. Some minor references to Windows-specific properties (e.g., enableAutomaticUpdates) are necessary for Windows VMs but are not flagged as bias. Overall, Linux parity is maintained, but Windows tools and patterns are shown first, which may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • In ARM template and Bicep snippets, use a Linux image as the default example or provide parallel examples for both Windows and Linux.
  • Explicitly state that all examples (PowerShell, CLI, ARM, Bicep) work for both Windows and Linux scale sets unless otherwise noted.
  • Where referencing Windows-specific properties, clarify their relevance and provide equivalent Linux guidance if applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Update scale set to add availability zones'), PowerShell is presented before REST API and after CLI. There is a slight 'windows_first' bias in listing PowerShell as a primary method alongside CLI, and the PowerShell example uses Windows-specific syntax. The Resource Manager template section references both Linux and Windows getting started articles, but overall, Linux-specific shell examples (e.g., Bash) are not provided, nor are there explicit notes about Linux/macOS compatibility for CLI commands.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Add Bash shell examples or clarify that CLI commands can be run in Bash, zsh, or other Linux shells.
  • Consider listing CLI examples before PowerShell in all sections to reinforce Linux parity.
  • Add notes about PowerShell being Windows-centric and recommend CLI for Linux/macOS users.
  • Ensure that any screenshots or UI references are not Windows-specific.
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 before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with comparable detail, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell equally, without favoring Windows tools.
Recommendations
  • Present Linux and Windows operating system support in parallel or alphabetical order to avoid implicit prioritization.
  • Consider merging the OS support sections or using a table for parity.
  • Ensure future updates include Linux-specific examples or troubleshooting if Windows-specific guidance is added.
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 and explicitly states applicability to both. However, there is a mild bias in the ordering of examples and links: Windows/PowerShell resources are consistently mentioned before Linux/CLI equivalents throughout the page, and PowerShell is referenced in some guidance (e.g., revoking access) before CLI. No critical functionality is Windows-only, and Linux users are provided with equivalent instructions and links.
Recommendations
  • Alternate the order of Windows/PowerShell and Linux/CLI links and examples, or list them together without preference.
  • Where possible, provide cross-platform command examples side-by-side (PowerShell and Bash/CLI).
  • Ensure references to tools (e.g., Azure Key Vault PowerShell and CLI) are presented with equal prominence.
  • Review for any subtle language implying Windows as the default or primary platform.
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 examples for enabling on-demand disk bursting using the Azure portal, PowerShell, Azure CLI, and ARM templates. The PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool. The CLI section is present and covers Linux/macOS parity, but PowerShell is mentioned before CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. There is minor bias in the ordering and emphasis on PowerShell.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
  • Add a Bash shell example for invoking Azure CLI, or clarify that CLI commands are suitable for Bash/terminal users.
  • Ensure that references to Azure Cloud Shell highlight its availability for both Bash and PowerShell environments.
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 links and examples for both Azure PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. This creates a mild Windows bias, as Linux users may prefer CLI or need explicit Linux instructions.
Recommendations
  • Add a link to a Linux/CLI-based guide for creating custom RBAC roles, or clarify that the process is identical in CLI.
  • Ensure CLI examples and links are presented alongside or before PowerShell examples, especially in sections relevant to both platforms.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, provide sample commands for both PowerShell and CLI in critical configuration steps.
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 CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples. References to PowerShell are frequent, and in some sections (such as role assignment), PowerShell is mentioned before CLI. However, Linux parity is generally maintained, and CLI examples are included throughout. The 'Next steps' section lists Linux and Windows guides separately, but Windows PowerShell is referenced before Linux CLI in some links.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) and is recommended for Linux/macOS users.
  • Where possible, clarify which examples are platform-specific and which are cross-platform.
  • Consider adding Bash or shell script examples for Linux users if relevant.
  • Ensure that Linux/macOS users are not required to use PowerShell for any critical task.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are presented first in several sections, such as 'Sample workloads' and performance throttling examples. Linux information is present and detailed, but Windows scenarios are prioritized in ordering and example depth.
Recommendations
  • Present Windows and Linux examples in parallel or alternate order to avoid implicit prioritization.
  • Expand Linux workload examples to match the depth and specificity of Windows examples (e.g., provide step-by-step guides or templates for Pacemaker/Corosync clusters, as is done for WSFC and SoFS).
  • Ensure that performance throttling examples include both Windows and Linux scenarios equally, possibly with diagrams for Linux as well.
  • Where possible, provide links to Linux-specific templates or walkthroughs, similar to the Windows links.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is generally neutral and focused on Azure Disk Storage features, but there are a few instances where Windows-specific links or references are given before Linux equivalents, and some links point to Windows-specific documentation. For example, in the 'Live Resize' section, the link is to a Windows page, and in the 'Expand Ultra Disks and Premium SSD v2 without downtime' section, the Windows article is mentioned before the Linux article. There is also a reference to Azure PowerShell in the 'LastOwnershipUpdateTime' section, but Azure CLI is mentioned alongside it.
Recommendations
  • Ensure that Linux and macOS examples and documentation links are provided alongside Windows/PowerShell examples, and are given equal prominence.
  • Where possible, avoid linking only to Windows-specific documentation; include Linux/macOS documentation or clarify if a feature is platform-agnostic.
  • When referencing both Windows and Linux documentation, alternate the order or present them together to avoid 'windows_first' bias.
  • Review all links and ensure parity between Windows and Linux documentation coverage.
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 covers ephemeral OS disks for both Linux and Windows VMs, with parity in most explanations and examples. However, there are minor signs of Windows bias: Windows image sizes are discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Linux equivalents are present, but Windows tools and examples tend to be listed first.
Recommendations
  • Alternate the order of Windows and Linux examples in sections to avoid implicit prioritization.
  • In the 'Customer Managed key' section, mention Azure CLI (Linux) before PowerShell, or present both together.
  • In 'Size requirements', discuss Linux image sizes before Windows, or present both together.
  • Ensure that all code samples and links for Linux and Windows are equally prominent and accessible.
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 provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently lists PowerShell examples after CLI, and sometimes gives them equal prominence. There are no Linux shell-specific examples beyond Azure CLI, but this is reasonable given the Azure context. No Windows-only tools or patterns are used, and all examples are relevant to Linux VMs. However, PowerShell is not natively available on most Linux systems, so its inclusion may be less useful for Linux-focused users.
Recommendations
  • Clearly indicate that Azure PowerShell examples are optional for Linux users, and that Azure CLI is the recommended cross-platform tool.
  • Consider adding Bash shell script examples for common extension management tasks (where appropriate) to further support Linux-native workflows.
  • In sections where both CLI and PowerShell are shown, consider listing CLI first (as is mostly done), and clarify that PowerShell is primarily for users who prefer it or are on Windows.
  • Add a brief note at the top explaining that Azure CLI is the primary tool for Linux VM management, with PowerShell as an alternative.
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 generally Linux-focused, as expected for the Azure Key Vault VM Extension for Linux. However, there are minor signs of Windows bias: PowerShell examples are presented before Azure CLI examples in deployment and troubleshooting sections, and troubleshooting instructions reference Azure PowerShell first. Azure CLI (the cross-platform tool) is included, but is not always shown as the primary or first option. There are no missing Linux examples or Windows-only tools referenced.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
  • Ensure troubleshooting instructions highlight Azure CLI as the primary method for Linux users.
  • Consider adding explicit notes that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
  • Where possible, use bash syntax for CLI examples instead of PowerShell-style backticks.
  • Review and update any references or links that default to Windows-centric instructions, ensuring Linux parity.
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 Azure VMs, but includes PowerShell examples alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which may create a perception of Windows-first bias. However, all critical instructions and examples are provided for Linux users, and Linux-specific tools and commands are well represented.
Recommendations
  • Move the Azure CLI example before the PowerShell example, as Azure CLI is cross-platform and more commonly used on Linux.
  • Clarify that PowerShell can be used on Linux, or explicitly note that the PowerShell example is optional for users who prefer it.
  • Consider adding Bash shell script examples for common deployment scenarios, as Bash is native to Linux.
  • Ensure troubleshooting and manual steps reference Linux-native commands and tools first.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents benchmarking instructions for both Windows (using DISKSPD) and Linux (using FIO), but the Windows section and tool are described first, with more detailed parameter explanations. Linux instructions are comprehensive and include job file examples, but appear after the Windows section. Both platforms are covered, but Windows is prioritized in ordering and parameter detail.
Recommendations
  • Reorder sections so Linux and Windows instructions are presented in parallel or with Linux first if targeting cross-platform users.
  • Provide equally detailed parameter explanations for FIO as are given for DISKSPD.
  • Explicitly state that both DISKSPD and FIO are platform-specific tools, and clarify which tool to use for each OS at the start.
  • Consider adding a summary table comparing DISKSPD and FIO usage for Windows and 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 for both Linux and Windows image creation in Azure Compute Gallery, with CLI, PowerShell, REST, and Portal instructions. However, there is a mild Windows bias: PowerShell examples default to Windows OS, and Windows is often mentioned first in some sections. Linux-specific guidance is present and referenced, but PowerShell examples are Windows-centric and shown before Linux equivalents. CLI and REST examples are Linux-centric, balancing the bias.
Recommendations
  • In PowerShell example blocks, provide Linux examples alongside Windows examples, or default to Linux where possible.
  • Ensure that both Linux and Windows are equally represented in example code and explanations, especially in PowerShell sections.
  • Where OS-specific steps are referenced, link to both Linux and Windows guidance equally.
  • Consider alternating the order of OS mentions (Linux first in some sections, Windows first in others) to avoid implicit prioritization.
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. In several sections, PowerShell cmdlets are referenced before CLI commands, and there is frequent use of PowerShell-specific terminology and scripting patterns. However, Linux parity is generally maintained, as Azure CLI is cross-platform and all critical tasks have CLI equivalents. There are no Windows-only tools or missing Linux examples.
Recommendations
  • Where possible, present Azure CLI examples before PowerShell examples, as CLI is more native to Linux/macOS users.
  • Ensure that CLI instructions are as detailed as PowerShell instructions, including variable initialization and error handling.
  • Clarify that PowerShell can be run cross-platform, but highlight that Azure CLI is the preferred tool for Linux/macOS environments.
  • Consider adding bash shell scripting examples for advanced scenarios, especially for Linux administrators.
  • Review terminology to avoid implying PowerShell is the default or preferred method for Linux users.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
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, Windows-centric tools and patterns (notably Hyper-V Manager and PowerShell convert-vhd) are mentioned first and most prominently, especially in the introductory sections and throughout the step-by-step guides. Linux alternatives (KVM, VMware, Kickstart) are covered in detail, but Windows/Hyper-V tools and workflows are consistently presented before their Linux equivalents, and some conversion steps reference Windows tools as primary options.
Recommendations
  • Reorder sections so Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V/Windows tools, especially in introductory notes.
  • Explicitly mention Linux-native disk conversion tools (e.g., qemu-img) in the VHD conversion prerequisites and summary, not just in the hypervisor-specific sections.
  • Where disk conversion is discussed, avoid suggesting Windows/PowerShell tools as the default; instead, provide parity by listing Linux tools first or equally.
  • Clarify that all steps can be performed on Linux hosts, and highlight cross-platform alternatives where possible.
  • Add a summary table comparing supported hypervisors and tools, with clear Linux options.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. This could be seen as a minor 'windows_first' bias, as Windows technologies and links are mentioned upfront, despite the page being Linux-focused. All technical instructions, tools, and examples are Linux-centric, with no missing Linux examples or Windows-only tools.
Recommendations
  • Move the Windows Server 2016 discussion and links to a background or context section, or clarify their relevance to Linux VM users.
  • Consider adding a brief summary of how Azure host time sync benefits Linux VMs without focusing on Windows improvements.
  • Ensure Linux-specific guidance is always prioritized and presented before any Windows-related context.
  • If referencing Windows documentation, explicitly state its relevance to Linux VM users in Azure.
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 and explicitly states applicability to both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first (e.g., MBR/GPT partitioning), Windows-specific tools (PowerShell) are referenced alongside Linux tools (Azure CLI), and some links and examples reference Windows first or more prominently. These biases are minor and do not prevent Linux/macOS users from completing tasks, as Linux equivalents are provided or referenced.
Recommendations
  • Ensure Linux and Windows examples/tools are presented together, or alternate which is shown first.
  • Where partitioning concepts are discussed, provide Linux-specific links and guidance alongside Windows references (e.g., link to Linux partitioning documentation when discussing MBR/GPT).
  • When referencing upload tools, clarify parity between Azure CLI (Linux/macOS) and PowerShell (Windows), and ensure both are equally prominent.
  • Review linked articles to confirm Linux parity in deeper content, especially for disk upload, encryption, and partitioning.
GitHub Create Pull Request