← Back to Dashboard
277
Pages Scanned
110
Pages Flagged
277
Changed Pages
39.7%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-28 00:00:40

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

109 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 reference Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows paths (C:\...), and Windows commands (cmd, echo, type, ping). There are no examples or guidance for Linux containers, nor is it stated whether Initializer CodePackages are supported for Linux container workloads. The ApplicationManifest and ServiceManifest examples exclusively use Windows-specific constructs.
Recommendations
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric.
  • If supported, provide equivalent examples using Linux container images (e.g., Ubuntu, Alpine), Linux paths (/workspace), and Linux commands (sh, echo, cat, ping).
  • Add notes or guidance for Linux/macOS users, including any limitations or differences.
  • Consider providing a cross-platform example or explicitly stating Windows-only scope if applicable.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page claims Service Fabric clusters run on Windows Server and Linux, but the actual content is heavily focused on Windows. All examples, security recommendations, and supported OS lists are Windows-only. Windows authentication and tools (Active Directory, group Managed Service Accounts) are discussed, with no Linux equivalents or guidance. Linux is mentioned in the introduction, but not supported in any practical section, and the 'Supported operating systems' section explicitly states Linux isn't yet supported.
Recommendations
  • Clarify in the introduction that Linux support is not available for standalone clusters, to avoid misleading readers.
  • Remove or revise statements suggesting Linux parity unless Linux support is actually available.
  • When Linux support is added, provide equivalent Linux examples, tools, and security guidance.
  • If Linux support is planned, add a section describing roadmap, limitations, or alternative approaches for Linux users.
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, explanations, and configuration guidance are implicitly Windows-centric. There are no Linux-specific instructions, examples, or guidance, and Linux users are informed that the feature is unavailable to them.
Recommendations
  • Explicitly mention in the introduction that the reverse proxy feature is Windows-only, to set expectations for Linux users.
  • Provide links or references to alternative approaches for service discovery and communication in Linux Service Fabric clusters, if available.
  • Consider adding a section outlining the roadmap or alternatives for Linux users, or clarifying if/when Linux support is planned.
  • Ensure that related documentation pages (e.g., setup, diagnostics) also clearly state platform limitations.
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 provides RunToCompletion semantics for Service Fabric, but all code examples, container images, and tooling references are Windows-centric. The examples exclusively use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set), and PowerShell for querying deployment status, with no mention of Linux container equivalents or Linux/macOS tooling. This creates friction for Linux users and does not demonstrate Linux parity.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) alongside Windows examples.
  • Show Linux shell commands (bash, sh) for CodePackage entry points and exit scenarios.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, REST API, or Service Fabric CLI) instead of only PowerShell.
  • Clarify any platform limitations (if RunToCompletion semantics are Windows-only, state this explicitly; if not, show cross-platform usage).
  • Present examples for both Windows and Linux containers, or note differences in supported features.
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 page provides PowerShell examples for application removal and references PowerShell as a deployment tool before mentioning CLI. There are no explicit Linux/macOS examples or references to Linux-native tools, and PowerShell is presented as the primary scripting interface for resource management tasks.
Recommendations
  • Add equivalent Azure CLI examples for application removal and management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Service Fabric CLI (sfctl) and Azure CLI alongside PowerShell when describing deployment and management workflows.
  • Provide guidance or links for Linux/macOS users, clarifying how to perform tasks without PowerShell.
  • Ensure that REST API usage examples are platform-neutral and include sample curl commands 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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) for operational tasks such as deployment, upgrade, removal, and cleanup. While REST API endpoints are mentioned, there is a lack of explicit Linux/macOS CLI examples (such as Azure CLI or sfctl) and Linux-native workflows. PowerShell is presented as the primary scripting interface, and Windows tools are often listed before REST APIs, with no clear Linux parity or guidance.
Recommendations
  • Add explicit examples using Azure CLI and sfctl for each operational task (deploy, upgrade, remove, cleanup), especially for Linux/macOS users.
  • Where PowerShell cmdlets are referenced, provide equivalent sfctl or Azure CLI commands alongside.
  • Clarify which tools are cross-platform and which are Windows-only, and recommend Linux-friendly alternatives where possible.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows-specific tools.
  • Include notes or links to Linux/macOS guidance for Service Fabric operations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows Server 2016 container samples as the basis for the examples, mentioning Windows-specific tools (e.g., 'winver' for OS build detection), and using Windows file paths (e.g., 'c:\VolumeTest\Data'). Linux equivalents, such as Linux container samples, Linux file paths, or Linux OS build detection methods, are not provided. While some sections mention Linux (e.g., certificate handling), the overall examples and guidance are Windows-centric.
Recommendations
  • Include Linux-based container manifest examples or reference Linux container samples alongside Windows samples.
  • Provide Linux file path examples (e.g., '/mnt/VolumeTest/Data') in volume bindings.
  • Mention Linux methods for detecting OS build/version (e.g., 'cat /etc/os-release' or 'uname -r') in the ImageOverrides section.
  • Clarify which features are cross-platform and which are Windows-only, and provide parity guidance where possible.
  • Add links to Linux-specific Service Fabric container documentation or samples.
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 provides a PowerShell-based deployment example and refers to Windows file paths and certificate stores before mentioning Linux equivalents. The only explicit deployment command is shown in PowerShell with a Windows path, and the Service Fabric SDK schema path is given in Windows format. The Linux certificate store location is mentioned, but only after the Windows example. There are no CLI or bash examples for Linux/macOS users.
Recommendations
  • Provide equivalent deployment examples using Azure CLI or bash scripts for Linux/macOS users alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations alongside Windows paths, not after.
  • Clarify which steps or features are cross-platform and which are Windows-specific, if any.
  • Where possible, use platform-agnostic language or provide parallel instructions for both environments.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is intended for both Windows and Linux VMs, and the Azure CLI and API examples are platform-neutral. However, the ARM template example is Windows-centric, providing only Windows image SKUs and parameters, with no Linux equivalents or guidance. Additionally, in the ARM template, the default and allowed values for the OS image are exclusively Windows Server versions, and the storageProfile is hardcoded for Windows images. This creates friction for Linux users who wish to deploy Linux VMs using ARM templates with capacity reservation groups.
Recommendations
  • Add a Linux-focused ARM template example, or at least document how to modify the template to deploy a Linux VM (e.g., using Ubuntu or CentOS images).
  • In the ARM template parameters, include both Windows and Linux image SKUs and explain how to select the appropriate one.
  • In the ARM template's storageProfile, provide examples for both Windows and Linux image references.
  • Consider adding a note or section explicitly guiding Linux users on how to adapt the ARM template for their needs.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows-specific tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps, Convert-VHD usage) without offering equivalent Linux alternatives or mentioning cross-platform options. Windows tools are mentioned first and sometimes exclusively, creating friction for Linux users who may not have access to Hyper-V or PowerShell.
Recommendations
  • Provide instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd) alongside Hyper-V/PowerShell steps.
  • Add guidance for extracting and preparing VHDs on Linux systems, not just Windows/WSL.
  • Mention cross-platform alternatives for virtualization (e.g., VirtualBox, KVM) and disk conversion.
  • Reorder sections so Linux-native workflows are presented first or in parallel with Windows options.
  • Clarify which steps are Windows-only and offer Linux/macOS equivalents where possible.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux examples and covers Azure Image Builder features for both OS types. However, there are several areas where Windows-specific tools (PowerShell, WindowsRestart, WindowsUpdate customizers) are described in greater detail, and PowerShell is often used for checksum generation and image operations. Windows customizers are listed before Linux equivalents, and PowerShell commands are frequently shown first. Some features (restart customizer, update customizer) are Windows-only, but this is clearly stated. Linux examples are present but sometimes less emphasized or appear after Windows examples.
Recommendations
  • Ensure Linux and macOS command-line examples (e.g., for checksum generation) are always provided alongside Windows/PowerShell equivalents.
  • Where possible, present Linux and Windows examples in parallel, rather than listing Windows first.
  • Expand Linux-specific guidance for customizers and validations (e.g., troubleshooting, best practices) to match the detail given for Windows.
  • For sections where only Windows tools are mentioned (e.g., Get-FileHash), add Linux/macOS alternatives (e.g., sha256sum) with equal prominence.
  • Consider adding a summary table of customizer types, clearly indicating OS support and parity.
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 ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page is focused on Linux VMs and managed Run Command, but exhibits several Windows biases. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, even though PowerShell is primarily a Windows-centric tool. Windows-specific terminology and tools (e.g., 'ipconfig', 'Write-Host', '.ps1' scripts, 'Secondary Logon' service) are mentioned or used in examples, sometimes before or instead of Linux equivalents. REST API and ARM template examples use Windows-style scripts (.ps1, Write-Host) without showing Linux shell script alternatives. Some explanations and notes reference Windows behaviors or tools without Linux parity. There are missing Linux-specific examples for REST API and ARM templates, and Windows terminology appears in Linux-focused sections.
Recommendations
  • Add Linux shell script examples (e.g., using bash, sh, or .sh files) for REST API and ARM template sections, not just PowerShell/.ps1.
  • When referencing command IDs or built-in scripts, ensure Linux equivalents (e.g., 'ifconfig', 'uname', 'ls') are shown alongside or before Windows ones.
  • Clarify when PowerShell tools are cross-platform, and provide guidance for Linux users who may not have PowerShell installed.
  • Avoid referencing Windows-specific services (e.g., 'Secondary Logon') in Linux documentation unless clearly marked as Windows-only.
  • Show Linux CLI and shell script examples first in each section, and ensure Linux terminology is used throughout.
  • Where possible, use generic scripting terminology (e.g., 'script', 'shell script') rather than Windows-centric terms (e.g., '.ps1', 'Write-Host').
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several ways. PowerShell is the only scripting example provided for certificate enrollment, and references to Windows-specific tools and concepts (such as certificate stores, ACLing, S-channel, and Key Vault VM extension for Windows) are frequent. Windows terminology and mechanisms are mentioned first or exclusively, with little to no guidance for Linux users or parity in examples. While Service Fabric supports Linux clusters, the documentation does not address Linux-specific certificate provisioning, scripting, or operational patterns.
Recommendations
  • Add equivalent Bash/CLI scripting examples for certificate enrollment and management, especially for Key Vault operations.
  • Include guidance or examples for certificate provisioning and management on Linux Service Fabric clusters, such as using Linux VM extensions or manual certificate installation.
  • Clarify which mechanisms and tools are Windows-only and provide Linux alternatives where possible (e.g., certificate store locations, ACLing, VM extensions).
  • Mention Linux-specific considerations for certificate rotation, cleanup, and monitoring.
  • Link to Linux-focused Service Fabric documentation or provide a section summarizing Linux differences.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily discusses deploying custom Windows images to Service Fabric Managed Clusters, with PowerShell examples and terminology focused on Windows. While there are references to Linux custom images and Azure CLI, the main example and workflow are Windows-centric, and the PowerShell command is given without a Linux equivalent.
Recommendations
  • Provide equivalent Linux/bash examples for role assignment (e.g., using Azure CLI instead of PowerShell).
  • Clarify when instructions are applicable to both Windows and Linux node types, or explicitly state if only Windows is supported.
  • Add ARM template examples for Linux images, or note any limitations for Linux custom images.
  • Ensure that references to Linux documentation are as prominent as Windows documentation.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides extensive PowerShell examples and references to Windows-specific tools (e.g., Service Fabric PowerShell cmdlets, AzureRm modules) for migration steps, especially in the 'Basic SKU load balancer and IP resources' scenario. There are no equivalent CLI or Linux/macOS instructions, and PowerShell is used exclusively for critical migration tasks. While ARM templates are platform-neutral, the operational steps are Windows-centric.
Recommendations
  • Add Azure CLI examples for all migration steps, especially for resource deployment, node disabling/removal, and DNS updates.
  • Document how to perform Service Fabric cluster operations (e.g., node disable/remove) using cross-platform tools or REST APIs.
  • Explicitly mention that PowerShell steps can be performed with Azure CLI or Bash on Linux/macOS, and provide sample commands.
  • Clarify any Windows-only requirements (e.g., if Service Fabric cmdlets are required, note their OS support and alternatives).
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page exhibits mild Windows bias. The only explicit tooling recommendation is to use Visual Studio on Windows and reference a local Windows path for the Service Fabric schema file. Additionally, the PowerShell module is mentioned as a way to create service instances, but no equivalent CLI or Linux-native tools are referenced. Windows tooling and patterns are mentioned before any cross-platform alternatives, and Linux/macOS users are not provided with parity guidance.
Recommendations
  • Add instructions for validating manifest XML schema using cross-platform editors (e.g., VS Code, JetBrains Rider) and explain how to obtain the schema file on Linux/macOS.
  • Mention Azure CLI or Service Fabric CLI (sfctl) as alternatives to PowerShell for creating service instances, with example commands.
  • Clarify how Linux/macOS users can author, validate, and deploy manifests, including any differences in tooling or workflow.
  • Ensure that references to Windows-specific paths/tools are accompanied by Linux/macOS equivalents or notes.
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 the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no mention of Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are given equal or greater prominence than ARM templates, and no Linux-native tooling is referenced.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, 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 (e.g., recommend Azure CLI or ARM templates).
  • Consider showing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
  • Where possible, clarify that ARM templates can be deployed from any OS using Azure CLI or portal.
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 Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform commands are given, and Windows patterns are presented first and exclusively.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using Azure CLI, REST API, or Service Fabric CLI if available).
  • Clarify whether the PowerShell command is required or if cross-platform tools can be used.
  • Mention any cross-platform management tools or interfaces for Service Fabric clusters.
  • If Service Fabric Explorer is Windows-only, note this and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides best practice examples using Azure PowerShell modules and references PowerShell-based tools before mentioning cross-platform alternatives. While Azure CLI and ARM/Bicep are listed, PowerShell is emphasized in guidance and example links, and no explicit Linux/macOS shell examples are provided. The 'sfctl' tool (which is cross-platform) is mentioned only in a table, not in narrative or examples.
Recommendations
  • Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • Mention cross-platform tools (Azure CLI, sfctl) in the narrative best practices section, not just in tables.
  • Clarify that Azure PowerShell is available on Linux/macOS, but also provide Bash/Linux shell usage examples for parity.
  • Ensure that guidance does not imply PowerShell is the preferred or only option for managing Service Fabric clusters.
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 provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlets) for resource operations, mentioning them before or instead of Azure CLI equivalents. While az resource (Azure CLI) is referenced once for application deletion, most examples and links are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI.
Recommendations
  • Include Azure CLI equivalents for all PowerShell cmdlets mentioned (e.g., az resource delete, az servicefabric managed-cluster application create).
  • Present both PowerShell and CLI options side-by-side, or clarify which tools are cross-platform.
  • Link to Azure CLI documentation where relevant, not just PowerShell modules.
  • Explicitly note that Azure CLI is fully supported on Linux/macOS for these operations.
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 areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (Event Log, Event Viewer, Diagnostics Agent) are referenced before Linux equivalents, and some examples/tutorials focus on .NET applications (typically Windows-centric). Linux-specific guidance is present but less prominent, and some features (EventStore APIs) are Windows-only without clear Linux alternatives or workarounds. The overall structure and example flow tends to prioritize Windows scenarios, creating friction for Linux users.
Recommendations
  • Ensure Linux-specific tools and patterns (such as LTTng, Syslog, Linux agent setup) are given equal prominence and described before or alongside Windows equivalents.
  • Provide Linux-focused examples and tutorials, especially for application monitoring and cluster diagnostics, not just referencing Windows/.NET scenarios.
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds where possible.
  • Add explicit Linux sample code, configuration snippets, and screenshots where Windows examples are shown.
  • Review the order of tool and agent recommendations to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific tools and patterns (e.g., Active Directory, gMSA, BitLocker, NetworkService account) are mentioned, often before or instead of Linux equivalents. Linux-specific guidance is minimal or absent in areas such as disk encryption, user accounts, and container security. Some features are described as Windows-only without clear Linux alternatives or parity.
Recommendations
  • Add explicit Linux examples and guidance alongside Windows instructions, especially for disk encryption, user accounts, and container certificate access.
  • Mention Linux tools and patterns (e.g., Linux user/group management, LUKS for disk encryption) where Windows tools are referenced.
  • Clarify which features are cross-platform and which are Windows-only, and provide Linux alternatives or workarounds where possible.
  • Ensure parity in example ordering (e.g., do not always mention Windows first; alternate or combine examples).
GitHub Create Pull Request
Service Fabric Application upgrade: data serialization ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides upgrade tutorials for Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS equivalents (such as CLI or cross-platform tools) are mentioned or linked, and Windows-oriented upgrade paths are listed first. The core serialization guidance is platform-neutral, but upgrade workflow examples are Windows-focused.
Recommendations
  • Add links or sections for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Mention and provide examples for Linux/macOS users, such as using sfctl or REST APIs for application upgrades.
  • Clarify which tools are Windows-only and suggest alternatives for other platforms.
  • Consider listing cross-platform options before or alongside Windows-specific tools in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and workflows first, with detailed tables and explanations. SFCTL (Service Fabric CLI), which is cross-platform and used on Linux/macOS, is covered after the Windows tools and receives less prominence. Examples and parameter descriptions are more extensive for PowerShell/Visual Studio, while SFCTL is described more briefly. There are no Linux-specific examples or patterns, and Windows tools are mentioned before their Linux equivalents.
Recommendations
  • Reorganize the page so that cross-platform tools (SFCTL) are presented before or alongside Windows/PowerShell and Visual Studio sections.
  • Provide Linux/macOS-specific examples and workflows, especially for SFCTL usage.
  • Ensure parameter tables for SFCTL are as detailed as those for PowerShell/Visual Studio.
  • Add explicit notes about cross-platform compatibility and highlight SFCTL as the recommended tool for Linux/macOS users.
  • Consider including a comparison table showing which tools are available on which platforms.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, without referencing Linux or cross-platform alternatives (such as Azure CLI or REST APIs). Additionally, Windows security is mentioned alongside X509 certificates in the transport subsystem, with no discussion of Linux authentication mechanisms. These examples and tools are presented as default or primary, creating friction for Linux/macOS users.
Recommendations
  • Add references to cross-platform management tools such as Azure CLI or REST APIs alongside PowerShell cmdlets.
  • Clarify whether Linux-based clusters can use the same management subsystem and tools, and provide examples for Linux environments.
  • Mention Linux authentication mechanisms (such as certificate-based authentication) explicitly, and clarify Windows-specific aspects where relevant.
  • Ensure that examples and tool references are presented in a platform-neutral or parallel manner (e.g., 'PowerShell cmdlets or Azure CLI/REST APIs').
GitHub Create Pull Request
Service Fabric On-demand backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation and REST API usage via PowerShell. There are no Linux/macOS shell (e.g., Bash, curl) equivalents, nor is there guidance for cross-platform tools. The reliance on PowerShell and Windows-centric modules creates friction for Linux/macOS users, who may not have access to PowerShell or may prefer native tools.
Recommendations
  • Add Bash/curl examples for REST API calls, showing how to trigger backups and track progress using standard Linux/macOS tools.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available cross-platform (PowerShell Core), and provide installation instructions for Linux/macOS if so.
  • Mention alternative approaches for Linux users, such as using Azure CLI or direct REST API calls.
  • Where possible, provide parity in example order (show Bash/curl before or alongside PowerShell).
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 for advanced Service Fabric application upgrade topics heavily relies on PowerShell cmdlets for examples and workflows, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line instructions are given in PowerShell, and there is no guidance for users running Service Fabric clusters on Linux or using Azure CLI. This creates friction for non-Windows users, as they must translate PowerShell examples or seek alternative tooling.
Recommendations
  • Add Azure CLI or REST API examples alongside PowerShell for all upgrade operations.
  • Clearly indicate which commands are Windows-only and provide Linux/macOS alternatives where available.
  • Include guidance or links for managing Service Fabric upgrades on Linux clusters, including references to sfctl (Service Fabric CLI).
  • Structure examples so that cross-platform options are shown first or equally, rather than PowerShell exclusively.
  • Mention any limitations or differences for Linux clusters in relevant sections.
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 upgrade demonstrates notable Windows bias. PowerShell is the only CLI example provided, and references to Service Fabric PowerShell cmdlets are prominent throughout. There are no Linux or cross-platform CLI examples (such as Azure CLI or REST API usage), and Windows-specific tools and APIs (e.g., http.sys, Windows HTTP Server API) are mentioned without Linux equivalents. The 'Next steps' section also prioritizes Windows tools (Visual Studio, PowerShell) and lacks Linux/macOS guidance.
Recommendations
  • Add equivalent examples for Linux/macOS users, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs for application upgrades.
  • Include guidance for performing upgrades on Linux-based Service Fabric clusters, noting any differences in process or tooling.
  • When referencing Windows-specific APIs (e.g., http.sys), clarify if the limitation applies only to Windows clusters and provide Linux-specific notes if applicable.
  • Balance 'Next steps' by linking to tutorials or documentation for Linux/macOS users, including cross-platform tools.
  • Where possible, present cross-platform examples first or side-by-side, rather than Windows/PowerShell examples exclusively.
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 backup configuration for Azure Service Fabric, which is a cross-platform technology. However, in the section describing file share backup storage, only Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods are mentioned. There are no examples or guidance for Linux-based file shares (such as SMB/CIFS mounts or NFS), nor is there mention of Linux authentication patterns. This omission may create friction for Linux users wishing to use on-premises file shares for backups.
Recommendations
  • Add examples and guidance for configuring file share backup storage using Linux-based file shares (e.g., SMB/CIFS or NFS mounts).
  • Include authentication patterns relevant to Linux (such as mount options, credential files, or Kerberos).
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide parity in documentation.
  • If file share backup is Windows-only, explicitly state this limitation to avoid confusion.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides several manual scaling steps using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without offering equivalent Linux CLI or cross-platform alternatives. Additionally, PowerShell examples are presented first and exclusively in critical operational sections, creating friction for Linux users. However, the page does mention Linux clusters in the 'Next steps' section and does not focus on Windows-only features.
Recommendations
  • Add equivalent Linux CLI commands (e.g., Service Fabric CLI or REST API) for scaling operations alongside PowerShell examples.
  • Clearly indicate which commands are platform-specific and provide guidance for Linux/macOS users.
  • Where possible, use cross-platform tools (such as Azure CLI or Service Fabric CLI) in examples.
  • Ensure that manual and programmatic scaling instructions are accessible for both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell only, with PowerShell being the exclusive CLI example for configuring placement policies. There are no examples or instructions for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools. The PowerShell examples are shown alongside C# code, but no Linux-native equivalents are given.
Recommendations
  • Add Azure CLI examples for configuring placement policies, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example calls for placement policy configuration, which are platform-agnostic.
  • Mention and link to any available Linux/macOS-compatible Service Fabric management tools.
  • Clarify if PowerShell examples are only applicable on Windows, and provide alternatives for Linux/macOS users.
  • Consider providing bash scripts or instructions for Linux environments where applicable.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based examples and instructions for restoring backups in Azure Service Fabric. All CLI and REST API usage is demonstrated via PowerShell scripts, and the prerequisite is to install a Microsoft.ServiceFabric.Powershell.Http module. There are no Bash, Linux, or cross-platform CLI examples, nor is there mention of Linux-compatible tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Bash or cross-platform CLI examples for REST API calls (e.g., using curl or az CLI).
  • Mention that PowerShell Core is available on Linux/macOS and clarify if the Microsoft.ServiceFabric.Powershell.Http module is compatible with PowerShell Core on non-Windows platforms.
  • Provide guidance for Linux/macOS users on how to authenticate and make REST API calls without PowerShell.
  • Include references to Service Fabric CLI (sfctl) if applicable, or note its limitations.
  • Explicitly state platform requirements and alternatives for non-Windows 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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used for advanced cluster upgrade operations without Linux/bash equivalents. Windows-specific configuration details (e.g., registry keys, Windows Update settings) are described without mentioning Linux alternatives or clarifying their applicability. In several places, Windows tools and patterns are mentioned first or exclusively.
Recommendations
  • For every PowerShell example, provide an equivalent Bash/Azure CLI or Linux-native example where possible, especially for cluster upgrade operations.
  • When discussing OS-specific configuration (e.g., registry keys, Windows Update), clarify that these steps are Windows-only and, if relevant, provide Linux equivalents or state if not applicable.
  • Balance the order of presentation: alternate or parallelize Windows and Linux instructions/examples to avoid implicit prioritization.
  • Explicitly indicate when a step or configuration is Windows-only, and link to Linux-specific documentation or guidance where available.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a generally balanced overview of Service Fabric networking best practices, but there are several instances of Windows bias. PowerShell and Windows-specific tools are mentioned more frequently and sometimes before their Linux equivalents. Windows examples and terminology (such as PowerShell APIs, netsh commands, and Windows container guidance) are often presented first or exclusively, while Linux-specific instructions or CLI alternatives are less prominent or referenced later. Some example links and templates are Windows-focused, and there is occasional lack of parity in example depth for Linux users.
Recommendations
  • Where PowerShell is referenced, provide equivalent Azure CLI or bash examples for Linux users.
  • When mentioning Windows tools (e.g., netsh), include Linux alternatives (e.g., 'ss', 'lsof', or 'cat /proc/net/tcp').
  • Ensure that ARM template examples and sample links include both Windows and Linux cluster templates.
  • When discussing application networking, clarify Linux container support and provide Linux-specific guidance where relevant.
  • In tables and lists, avoid presenting Windows-specific information before Linux unless the feature is Windows-only.
  • Expand Linux-specific instructions (e.g., for enabling Accelerated Networking, port ranges, and cluster creation) to match the detail provided for Windows.
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: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents some evidence of Windows bias. While it describes both Windows and Linux node types in Service Fabric clusters, it uses Windows-style paths (e.g., 'D:\\SvcFab') in JSON snippets, and the 'Next steps' section links exclusively to Windows/PowerShell-specific tasks (RDP port range, admin username/password changes) without Linux/SSH equivalents. There are no Linux-specific examples or guidance for connecting to Linux nodes or managing them, and Windows tools/patterns (RDP, PowerShell) are mentioned without parity for Linux/macOS users.
Recommendations
  • Add Linux/SSH-specific guidance and examples for connecting to Linux node types (e.g., SSH port management, changing SSH user/password).
  • Provide Linux-style paths (e.g., '/var/svcfab') in JSON snippets or clarify that the 'dataPath' should be OS-appropriate.
  • Include links to Linux management scripts or documentation alongside Windows/PowerShell scripts.
  • Ensure that guidance for node management covers both Windows and Linux scenarios equally.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples for key security tasks, such as certificate generation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows-centric patterns (e.g., certificate store behavior, Defender exclusions) are described in detail, while Linux equivalents are less prominent or omitted. Some sections (Windows Defender, DSC) are Windows-only by nature, but others could improve Linux parity.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them, especially for certificate and secret management.
  • Where Windows tools (PowerShell, DSC, Defender) are discussed, provide equivalent Linux guidance or clarify if no direct equivalent exists.
  • Add more explicit references to Linux security baselines and tools (e.g., SELinux, AppArmor, Linux antivirus solutions) where relevant.
  • Clarify which sections are Windows-only and which apply to both platforms, to reduce ambiguity.
  • Consider reordering sections so Linux and Windows examples are equally prominent.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows-specific terminology (e.g., 'Windows Fabric', 'Windows only' flags, 'Windows Defender Firewall', 'NTLM authentication', 'MY' certificate store, 'LocalMachine' store location) is used throughout, and Windows-related settings are often mentioned first or exclusively. Linux equivalents are sometimes referenced (e.g., LinuxExternalExecutablePath, container network setup defaults), but Windows tools and patterns dominate, and Linux-specific guidance is sparse.
Recommendations
  • Where Windows-specific settings are mentioned, add Linux equivalents or clarify if the setting is cross-platform.
  • For parameters like certificate store names ('MY', 'LocalMachine'), provide Linux equivalents or note differences.
  • Expand guidance for Linux users, especially around security, networking, and file store configuration.
  • Ensure that examples and descriptions reference both Windows and Linux patterns equally.
  • Clarify which features are Windows-only and which are supported on Linux, ideally in a summary table.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Auto Scaling Services and Containers ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides example code for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. There is no mention of Linux-native tools or cross-platform CLI approaches (e.g., Azure CLI, Bash scripts). Additionally, PowerShell examples are presented alongside C# and manifest examples, but Linux alternatives are absent.
Recommendations
  • Add equivalent Bash or Azure CLI examples for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly mention any cross-platform tools or APIs available for Linux/macOS users.
  • Clarify which steps or commands are Windows-only and provide Linux alternatives where possible.
  • Consider referencing or linking to Linux-specific Service Fabric management documentation.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively provides PowerShell command examples for managing Service Fabric Application Groups, alongside C# API usage. There are no examples or instructions for Linux/macOS users, such as Bash/CLI equivalents or references to cross-platform tools. PowerShell is a Windows-centric tool, and its use here assumes a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and supported on Linux/macOS.
  • Explicitly mention whether PowerShell Core (cross-platform) can be used, or clarify if only Windows PowerShell is supported.
  • Provide Bash shell script examples or reference REST API endpoints for users on Linux/macOS.
  • Include a note about platform support for Service Fabric management tools, and link to relevant installation guides for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell example for querying Service Fabric partition health, using Windows-specific syntax and paths. No equivalent Linux/macOS CLI or REST API example is given. The example is presented early in the page, and references to Windows tools (PowerShell) are made before any mention of cross-platform alternatives. However, the rest of the documentation is largely conceptual and platform-neutral.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health queries, which are platform-independent.
  • When showing command-line examples, present both Windows (PowerShell) and Linux/macOS (bash/CLI) versions side-by-side.
  • Clarify that PowerShell is just one option, and link to documentation for cross-platform tools.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or cross-platform Azure CLI). PowerShell is presented as the primary scripting interface, and there is no mention of Linux-native tools or commands. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other interfaces.
Recommendations
  • Add cross-platform Azure CLI examples for all PowerShell commands shown.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for Service Fabric management, and provide usage instructions if so.
  • Mention any REST API or SDK alternatives for configuring sensitivity and maximum load, with example requests.
  • Explicitly state platform requirements for each example (e.g., 'Windows-only', 'cross-platform').
  • Consider including Bash or shell script examples if supported.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and cross-platform (JSON) configuration examples for Service Fabric clusters, but Windows-specific XML (ClusterManifest.xml) and PowerShell examples are presented first and more frequently. PowerShell is the only CLI example shown, with no Linux shell or CLI parity. The XML configuration is labeled as 'WindowsServer', and the PowerShell examples are not accompanied by Linux CLI equivalents. However, JSON examples for standalone deployments are included, and the overall concepts are platform-neutral.
Recommendations
  • Add Linux CLI examples (e.g., Bash with sfctl or Azure CLI) alongside PowerShell for service creation and updates.
  • Clarify when XML/WindowsServer configuration is Windows-only and when JSON applies to Linux clusters.
  • Present JSON configuration examples before or alongside XML/WindowsServer examples to emphasize cross-platform support.
  • Mention Linux/macOS tools (such as sfctl) where PowerShell is referenced.
  • Explicitly state platform applicability for each example.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides code examples primarily in C# and PowerShell, with PowerShell being the only CLI example shown. There are no Linux CLI equivalents (such as Bash or Azure CLI), and PowerShell is presented as the default scripting tool for service creation and management. This creates friction for Linux/macOS users, as Service Fabric can be managed from Linux using Azure CLI or REST APIs, but these options are not mentioned or demonstrated.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for metric configuration and load reporting, with links to relevant documentation.
  • Clarify which management operations are available from Linux/macOS and provide parity in examples where possible.
  • If PowerShell is required for certain operations, explicitly state this and provide alternative guidance for Linux users.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager: Movement cost ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell and C# examples for configuring movement cost in Service Fabric clusters, but does not include equivalent Linux/bash/CLI examples. PowerShell is a Windows-centric tool, and its use is presented before any mention of cross-platform alternatives. There is no indication of how Linux/macOS users can perform these tasks, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating MoveCost, as these are cross-platform and usable on Linux/macOS.
  • Explicitly mention whether PowerShell examples are usable on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide bash or shell script equivalents where possible, or clarify if certain operations are only possible via PowerShell.
  • Document any limitations or differences for Linux/macOS users in a dedicated section.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell examples for managing node tags and service requirements, but does not include equivalent Linux/macOS CLI (e.g., Bash, Azure CLI) or cross-platform REST API examples. PowerShell is primarily a Windows tool, and its prominence creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add examples using Azure CLI or REST API for managing node tags and service requirements, as these are cross-platform and accessible from Linux/macOS.
  • Explicitly mention whether PowerShell cmdlets are available on Linux/macOS, or provide guidance for Linux users (e.g., using PowerShell Core, if supported).
  • Include Bash or shell script examples where possible, or clarify if only PowerShell is supported.
  • Ensure REST API documentation is referenced and linked for users on non-Windows platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias. It references PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without providing equivalent Linux or cross-platform CLI examples. The linked 'scale a standalone cluster' documentation appears to be Windows Server-focused, and there is no mention of Linux tooling or procedures for scaling standalone clusters, despite Service Fabric supporting Linux nodes.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) or REST APIs for cluster scaling, which are cross-platform.
  • Explicitly mention whether standalone cluster scaling is supported on Linux, and provide guidance or links for Linux-based clusters.
  • If PowerShell is required, clarify whether PowerShell Core (cross-platform) is supported, or provide Bash/Linux shell alternatives.
  • Ensure linked documentation (e.g., 'scale a standalone cluster') covers Linux scenarios or clearly states if only Windows is supported.
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 security mechanisms (Kerberos, Windows accounts, group Managed Service Accounts) are mentioned prominently and often before Linux equivalents. References to certificate creation tools and best practices are Windows-centric (e.g., MakeCert.exe, Windows Server certificate service). There is a lack of explicit Linux example links or guidance for standalone Linux clusters, and Linux-specific certificate management or authentication patterns are not discussed. The concept of Linux clusters is acknowledged, but practical instructions and parity are missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate creation and management using Linux tools (e.g., OpenSSL).
  • Provide Linux-specific examples for node-to-node and client-to-node security setup, including configuration templates and authentication mechanisms.
  • Mention Linux certificate authorities and tools alongside Windows Server certificate service.
  • Ensure parity in recommendations for production certificate creation and management for Linux environments.
  • Clarify which instructions are applicable to both Windows and Linux, and highlight any differences.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux examples or links to Linux-specific upgrade/configuration documentation, despite Service Fabric standalone clusters supporting Linux nodes.
Recommendations
  • Add links to Linux-specific upgrade and configuration documentation where available.
  • Provide examples or instructions for Linux clusters, such as how to patch Linux nodes or upgrade Service Fabric on Linux.
  • Clarify when a feature or tool is Windows-only, and offer Linux alternatives or note limitations.
  • Ensure parity in documentation structure and guidance for both Windows and Linux users.
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 provides general guidance for upgrading Azure Service Fabric clusters but exhibits some Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (such as Bash or Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, with no mention of Linux node patching. Windows terminology and tools are sometimes mentioned first or exclusively, and Linux/macOS users may need to infer their own workflows.
Recommendations
  • Explicitly mention Linux/macOS support where applicable, especially for cluster management and upgrades.
  • Provide Linux-specific examples or clarify when Azure CLI commands are cross-platform.
  • Add links or sections for patching Linux-based Service Fabric clusters, if supported.
  • Ensure that references to PowerShell are balanced with Bash or Azure CLI examples, and clarify tool parity.
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 exhibits several Windows biases: all deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Linux/macOS alternatives; Visual Studio is referenced for packaging the sample application, with no mention of cross-platform tools; and Windows file paths and patterns are used throughout. No Linux/macOS-specific guidance or parity is provided, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for deployment and deletion tasks alongside PowerShell examples.
  • Mention and provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Include Linux/macOS file path examples and clarify any OS-specific steps.
  • Explicitly state that Visual Studio is optional and provide alternatives for non-Windows environments.
  • Consider referencing VS Code or other editors for cross-platform development.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples and administrative instructions primarily using PowerShell and C#, both of which are more commonly associated with Windows environments. There are no equivalent Linux CLI or bash examples, and PowerShell commands are referenced as the main administrative tooling. The 'Choosing a platform' section does acknowledge Linux, but only in the context of implementation differences, not in terms of parity of tooling or examples.
Recommendations
  • Add Linux-specific CLI/bash examples alongside PowerShell for administrative tasks (e.g., scaling services, creating/removing instances).
  • Reference and link to Service Fabric CLI (sfctl) usage for Linux users, and provide equivalent commands where possible.
  • Explicitly mention cross-platform administrative tools and workflows, clarifying which commands are available on both Windows and Linux.
  • Ensure that examples and instructions are presented in a platform-neutral way, or in parallel sections for Windows and Linux.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation covers Azure Service Fabric concepts for both Windows and Linux, but there are several areas where Windows is prioritized or Linux parity is lacking. Windows-specific tools (PowerShell, Visual Studio) are mentioned first or exclusively in some sections, and standalone clusters are only supported on Windows. Examples and explanations often reference Windows services and executables before Linux equivalents, and Linux-specific guidance is minimal or missing in some areas.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and upgrades.
  • Mention Linux CLI tools (e.g., Bash, sfctl) before or alongside PowerShell, and clarify which tools are cross-platform.
  • Add explicit guidance for Linux users in sections about application lifecycle, health monitoring, and diagnostics.
  • Clearly indicate feature parity and limitations for Linux throughout the documentation, linking to the differences page where relevant.
  • Include Linux-focused 'Next Steps' and sample links, not just Windows/Visual Studio-centric ones.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Azure Service Fabric Events demonstrates a moderate Windows bias. It references Windows Event logs, ETW, and the Windows Azure diagnostics agent as primary mechanisms for accessing events, with no mention of Linux equivalents or cross-platform tooling. Windows-specific tools and patterns are mentioned first and exclusively, potentially creating friction for Linux cluster administrators.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels, logging mechanisms, or monitoring tools.
  • Include examples or references for accessing Service Fabric events on Linux, such as using syslog, journald, or Azure Monitor integration for Linux clusters.
  • Clarify which instructions or tools are Windows-only and provide Linux alternatives where available.
  • Consider reordering sections to present cross-platform or platform-neutral methods (such as REST APIs) before platform-specific tooling.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, ApplicationManifest.xml editing in Visual Studio) are mentioned and demonstrated, while Linux alternatives (such as Azure CLI, Bash, or editing manifests in Linux environments) are not. Additionally, enabling DNS service via the Azure portal is described, but it is noted that Linux clusters cannot use this method, with no Linux-specific guidance provided. Windows-centric approaches are presented first or exclusively in several sections.
Recommendations
  • Add Linux-specific examples for setting DNS names, such as using Azure CLI or Bash scripts.
  • Provide guidance for editing manifests and deploying services from Linux environments (e.g., using VS Code, nano, or vim).
  • Include instructions for enabling DNS service in Linux clusters, focusing on ARM templates and CLI methods, since portal support is unavailable.
  • Clarify which steps or features are Windows-only and provide Linux alternatives where possible.
  • Balance PowerShell examples with Azure CLI or Bash equivalents for cross-platform parity.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. The main example uses Windows PowerShell cmdlets, which may create friction for Linux users, as Service Fabric supports cross-platform management via REST and CLI tools.
Recommendations
  • Add equivalent examples using Service Fabric REST API for health reporting and querying, which are platform-agnostic.
  • Include examples using Azure CLI or Service Fabric CLI (sfctl) for health reporting and evaluation, which work on Linux/macOS.
  • Clearly indicate that PowerShell is one option, and provide links or references to cross-platform alternatives.
  • Ensure that all critical tasks demonstrated with Windows tools are also shown with Linux-compatible methods.
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 provides PowerShell-based examples and references for managing Service Fabric services, with no equivalent Linux CLI or cross-platform examples. PowerShell is presented as the primary tooling for service creation and management, and REST API and .NET examples are included, but Linux-native tools (such as sfctl or Azure CLI) are not mentioned. The 'Next steps' section also directs users to PowerShell for application management.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and commonly used on Linux/macOS.
  • Include Azure CLI commands where applicable for service creation and management.
  • Explicitly mention that PowerShell examples are for Windows, and provide Linux/macOS alternatives.
  • Update 'Next steps' to reference both PowerShell and sfctl/Azure CLI documentation for application deployment/removal.
  • Clarify any platform-specific limitations, if present, to help users understand which tools are supported on their OS.
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 page provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed in detail, both of which are primarily Windows-centric tools. Linux equivalents (sfctl and install.sh) are mentioned but receive less prominence and explanation.
Recommendations
  • Provide more detailed Linux/macOS examples, such as using sfctl and install.sh, including sample commands and parameter formats.
  • Ensure Linux tools (sfctl) are given equal prominence and explanation as PowerShell and Visual Studio.
  • Add explicit guidance for Linux/macOS users on managing parameter files and deployment workflows.
  • Consider including a table or section comparing Windows and Linux workflows for parameter management.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application and service manifest examples exhibits mild Windows bias. It references Windows-specific accounts (e.g., NetworkService, Administrators), uses Windows-style scripts (Setup.bat), and mentions the ServiceFabric PowerShell module for service creation. There are no explicit Linux examples or references to Linux equivalents for user accounts, startup scripts, or tooling. The manifest XML itself is cross-platform, but supporting instructions and examples are Windows-centric.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
  • Clarify how user accounts and groups map to Linux (e.g., use of system users, sudo, etc.) and whether NetworkService/Administrators concepts apply.
  • Mention or link to Linux-compatible tools for deploying and managing Service Fabric applications (e.g., Service Fabric CLI instead of PowerShell).
  • Provide guidance for cross-platform manifest authoring, highlighting any OS-specific considerations.
  • Explicitly state when examples are Windows-only and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows-centric tools (e.g., RDP, Windows command prompt for ping), without offering equivalent Linux/macOS instructions or CLI examples. Windows tools and patterns are mentioned first and exclusively, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) examples for all deployment steps alongside PowerShell commands.
  • Include instructions for accessing VMs via SSH (for Linux/macOS) in addition to RDP.
  • Show Linux/macOS command-line equivalents for network testing (e.g., ping, ssh).
  • Clarify that Service Fabric clusters can be managed from any OS and provide cross-platform guidance.
  • Consider referencing Bash scripts or templates for Linux 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 as the primary example for interacting with the Service Fabric cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned as alternatives, PowerShell is consistently presented first and most prominently. There are no explicit Linux/macOS shell (e.g., Bash/CLI) examples or references, and the documentation assumes Visual Studio for publishing, which is Windows-centric.
Recommendations
  • Add Azure CLI or Bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString, if supported.
  • Include references or links to cross-platform tools or SDKs (e.g., Service Fabric CLI, REST API usage with curl) alongside PowerShell.
  • Clarify if certain operations (such as Visual Studio publishing) are Windows-only, and suggest alternatives for Linux/macOS users.
  • Balance the order of tool mentions (e.g., list REST, .NET, and PowerShell together or in a non-Windows-first order).
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of equivalent Linux CLI tools or usage patterns. The documentation repeatedly refers to administrative operations via PowerShell, and does not provide examples or guidance for Linux/macOS users, even though Service Fabric supports cross-platform development and management. This creates friction for non-Windows users who may need to perform these operations via REST APIs, FabricClient SDKs, or other cross-platform tools.
Recommendations
  • Add examples for performing replica soft delete and restore operations using cross-platform tools such as the Service Fabric CLI (sfctl), REST APIs, or FabricClient SDKs.
  • Clarify whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative instructions if not.
  • Include sample commands for querying and managing replicas using sfctl or REST endpoints.
  • Explicitly mention cross-platform support and provide links to relevant Linux/macOS documentation.
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 thorough coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, there is a notable Windows bias in several sections: HTTP.sys is discussed in detail, including endpoint configuration and port sharing, but is explicitly marked as Windows-only. Windows-specific tools and APIs (such as netsh and the Windows HTTP Server API) are referenced without Linux/macOS equivalents. In some sections, Windows/HTTP.sys is discussed before Kestrel, and endpoint configuration examples are given in a Windows-centric context. The debugging section references Visual Studio, a Windows-first tool, as the next step. While Kestrel is recommended for cross-platform scenarios, Linux/macOS users may find some friction due to Windows-centric explanations and lack of parity in tooling and examples.
Recommendations
  • Ensure that all examples and configuration instructions for Kestrel are presented before or alongside HTTP.sys/Windows-specific guidance.
  • Add explicit notes or sections clarifying Linux/macOS support, including any limitations or differences in Service Fabric hosting and endpoint configuration.
  • Provide Linux/macOS equivalents for any Windows tools mentioned (e.g., netsh), or clarify when such tools are not needed for Kestrel.
  • Include cross-platform debugging guidance (such as using Visual Studio Code or CLI tools) in the 'Next steps' section.
  • Where possible, highlight that Kestrel is the preferred option for Linux/macOS and provide clear instructions for those platforms.
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 provides detailed PowerShell examples for health reporting and cluster interaction, but does not mention or provide equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform tools). PowerShell is presented as the primary scripting interface, and Windows-style paths and prompts are used. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting tasks.
  • Explicitly mention cross-platform support for Service Fabric CLI tools, if available, and provide links or references.
  • Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or provide alternatives.
  • Include REST API examples with curl commands for Linux/macOS users.
  • Use neutral prompts and paths (e.g., $> or #) in examples, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service, but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). It references Windows-centric tools (PowerShell, Service Fabric SDK) without Linux equivalents, and omits guidance for cross-platform environments.
Recommendations
  • Add examples for using the Fault Analysis Service from Linux/macOS, such as via Azure CLI, Bash, or REST API.
  • Mention how Linux users can install and use Service Fabric SDK and interact with the Fault Analysis Service.
  • Clarify whether PowerShell is required or if alternative cross-platform tools are available.
  • Provide parity in code samples and tooling instructions for non-Windows platforms.
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 oriented towards Windows development workflows, specifically Visual Studio and PowerShell. All deployment and configuration examples reference Visual Studio features (Build/Rebuild/F5/Ctrl+F5/Publish) and PowerShell cmdlets, with no mention of Linux/macOS equivalents or cross-platform tooling. There are no examples or guidance for Linux/macOS users, and the documentation assumes the use of Windows-centric tools and patterns throughout.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using Azure CLI or cross-platform tools instead of (or in addition to) PowerShell.
  • Clarify which features are exclusive to Visual Studio/Windows and offer alternative workflows for Linux/macOS users where possible.
  • Mention any limitations or differences for Linux/macOS users up front, so expectations are set clearly.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page is generally platform-neutral, but there are notable Windows-centric elements. Windows terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections. The description of nodes references an 'auto-start Windows service' and Windows executables, with no mention of Linux equivalents or service management patterns. Code package examples focus on EXE/DLL files, which are Windows-specific, and do not provide Linux examples (such as ELF binaries or .sh scripts). While Linux support is acknowledged, Windows patterns are presented first and more prominently.
Recommendations
  • Add Linux-specific terminology and examples alongside Windows references (e.g., mention systemd services, ELF binaries, .sh scripts).
  • Clarify how Service Fabric nodes and services are managed on Linux (e.g., what replaces the Windows service model, how executables are launched).
  • Provide parity in code package examples by including Linux file types and startup patterns.
  • Ensure that references to Windows tools and patterns are balanced with Linux equivalents throughout the documentation.
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 page focuses exclusively on upgrading Service Fabric applications using Visual Studio and PowerShell, both of which are Windows-centric tools. All examples and instructions are tailored to Windows environments, with no mention of Linux/macOS alternatives or cross-platform CLI tools. Linux users are not provided with equivalent guidance, creating friction for those not on Windows.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Mention and link to any Linux-compatible tools or workflows for Service Fabric application upgrades.
  • Clarify if Visual Studio and PowerShell are required, and provide alternative guidance for Linux/macOS users if possible.
  • Include sample commands for Bash or other Linux shells where applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Azure PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or bash scripting examples are given. Windows-specific scenarios (such as Windows VM activation and Windows updates) are mentioned before Linux equivalents, and Linux package manager access is only briefly referenced. The sample command for assigning fault domains uses Azure CLI, which is cross-platform, but there is no demonstration of Linux shell usage or explicit Linux/macOS considerations.
Recommendations
  • Add explicit bash/Linux shell examples alongside PowerShell and Azure CLI commands.
  • Provide Linux-specific migration considerations, such as handling SSH keys, package manager updates, and disk management.
  • Ensure Linux scenarios (e.g., package manager access, Linux VM extensions) are described with equal detail as Windows scenarios.
  • Mention cross-platform tools (e.g., Azure CLI) as primary options, and clarify PowerShell usage is optional.
  • Include links to Linux documentation for relevant Azure features (e.g., Linux VM activation, Linux troubleshooting).
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows (PowerShell) and cross-platform (Azure CLI, REST, ARM/Bicep) examples for configuring and managing automatic OS image upgrades in Azure Virtual Machine Scale Sets. However, in several sections, PowerShell (a Windows-centric tool) examples are presented before Azure CLI, and some ARM template snippets use Windows images as defaults. There are also multiple references to Windows-specific properties and behaviors, sometimes without equivalent Linux notes. While Linux is supported and examples are present, the ordering and emphasis can create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • When showing ARM or Bicep template snippets, use a Linux image as the default or provide both Windows and Linux examples.
  • Where Windows-specific properties (e.g., enableAutomaticUpdates) are discussed, add clarifying notes about Linux equivalents or state when not applicable.
  • Ensure that all sections referencing tools or commands provide parity between Windows and Linux (e.g., Bash scripts, cloud-init, etc.), or explicitly state when a feature is Windows-only.
  • Consider adding a table or section summarizing differences or additional steps for Linux users.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI examples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-centric variable names. There are no examples for deploying Linux VMs or using Linux-specific images, and the PowerShell examples are inherently Windows-focused. The CLI examples could be used on Linux/macOS, but they only show Windows VM deployment, creating friction for Linux users.
Recommendations
  • Add Linux VM deployment examples alongside Windows examples in Azure CLI sections (e.g., use 'UbuntuLTS' or other popular Linux images).
  • Explicitly mention that Azure CLI commands work cross-platform and provide sample variable values for Linux scenarios.
  • In PowerShell sections, clarify that PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS users.
  • Ensure parity in screenshots and portal instructions by referencing both Windows and Linux VM creation flows where relevant.
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 parity between Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. Windows/PowerShell commands are shown first in some sections, and ARM template deployment examples use PowerShell exclusively. There are no Linux-specific shell examples for ARM template deployment or feature registration, and the PowerShell examples use Windows VM images by default.
Recommendations
  • Add Bash or cross-platform shell examples for ARM template deployment and feature registration (e.g., using Azure CLI or Bash scripts).
  • Provide examples for deploying Linux VM images in PowerShell sections, or clarify how to do so.
  • When showing PowerShell and CLI examples, alternate their order or explicitly note both are equally supported.
  • For feature registration, show Azure CLI equivalents alongside PowerShell.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, if applicable.
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 is intended for both Linux and Windows VMs, but consistently uses Windows-specific VM images (e.g., 'Win2016Datacenter') in all CLI and PowerShell examples. There are no examples showing how to deploy Ultra Disks with a Linux VM image, nor any Linux-specific considerations or commands. The Quickstart link in the portal section also points only to Windows VM creation. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
  • Provide parallel examples using a Linux VM image (e.g., 'UbuntuLTS') for Azure CLI and PowerShell sections.
  • Add a Quickstart link for creating a Linux VM in the portal.
  • Explicitly mention that the steps apply to both Linux and Windows, and highlight any OS-specific considerations.
  • Where variables are set (e.g., --image), show both Windows and Linux options, or note that any supported image can be used.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation references both Azure CLI and Azure PowerShell for configuring the NetworkAccessPolicy, but the PowerShell link is listed first and the custom RBAC role creation link points only to a PowerShell-based guide. There are no explicit Linux/macOS examples or links for custom role creation, and PowerShell is emphasized over CLI in some sections.
Recommendations
  • Provide links to both Azure CLI and Azure PowerShell guides for custom RBAC role creation.
  • Ensure Azure CLI examples and links are presented alongside or before PowerShell examples, especially for cross-platform tasks.
  • Add explicit Linux/macOS instructions or links where relevant, such as for custom role creation and disk configuration.
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, which are primarily Windows-centric, and references Windows tools (e.g., Chocolatey, PowerShell, cmd.exe) for installing the armclient. While Azure CLI and REST API methods are documented, the PowerShell section is significantly more detailed and presented first. Linux support is acknowledged throughout, but Linux-native installation methods and shell examples are missing or secondary.
Recommendations
  • Add Bash shell examples for Azure CLI usage, showing Linux/macOS command syntax and environment.
  • Provide Linux-native installation instructions for armclient (e.g., using pip, npm, or manual download), avoiding exclusive reliance on Chocolatey.
  • Include parity in scripting examples for disk management, using Azure CLI or REST API in Bash, not just PowerShell.
  • Clarify that PowerShell can be used cross-platform, but highlight any limitations or differences for Linux/macOS users.
  • Consider reordering sections so Azure CLI and REST API methods are presented before or alongside PowerShell.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements, without mentioning Linux equivalents (such as Linux clustering solutions or disk sharing limitations for Linux-based clusters). The proximity placement groups link is Windows-specific, and there are no Linux-focused examples or references. Windows clustering is discussed first and exclusively, creating a subtle Windows bias.
Recommendations
  • Add information about shared disk limitations for Linux-based clustering solutions (e.g., Pacemaker, Corosync, or other Linux HA clusters).
  • Include links to Linux documentation or guidance for configuring shared disks in Linux environments.
  • Clarify if certain limitations (such as 'only basic disks can be used with some versions of Windows Server Failover Cluster') apply only to Windows, and provide Linux-specific guidance where relevant.
  • Balance references to Windows and Linux clustering tools and scenarios.
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-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') but does not include a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the use of Windows paths ('c:\somewhere\mydisk.vhd') may confuse Linux/macOS users. Additionally, AzCopy is referenced as 'AzCopy.exe', which is specific to Windows, and there is no mention of how to run AzCopy on Linux/macOS or what the command would look like. The rest of the CLI examples are generic and compatible with all platforms, but the critical upload step is Windows-centric.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention that the path syntax differs between Windows and Linux/macOS, and show both formats.
  • Use 'azcopy' (lowercase) for Linux/macOS and 'AzCopy.exe' for Windows, or note the difference.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation page provides a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits mild Windows bias. Windows-specific terminology (e.g., certificate store paths like 'LocalMachine\My'), references to Windows APIs (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting guidance (event logs, CAPI2 logging) are presented first and in greater detail. Linux equivalents are mentioned briefly (e.g., '*var/lib/sfcerts*'), but lack parity in examples, troubleshooting, and tool references.
Recommendations
  • Expand Linux-specific guidance, including certificate store locations, relevant commands (such as openssl, systemd journal, or Linux certificate management tools), and troubleshooting steps.
  • Provide Linux/macOS examples alongside Windows examples, including cluster manifest excerpts and certificate management workflows.
  • Clarify cross-platform differences in certificate handling, validation, and error codes.
  • Reference Linux/macOS documentation or tools where Windows-specific APIs or logs are mentioned.
  • Ensure troubleshooting sections include Linux/macOS log locations and diagnostic commands.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This ordering and emphasis may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, while sfctl is cross-platform. However, Linux-compatible instructions are present and functional.
Recommendations
  • Present sfctl (CLI) examples before PowerShell, or at least in parallel, to emphasize cross-platform support.
  • Explicitly state that sfctl is recommended for Linux/macOS users.
  • Clarify any OS-specific requirements for PowerShell and sfctl usage.
  • Ensure equal detail and explanation for CLI and PowerShell sections.
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, including development environments and SDKs. However, Windows development is described first, and the quickstart link points to a .NET (Windows-oriented) guide, potentially creating a perception of Windows as the default or primary platform. Linux examples and tooling are mentioned, but not as prominently or as the first option.
Recommendations
  • Alternate the order in which Windows and Linux development environments are described, or present them side-by-side.
  • Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users in the 'Next steps' section.
  • Ensure that Linux-specific tooling and examples are as visible and accessible as Windows equivalents.
  • Clarify that Service Fabric supports both platforms equally, and highlight cross-platform parity.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Linux and Windows VMs, and provides example commands for both Azure CLI and Azure PowerShell. However, the PowerShell example is listed first, which may indicate a minor 'windows_first' bias. All tools and instructions are cross-platform, and no Windows-specific tools or patterns are mentioned exclusively.
Recommendations
  • Present Azure CLI and Azure PowerShell examples in parallel or alternate their order to avoid implicit Windows-first bias.
  • Explicitly state that both CLI and PowerShell commands work for Linux and Windows VMs.
  • Consider adding sample scripts for both Linux and Windows environments if relevant.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented first and in greater detail, with more step-by-step breakdowns and screenshots. Azure CLI examples are present and thorough, but PowerShell is given prominence, which may create friction for Linux users who typically use Bash and Azure CLI. There are no missing Linux examples, and the OS-level validation uses standard Linux tools (lsblk, cryptsetup, dmsetup).
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more native to Linux environments.
  • Ensure parity in detail and screenshots between Azure CLI and PowerShell sections.
  • Explicitly note that PowerShell examples are for cross-platform use, but Azure CLI is recommended for Linux users.
  • Consider adding Bash scripting examples for common tasks, where relevant.
  • Clarify that PowerShell can be used on Linux, but Azure CLI is the default for Linux administrators.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VMs and provides Linux-specific instructions and examples. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' section, PowerShell is listed after CLI, but both are given parity. The terminology table includes 'PowerShell cmdlets' as a term, even though this is not a Linux-native tool. Overall, there is minor bias in mentioning PowerShell for Linux management, but Linux-native tools and examples are prioritized.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform, but CLI is the native Linux tool.
  • Consider removing 'PowerShell cmdlets' from the terminology table unless specifically relevant to Linux users.
  • Ensure that CLI examples and scripts are always presented before PowerShell, and that PowerShell is described as optional for Linux users.
  • Add a note explaining the cross-platform nature of Azure PowerShell, and recommend CLI as the default for Linux users.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time sync in Azure and provides thorough Linux-specific guidance, commands, and configuration examples. However, the introduction and overview sections discuss Windows Server 2016 and its time sync improvements before describing Linux mechanisms. There are references and links to Windows time service documentation, but all technical instructions, tools, and examples are Linux-centric. The only minor bias is the Windows context being presented first in the background, which could be confusing or distracting for Linux users.
Recommendations
  • Move Windows Server 2016 context to a separate 'Background' or 'Azure host infrastructure' section, clarifying its relevance to Linux VM time sync.
  • Add a brief statement at the start explaining that Azure hosts run Windows Server, but this page is focused solely on Linux VM configuration.
  • Ensure Linux-specific information is presented before or independently of Windows references.
  • Consider reducing or relocating Windows documentation links to a 'See also' section if not directly relevant to Linux VM configuration.
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 provides a generally balanced overview of Azure Managed Disks for both Linux and Windows VMs. However, there are a few instances where Windows terminology, tools, or references are presented first or more prominently, such as in partitioning guidance and some linked articles. Linux equivalents are present but sometimes appear after Windows references or are less detailed.
Recommendations
  • When discussing partitioning (MBR/GPT), include Linux partitioning tools and documentation (e.g., 'fdisk', 'parted', or relevant Linux docs) alongside Windows links.
  • In sections referencing drive letters (e.g., OS disk as C:, data disk as D:), provide Linux device path equivalents (e.g., /dev/sda, /dev/sdb) with equal prominence.
  • For all how-to links (such as uploading VHDs), ensure Linux and Windows options are presented together and with equal visibility.
  • Where possible, avoid Windows-centric language (like 'Sysprep') without mentioning the Linux equivalent (such as 'waagent -deprovision+user').
  • Review linked articles to ensure Linux parity in depth and clarity.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described first and in more depth, with links to Windows container resources. Linux examples and tutorials are present and referenced, but Windows-specific tools and scenarios are more prominent.
Recommendations
  • Expand the Linux container runtime section to mention alternatives or clarify Docker's role and compatibility.
  • Provide more Linux-specific scenarios, such as using NGINX, Apache, or other Linux-native workloads, to balance the IIS lift-and-shift example.
  • Ensure Linux and Windows tutorials are referenced equally and with similar prominence throughout the article.
  • Add links to Linux container resources (e.g., Docker documentation, Linux container best practices) alongside Windows container links.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents Service Fabric guest executable packaging in a generally platform-neutral way, but it exhibits mild Windows bias. The directory structure example uses a Windows-style .exe file, and the Service Fabric SDK schema path is given only as a Windows filesystem location. There are no explicit Linux/macOS examples or references, and Visual Studio (a Windows-centric tool) is mentioned before command-line utilities. However, the content does not prevent Linux/macOS users from understanding or completing the task.
Recommendations
  • Include examples using Linux/macOS file paths and executable formats (e.g., .sh, no extension).
  • Mention cross-platform tools (e.g., Visual Studio Code, CLI utilities) alongside Visual Studio.
  • Provide the location of Service Fabric SDK schema files for Linux/macOS installations, if available.
  • Add explicit notes or examples for packaging non-Windows executables.
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 VM Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or immediately after CLI examples, and some extension examples use 'ApplicationHealthWindows' as the type, even in contexts where Linux is also supported. Portal instructions reference Windows UI patterns. There is no explicit Linux/macOS bias, but the PowerShell and Windows-centric extension naming may cause confusion for Linux users. All major tasks can be completed via CLI and REST API, so Linux/macOS users are not blocked, but Windows tools and patterns are given prominent placement.
Recommendations
  • Ensure that examples for Linux (e.g., ApplicationHealthLinux extension) are provided and clearly separated from Windows examples.
  • Clarify when PowerShell examples are Windows-only and provide Bash or shell script equivalents for Linux/macOS users.
  • Present CLI examples before PowerShell examples to reduce Windows-first bias.
  • Explicitly state OS support for each extension type (e.g., ApplicationHealthLinux vs ApplicationHealthWindows) and when to use each.
  • Add notes or links for Linux/macOS users where PowerShell is referenced, suggesting CLI or REST API alternatives.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI. Some sections, such as querying public IPs, show PowerShell examples before CLI, and the Application Gateway integration section has PowerShell and CLI tabs, with PowerShell appearing first. There are no Linux-specific shell examples (e.g., Bash), but CLI commands are cross-platform. No Windows-only tools or patterns are used, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS, and consider adding Bash shell script snippets where appropriate.
  • Ensure that all PowerShell examples are matched with CLI equivalents, and vice versa.
  • Where possible, clarify any OS-specific requirements or limitations for commands.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell (a Windows-centric tool) is always presented after CLI and before ARM template examples. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. The PowerShell examples are detailed and prominent, which may create a perception of Windows bias, especially for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Explicitly note that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell script examples for common tasks, or clarify that Azure CLI commands can be run in Bash, Zsh, etc.
  • Reorder examples so CLI is shown first, and PowerShell is clearly marked as Windows-specific.
  • Add a short section or note for Linux/macOS users, highlighting their recommended tools and workflows.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes example commands for Azure CLI, PowerShell, Portal, and ARM Template. The PowerShell example is present, which is Windows-centric, but the CLI example (Azure CLI) is cross-platform and appears before PowerShell. There is no exclusive use of Windows tools, and Linux/macOS users can use Azure CLI or ARM templates. However, the inclusion of PowerShell and its detailed example may indicate a mild Windows bias, and PowerShell is listed after CLI but before ARM Template.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Consider adding Bash shell script examples for Azure CLI usage to further highlight Linux parity.
  • Explicitly mention that PowerShell examples are for Windows users, while Azure CLI is cross-platform.
  • Ensure that all features described are accessible via CLI and ARM templates, and note any limitations for Linux/macOS users if present.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific tools (PowerShell cmdlets) are emphasized. The REST and Azure CLI examples are cross-platform, but PowerShell is given equal or greater prominence, and some sample code uses Windows-centric extension types (e.g., ApplicationHealthWindows) even when Linux equivalents exist.
Recommendations
  • Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in sections where both are relevant.
  • Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows extension types are supported, and provide explicit Linux-focused examples.
  • Where PowerShell cmdlets are used, provide equivalent Bash/CLI commands for Linux users.
  • Review sample outputs and snippets to ensure Linux and macOS users are not overlooked, and that instructions are clear for both platforms.
  • Consider adding a note at the start of the page indicating parity between Linux and Windows VMSS support for custom metrics and rolling upgrades.
GitHub Create Pull Request
Virtual Machines Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents." ...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Linux and Windows coverage, but there is a mild Windows bias in the ordering and tool references. Windows-specific backup tools (like Volume Shadow Service) are mentioned before Linux equivalents (fsfreeze), and Windows examples (SQL Server, Always On Availability Groups) are discussed first in database scenarios. However, Linux is acknowledged and included, and most solutions are platform-agnostic.
Recommendations
  • When mentioning backup coordination tools, list Linux options (e.g., fsfreeze) alongside Windows tools (e.g., VSS), and clarify their limitations and use cases.
  • In scenario examples, alternate between Windows and Linux workloads or explicitly mention Linux-first scenarios (e.g., PostgreSQL, Cassandra, MongoDB) with relevant backup strategies.
  • Provide links to Linux-specific documentation or third-party tools for application-consistent backups.
  • Ensure tables and comparison sections highlight Linux and Windows parity, especially for features like application/file system consistency.
  • Consider adding a brief section summarizing Linux-specific considerations for backup and disaster recovery.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with parity, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell equally, without bias.
Recommendations
  • Consider listing Linux operating system support before Windows, or presenting both together in a single table or section to avoid implicit prioritization.
  • Ensure future updates provide equal detail for both Windows and Linux, especially in example-driven sections.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is generally cross-platform and neutral, but there is a minor bias in the VM recommendations section, where Windows machines are mentioned first and given specific guidance (e.g., 'Use at least B2 for Windows machines') without equivalent Linux-specific advice. All other recommendations and links are inclusive of both Windows and Linux, and Windows-only features are appropriately flagged.
Recommendations
  • Provide equivalent Linux-specific guidance where Windows-specific advice is given (e.g., recommend minimum B-Series sizes for Linux VMs if applicable).
  • Ensure examples and recommendations are balanced, mentioning Linux and Windows equally and in parallel.
  • Where possible, add Linux-specific cost optimization tips (e.g., OS-level shutdown automation, licensing considerations).
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 server-side encryption for Azure Managed Disks and is intended for both Linux and Windows VMs. However, there is a recurring pattern where Windows/PowerShell examples and links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent, especially in sections about revoking access and enabling automatic key rotation, where PowerShell is mentioned first or exclusively in some cases. Linux parity is generally maintained, but Windows tools are prioritized in ordering and some references.
Recommendations
  • Present Azure CLI (Linux/macOS) and PowerShell (Windows) examples and links side-by-side, or alternate their ordering to avoid Windows-first bias.
  • Where PowerShell is mentioned for tasks (e.g., revoking access), ensure Azure CLI is equally referenced and linked.
  • In 'Next steps' and throughout the article, list Azure CLI and PowerShell options together, or in alphabetical order, rather than consistently listing PowerShell first.
  • Where possible, provide sample commands for both platforms inline, not just as links.
  • Review for any subtle language that implies Windows tools are preferred or default.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ minor_windows_tools
Summary
The documentation provides examples for enabling on-demand disk bursting using the Azure Portal, PowerShell, Azure CLI, and Resource Manager templates. PowerShell examples are prominent and appear before Azure CLI examples, which may suggest a Windows-first bias. The PowerShell section is detailed and uses Windows-specific terminology (cmdlets), but Azure CLI examples are also provided, supporting Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash scripting) are included, but the CLI coverage is sufficient for cross-platform parity. The Azure Portal instructions are platform-neutral.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell examples, as CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add brief Bash scripting examples for advanced Linux users, if relevant.
  • Clarify that Azure PowerShell is available in Azure Cloud Shell, which is accessible from any OS.
GitHub Create Pull Request
Virtual Machines Enable end-to-end encryption using encryption at host - Azure portal - managed disks ...-machines/disks-enable-host-based-encryption-portal.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 PowerShell and Azure CLI examples for subscription and feature registration tasks, but PowerShell examples are consistently shown first. The 'Next steps' section links to a PowerShell-focused sample repository, and there is a slight emphasis on PowerShell usage, which is more common on Windows. However, Linux parity is maintained via Azure CLI examples and explicit applicability to both Linux and Windows VMs.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or show Azure CLI examples first in some sections to avoid implicit Windows prioritization.
  • Include links to Azure CLI sample repositories in the 'Next steps' section, not just PowerShell.
  • Clarify that both PowerShell and CLI can be used from Cloud Shell, which is available on all platforms.
  • Explicitly mention that all steps are applicable to both Linux and Windows VMs, as already indicated, but reinforce this in the 'Next steps' and sample links.
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 PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are often presented before CLI, which may subtly prioritize Windows users. The 'Next steps' section lists CLI (Linux) guides first, but throughout the main content, PowerShell is frequently mentioned before CLI, and portal instructions are also Windows-centric. However, Linux parity is generally maintained, and CLI examples are present.
Recommendations
  • Ensure Azure CLI (Linux/macOS) examples are given equal prominence and are not consistently listed after PowerShell.
  • Where possible, alternate the order of PowerShell and CLI examples, or present them side-by-side.
  • Clarify that Azure CLI works on Windows, Linux, and macOS to avoid implicit platform bias.
  • Add explicit notes or links for Linux/macOS users where relevant, especially in sections referencing PowerShell.
  • Consider including Bash or shell script snippets for common tasks, if applicable.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure Managed Disks .../main/articles/virtual-machines/disks-shared-enable.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 major operations, but PowerShell examples are consistently present and often shown alongside or immediately after CLI examples. PowerShell is a Windows-centric tool, and its heavy presence may create a perception of Windows bias. However, Azure CLI examples are always present and are cross-platform. There are no missing Linux examples, and the documentation explicitly states applicability to both Linux and Windows VMs. No Windows-only tools or patterns are mentioned, and the documentation avoids Windows-specific terminology or instructions.
Recommendations
  • Consider explicitly mentioning that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, clarify that it is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • If possible, provide bash shell script examples for mounting disks to Linux VMs, especially in the 'Using Azure shared disks with your VMs' section, to further improve Linux parity.
  • Add a note in the prerequisites section indicating that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is generally Linux-focused and provides parity between Azure CLI and Azure PowerShell examples for managing VM extensions. However, PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. In several sections, PowerShell examples are presented immediately after CLI examples, and the introductory text mentions PowerShell as a method for managing extensions, which may create friction for Linux users who typically use Bash or CLI. Additionally, references to PowerShell are not always accompanied by explicit notes about cross-platform support, potentially confusing Linux users.
Recommendations
  • Clearly indicate that Azure PowerShell is cross-platform and can be used on Linux and macOS, or prioritize Azure CLI examples for Linux documentation.
  • Present Azure CLI examples before PowerShell examples in all sections, or group PowerShell examples in a separate section for users who prefer it.
  • Add Bash script examples where relevant, especially for troubleshooting or automation tasks.
  • Explicitly state in the introduction that Azure PowerShell is available for Linux, or link to installation instructions for Linux/macOS.
  • Review all references to PowerShell to ensure they do not imply Windows-only usage.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux, but Windows bias is evident in several areas: PowerShell deployment instructions are provided before Azure CLI instructions, and PowerShell is referenced for troubleshooting and deployment. Azure CLI examples are present, but PowerShell is often given first or exclusively in some troubleshooting sections. There are also references to Windows tools and patterns (e.g., PowerShell, backslash escapes), even though the extension is Linux-specific.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more relevant for Linux users.
  • Ensure troubleshooting sections provide Azure CLI commands first, or exclusively, for Linux-focused documentation.
  • Remove or minimize references to Windows-specific issues (such as PowerShell escape sequences) unless they are critical for Linux users.
  • Where PowerShell is mentioned, clarify its relevance for Linux users (e.g., if using PowerShell Core on Linux).
  • Add explicit notes about using Bash or other Linux-native scripting environments for deployment and troubleshooting.
GitHub Create Pull Request
Virtual Machines NVIDIA GPU Driver Extension - Azure Linux VMs ...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension, and in some sections (e.g., troubleshooting), PowerShell commands are presented before Azure CLI equivalents. This may create friction for Linux users, as PowerShell is not a native or common tool on Linux. However, Linux-specific instructions and examples are present throughout, and Azure CLI examples are included alongside PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more native and widely used on Linux.
  • Clearly indicate that PowerShell is optional and primarily for users on Windows or those who have installed PowerShell on Linux.
  • Consider removing or de-emphasizing PowerShell examples in Linux-focused documentation, or move them to an appendix or a 'Windows users' section.
  • Ensure troubleshooting and deployment instructions prioritize Linux-native tools and workflows.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows-specific tools (Sysprep, PowerShell) are mentioned. The Linux section is concise and references external distro-specific guides, but both platforms are covered. The Windows section appears after Linux, so there is no 'windows_first' ordering bias, but Windows-specific tools are naturally referenced for Windows VMs. No critical Linux parity issues are present.
Recommendations
  • Expand the Linux section to include troubleshooting tips and common issues, similar to the Windows section.
  • Add more detailed step-by-step instructions for Linux, including verification steps after deprovisioning.
  • Ensure parity in guidance for disk encryption and supported roles/services for Linux distributions, if applicable.
  • Consider linking to Linux-specific troubleshooting resources, as is done for Windows.
GitHub Create Pull Request
Virtual Machines HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs ...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform and covers both Linux and Windows. However, there is a subtle Windows-first bias in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ as the recommended OS without mentioning any Linux equivalents. Additionally, while Linux is referenced (e.g., in the lstopo example and OS support for SRIOV RDMA), there are no explicit Linux performance recommendations or Linux-specific best practices, and the only explicit OS recommendation is for Windows.
Recommendations
  • Add recommended Linux distributions (e.g., RHEL, Ubuntu, SLES) for performance parity in the 'Recommended OS for Performance' section.
  • If Windows Server is recommended for specific features, clarify what those features are and whether Linux alternatives exist.
  • Provide Linux-specific best practices or tuning guidance if available, especially since most HPC workloads on HBv3 are likely to run on Linux.
  • Consider listing Linux and Windows recommendations together, or in alphabetical order, to avoid implicit prioritization.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation presents Windows benchmarking (DISKSPD) first, with detailed parameter explanations and example commands, before introducing Linux benchmarking (FIO). The Windows tool DISKSPD is discussed in depth, while FIO for Linux is covered in a separate section. Both platforms are addressed, but Windows is prioritized in ordering and tool discussion.
Recommendations
  • Reorder sections so that Linux (FIO) and Windows (DISKSPD) tools are presented equally, or alternate which platform is shown first.
  • Provide a summary table comparing DISKSPD and FIO usage for both Windows and Linux, including installation instructions and example commands.
  • Ensure parameter explanations and example commands are equally detailed for both tools.
  • Add explicit guidance for benchmarking on macOS, if relevant, or clarify platform limitations.
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, there is a notable Windows bias: Hyper-V (a Windows-only tool) is consistently presented first in all sections and examples, and references to Windows tools (Hyper-V Manager, convert-vhd cmdlet) are prominent and often precede Linux alternatives. Linux hypervisors and tools are covered in detail, but are positioned after Windows-centric instructions, which may create friction for Linux/macOS users.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least provide a neutral ordering.
  • In introductory notes, mention Linux-native tools (e.g., qemu-img, guestfish) alongside Windows tools, rather than referencing Hyper-V Manager and convert-vhd first.
  • Where possible, provide parity in detail and clarity for Linux-native workflows, ensuring they are not dependent on Windows tools or terminology.
  • Consider adding a summary table or flowchart at the top to help users quickly identify the relevant workflow for their platform.
  • Explicitly state that Hyper-V instructions are for Windows users, and Linux/KVM/VMware instructions are for Linux/macOS users, to reduce confusion.
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 both Linux and Windows guidance, but there is a mild bias in example ordering and language. In the PowerShell section, Windows is shown first in the example, and Linux is mentioned as an alternative. CLI and REST examples are Linux-first. The page does not exclusively mention Windows tools or patterns, and Linux examples are present throughout. However, PowerShell is a Windows-centric tool, and its presence may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • In PowerShell examples, show Linux as the primary example or provide parity by alternating which OS is shown first.
  • Explicitly mention that PowerShell can be used cross-platform, or provide Bash/CLI alternatives for all tasks.
  • Ensure that Linux and Windows are equally represented in all example code blocks and explanations.
  • Consider adding a note for macOS users about CLI usage and any platform-specific considerations.
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 Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in greater detail. Some sections, such as prerequisites and backup instructions, reference PowerShell cmdlets before CLI equivalents. PowerShell scripts are more verbose and detailed, while CLI examples are concise. There is no evidence of missing Linux examples or exclusive Windows tools; however, the prominence and order of PowerShell content may create minor friction for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux.
  • Ensure parity in detail and explanation between CLI and PowerShell sections.
  • Explicitly note that Azure PowerShell can be used on Linux/macOS via Cloud Shell or installation, to avoid confusion.
  • Where possible, highlight CLI as the recommended method for Linux users.
  • Review backup and prerequisite instructions to ensure CLI commands are equally prominent.
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
⚠ī¸ windows_tools
Summary
The documentation is overwhelmingly Linux-focused, with all main examples and instructions tailored to Linux distributions (Ubuntu, SUSE, Red Hat). However, a single section at the end provides a PowerShell script for classic VM SKU support, which is Windows-centric and lacks a Linux CLI equivalent. This is a minor bias, as the PowerShell script is only for SKU discovery and not for the core disk expansion tasks.
Recommendations
  • Provide an Azure CLI or Bash equivalent for the PowerShell script used to determine VM SKU support for expanding disks without downtime, ensuring Linux users can perform this check without needing Windows tools.
  • Clarify that the PowerShell script is optional and only relevant for classic VM SKU users, and link to any existing Linux/CLI alternatives if available.
GitHub Create Pull Request