← Back to Dashboard
277
Pages Scanned
114
Pages Flagged
277
Changed Pages
41.2%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 277

Files Completed: 277

Problematic Pages

114 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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, specifically referencing Windows container images (mcr.microsoft.com/windows/nanoserver:1809), Windows file paths (C:\...), and Windows command syntax (cmd, echo, type, ping). There are no Linux container examples, nor any mention of Linux-compatible images, paths, or commands. The page assumes familiarity with Windows container applications and does not provide guidance for Linux users.
Recommendations
  • Add equivalent examples for Linux containers, using Linux-based images (e.g., mcr.microsoft.com/ubuntu or other Linux distros), Linux file paths (/workspace), and Linux shell commands (bash, echo, cat, etc.).
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation at the top of the article.
  • If Linux support exists, provide a complete ServiceManifest.xml and ApplicationManifest.xml example for Linux containers, including volume mounts and initialization commands.
  • Mention Linux container compatibility and any differences in behavior or configuration compared to Windows containers.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page on upgrading an Azure Service Fabric standalone cluster demonstrates a Windows bias. References and links to upgrade instructions, configuration, and patch orchestration are all Windows-specific (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md', 'Patch Orchestration Application for Windows'). There are no Linux equivalents or examples provided, and Linux-specific upgrade or patching guidance is missing.
Recommendations
  • Add explicit mention of Linux support status for standalone clusters. If Linux is supported, provide parallel instructions and links for Linux-based clusters.
  • Include Linux-specific examples, configuration file differences, and command-line instructions where applicable.
  • If certain features (like the Patch Orchestration Application) are Windows-only, clearly state this and provide Linux alternatives or workarounds if available.
  • Structure the documentation so that both Windows and Linux users can easily find relevant guidance, possibly by splitting sections or providing tabs for each OS.
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 and guidance are implicitly Windows-centric. There are no Linux-specific instructions or examples, and the reverse proxy feature is described as Windows-only. This creates a significant barrier for Linux users, as they cannot use the reverse proxy feature in Service Fabric clusters running on Linux.
Recommendations
  • Explicitly clarify in the introduction and relevant sections that the reverse proxy feature is Windows-only, to avoid confusion 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 comparison table summarizing feature parity between Windows and Linux clusters for Service Fabric, including reverse proxy support.
  • If Linux support is planned, mention roadmap or alternatives for Linux users.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
While the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters. The documentation then focuses exclusively on Windows Server versions, and security guidance includes Windows-specific recommendations (e.g., group Managed Service Accounts, Windows Active Directory) without Linux equivalents or guidance. There are no Linux-specific instructions, examples, or notes.
Recommendations
  • Clarify early in the document that standalone clusters are currently Windows-only, to avoid confusion from the initial Linux mention.
  • If Linux support is planned, provide a roadmap or link to relevant Linux documentation.
  • Remove or rephrase the opening statement to avoid implying Linux support where it does not exist.
  • When Linux support becomes available, include Linux-specific instructions, examples, and security guidance.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tooling, specifically Visual Studio and PowerShell. All upgrade instructions and examples are given for Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform tools. The documentation assumes the reader is on Windows and does not mention alternatives for Linux/macOS environments.
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 available Linux/macOS tooling for Service Fabric application upgrades.
  • Clarify whether the described upgrade process is only supported on Windows, or provide parity guidance for Linux/macOS users.
  • If Visual Studio is required, explicitly state that the process is Windows-only and suggest alternatives for non-Windows users.
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 links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows tools. There are no Linux/macOS equivalents or examples provided for upgrading applications, nor is there mention of cross-platform CLI tools. The serialization guidance is C#-centric, but Service Fabric supports .NET Core, which is cross-platform.
Recommendations
  • Add examples or links for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, and clarify if the PowerShell tutorial is compatible with PowerShell Core on Linux/macOS.
  • Provide guidance for Linux/macOS users on how to perform application upgrades without Visual Studio, possibly using command-line tools or other IDEs.
  • Explicitly state platform requirements for each upgrade method to help users identify which tutorials are relevant to their environment.
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 focuses on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and examples (such as PowerShell commands) are presented first and exclusively, with no equivalent Linux shell examples. Although there are references to Linux custom image creation and Azure CLI for browsing marketplace images, the main workflow and examples are Windows-centric, and Linux-specific guidance is minimal.
Recommendations
  • Add Linux shell (bash/CLI) equivalents for PowerShell commands, especially for role assignment.
  • Clarify whether Linux custom images are supported for Service Fabric Managed Clusters and provide explicit examples if so.
  • Include ARM template examples for Linux node types if applicable.
  • Balance the order of Windows and Linux references, mentioning both platforms equally where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, and does not provide equivalent Azure CLI or Linux/macOS command examples. While some mention of 'az resource' exists, PowerShell is emphasized and listed first, creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for resource deletion and creation.
  • List both PowerShell and Azure CLI options side-by-side, or clarify which tools are cross-platform.
  • Explicitly state that Azure CLI is supported on Linux/macOS and provide links to relevant documentation.
  • Where possible, include ARM template usage examples that are platform-agnostic.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides several critical operational examples (such as disabling and removing nodes) exclusively using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning or providing equivalent commands or guidance for Linux environments. This creates friction for Linux users, who may not have access to PowerShell or may prefer bash/CLI alternatives. Additionally, the documentation does not clarify whether these commands are available cross-platform, nor does it offer Azure CLI or REST API equivalents where possible.
Recommendations
  • For each PowerShell example (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode), provide equivalent Azure CLI, REST API, or bash script examples suitable for Linux users.
  • Clearly indicate if certain commands are only available on Windows, and provide alternative approaches for Linux clusters.
  • Add a section or note summarizing cross-platform management options for Service Fabric clusters, including links to Linux-specific tools or documentation.
  • Where programmatic examples are given (e.g., C#), clarify if they are cross-platform and provide guidance for running them on Linux (e.g., using .NET Core).
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows tools) parameters and workflows before those for SFCTL (cross-platform CLI), and provides more detailed parameter tables and examples for PowerShell/Visual Studio. SFCTL (the primary Linux/macOS tool) is covered later and less extensively. There are no explicit Linux/macOS examples or parity tables, and the PowerShell/Visual Studio sections dominate the page, which may cause friction for non-Windows users.
Recommendations
  • Reorganize the documentation to introduce SFCTL (cross-platform CLI) parameters and workflows before or alongside PowerShell/Visual Studio.
  • Provide equivalent examples for SFCTL commands wherever PowerShell examples are given.
  • Add a parity table or mapping between PowerShell/Visual Studio parameters and SFCTL/REST equivalents.
  • Explicitly mention that SFCTL is the recommended tool for Linux/macOS users at the top of the page.
  • Ensure that all parameter descriptions and workflows are equally detailed for SFCTL as for PowerShell/Visual Studio.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides code examples for configuring Service Fabric placement policies primarily using C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI or REST API) are provided. The PowerShell examples are consistently shown alongside C# code, with no mention of cross-platform alternatives or Linux-native tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API or ARM template approaches for configuring placement policies, which are platform-agnostic.
  • Explicitly note any limitations or differences for Linux clusters, if applicable.
  • Consider reordering examples to show cross-platform tools first or in parallel with PowerShell.
  • Clarify whether PowerShell examples are required or if alternatives exist for Linux/macOS 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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux shell (e.g., Bash/CLI) examples or mention cross-platform tools. PowerShell is a Windows-centric tool, and its exclusive use in command-line examples creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services with move cost settings, if supported.
  • Clarify if PowerShell commands are available cross-platform (e.g., via PowerShell Core) or if they require Windows.
  • Explicitly mention any platform limitations for the provided tools.
  • Consider including REST API or ARM template examples, which are platform-agnostic.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for the Azure Service Fabric application resource model demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any equivalent Azure CLI or Bash examples. The application packaging step is described using Visual Studio (a Windows-centric tool), and directory paths use Windows-style notation. There are no Linux/macOS-specific instructions or alternative workflows provided, even though Azure Resource Manager and Service Fabric support cross-platform tooling.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion alongside PowerShell commands.
  • Include instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, zip utilities) instead of only Visual Studio.
  • Show directory paths in both Windows and Linux/macOS formats.
  • Mention that all steps can be performed from Linux/macOS and provide relevant guidance.
  • Clarify that PowerShell is not required and that Azure CLI is supported on all platforms.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides security guidance for Azure Service Fabric clusters, referencing both Azure-hosted and standalone Windows clusters. However, it consistently presents Windows-specific instructions and links before any mention of Linux, and omits explicit examples or guidance for standalone Linux clusters. Certificate security is described as applicable to both platforms, but only Windows standalone cluster links are provided. Windows authentication (Kerberos) is discussed without Linux equivalents, and recommendations for standalone clusters are exclusively Windows-focused.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication options.
  • Clarify which security scenarios and features apply equally to Linux and Windows, and provide parity in examples and walkthroughs.
  • Where Windows-specific tools (e.g., Windows certificate services, MakeCert.exe) are mentioned, offer Linux alternatives (such as OpenSSL) and instructions.
  • Ensure that recommendations for standalone clusters include Linux scenarios, or clearly state if Linux standalone clusters are not supported.
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 primarily uses Windows-based examples and references, such as referencing the Windows Server 2016 Container Sample, specifying Windows file paths (e.g., c:\VolumeTest\Data), and mentioning Windows-specific tools like 'winver' for OS build detection. There is minimal mention of Linux equivalents, and no Linux-specific manifest examples or guidance are provided, despite Service Fabric supporting Linux containers.
Recommendations
  • Add Linux-based container manifest examples, referencing the Linux sample repository if available.
  • Include Linux file path conventions (e.g., /mnt/VolumeTest/Data) alongside Windows paths in volume examples.
  • Mention Linux tools for OS build/version detection (e.g., 'cat /etc/os-release', 'uname -r') where 'winver' is referenced.
  • Clarify which features or manifest settings are cross-platform and which are Windows-only.
  • Provide links to Linux container documentation and samples for Service Fabric.
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 examples for creating services and managing Service Fabric hosting models, but does not include equivalent CLI or Linux-native examples. Windows/PowerShell tools are referenced first and exclusively in command-line scenarios, creating friction for Linux/macOS users who may use Azure CLI or REST APIs. The documentation does not mention Linux-specific tools or provide guidance for non-Windows environments.
Recommendations
  • Add Azure CLI examples for service creation and management alongside PowerShell examples.
  • Explicitly mention REST API usage as a cross-platform option, and provide sample REST payloads or curl commands.
  • Clarify which tools are available on Linux/macOS and provide links or instructions for those platforms.
  • Consider including a section or note about Service Fabric support and tooling differences between Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users who cannot use PowerShell natively.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Include REST API examples for health reporting and querying, which are platform-agnostic.
  • Mention cross-platform tools and patterns alongside PowerShell, not just after or instead of it.
  • Clarify in the example section that PowerShell is one option, and link to Linux/macOS alternatives.
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 references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (such as Azure CLI or Bash), and no mention of cross-platform deployment tools or workflows.
Recommendations
  • Add examples and links for Linux/macOS users, such as using Azure CLI or Bash scripts to retrieve the cluster manifest and deploy applications.
  • Provide parity in deployment instructions, referencing cross-platform tools (e.g., Azure CLI, REST API usage with curl) alongside PowerShell.
  • Clarify which steps or tools are cross-platform and which are Windows-specific, to help users on non-Windows systems.
  • Include a note or section for Linux/macOS users outlining recommended workflows and tools.
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-centric examples for VM creation and disk attachment (e.g., 'Win2016Datacenter' as the VM image in CLI and PowerShell commands). There are no explicit Linux VM image examples or Linux-specific guidance, despite the article stating applicability to Linux VMs. This creates friction for Linux users, who must infer the necessary changes for their environment.
Recommendations
  • Provide parallel examples for Linux VM creation and disk attachment, using a Linux image (e.g., 'UbuntuLTS' or 'CentOS') in CLI and PowerShell commands.
  • Explicitly mention how to adapt commands for Linux VMs, including authentication options (e.g., SSH keys instead of passwords).
  • Add a note or section clarifying any OS-specific considerations for Ultra Disks, such as filesystem formatting or disk partitioning steps for Linux.
  • Ensure that all code snippets and instructions are equally applicable to both Linux and Windows, or provide separate tabs/examples for each.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.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 lists Azure PowerShell before Linux-native tools (Azure CLI), and provides a direct link to a Windows rescan function, but only a generic link for Linux. There are no explicit Linux shell/command examples, and the rescan process for Linux is less detailed than for Windows.
Recommendations
  • Provide explicit Linux shell command examples for rescanning disks (e.g., using 'echo 1 > /sys/class/block/<device>/device/rescan' or 'lsblk').
  • List Azure CLI (cross-platform) before Azure PowerShell to avoid Windows-first impression.
  • Include parity in detail for both Linux and Windows rescan steps, possibly with example commands and expected outputs.
  • Clarify that both Azure CLI and PowerShell are cross-platform, but highlight native Linux tools for Linux VMs.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a Windows-centric AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') and does not show a Linux/macOS equivalent. The AzCopy command is given only in Windows syntax, and the Windows path is used. While the rest of the CLI instructions are cross-platform, the upload step is biased toward Windows users, potentially confusing Linux/macOS users who need to use AzCopy differently.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
  • Mention that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Clarify that the AzCopy command syntax and path format differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS AzCopy commands side-by-side.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more detailed, with multiple scenarios and screenshots. This ordering and emphasis may create friction for Linux users, as PowerShell is not a native tool on Linux and Azure CLI is more commonly used in Linux environments. The OS-level section does provide Linux-native commands, but platform-level validation is PowerShell-first.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is the default cross-platform tool and more relevant for Linux users.
  • Ensure Azure CLI coverage is as detailed as PowerShell, including all scenarios and screenshots.
  • Clearly indicate that PowerShell is optional and primarily for users who prefer it, not required for Linux VM management.
  • Add explicit guidance for Linux users on installing and using Azure CLI if not already present.
  • Consider grouping PowerShell and Azure CLI examples together, or providing tabs for each tool, to avoid implicit prioritization.
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 covers both Linux and Windows VM image creation with Azure Image Builder, and provides parity for most features and examples. However, there is a notable Windows bias in several areas: PowerShell is frequently referenced for checksum generation and operational commands, Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, and Windows tools (e.g., PowerShell cmdlets) are often mentioned before or instead of Linux equivalents. While Linux examples and shell customizers are present, instructions for generating checksums and some operational steps (e.g., validation, generalization) prioritize Windows/PowerShell. Windows customizer types are more numerous and described in greater detail than Linux equivalents.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell commands, especially for checksum generation (e.g., always mention 'sha256sum' alongside 'Get-FileHash').
  • Ensure Linux shell customizer examples are as detailed as Windows PowerShell examples, including advanced usage (e.g., error handling, exit codes).
  • When listing customizer types, avoid listing Windows types first unless there is a technical reason; alternate or group by OS.
  • For operational steps (e.g., starting/cancelling builds), ensure Azure CLI examples are shown before or alongside PowerShell, and clarify CLI works cross-platform.
  • Where Windows-only customizers exist (e.g., WindowsRestart, WindowsUpdate), explicitly state Linux alternatives or limitations.
  • Expand Linux validation examples to match the detail of Windows validation (e.g., show advanced shell validation scenarios).
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
Although the page is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are presented extensively, sometimes before or alongside Azure CLI examples. Windows-specific tools and patterns (such as PowerShell scripts, SAS token generation via PowerShell, and REST/ARM template examples referencing .ps1 scripts) are used without Linux/bash equivalents. Some explanations and examples reference Windows behaviors or tools (e.g., 'ipconfig' as a commandId, referencing Windows VM usage, and script examples using Write-Host or .ps1 files), and there are missing Linux/bash script examples in REST and ARM template sections.
Recommendations
  • Ensure REST API and ARM template script examples use Linux/bash scripts (e.g., .sh files, echo/ls/id commands) instead of PowerShell/.ps1.
  • Where PowerShell tooling is referenced, provide equivalent Azure CLI or bash examples for Linux users, especially for SAS token generation and blob operations.
  • Clarify when a command or parameter is Windows-specific (e.g., 'ipconfig' commandId) and provide Linux alternatives (e.g., 'ifconfig', 'ip').
  • In sections describing parameter passing, show explicit Linux/bash script examples and clarify differences in script invocation.
  • Avoid referencing Windows VM behaviors (e.g., 'Secondary Logon' service) unless necessary, and clearly separate Linux and Windows instructions.
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux users.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides a mix of JSON ARM template snippets and PowerShell scripts for certificate management in Service Fabric clusters. The only explicit scripting example for certificate enrollment uses PowerShell (with Az modules), and references to the Key Vault VM extension are Windows-specific. The documentation repeatedly refers to Windows tools and patterns (e.g., S-channel, Windows certificate store, Key Vault VM extension for Windows), and troubleshooting/FAQ sections only provide PowerShell-based automation examples. Linux equivalents (such as Bash/CLI, Key Vault VM extension for Linux, or Linux certificate store handling) are not mentioned or illustrated, and Windows-specific mechanisms are discussed before any cross-platform alternatives.
Recommendations
  • Add Azure CLI (az) or Bash scripting examples for certificate enrollment and management alongside PowerShell examples.
  • Explicitly document the Key Vault VM extension for Linux, including its configuration and limitations, or clarify if it is not supported.
  • Discuss Linux certificate store handling and how Service Fabric on Linux nodes interacts with certificates, including any differences in ACLing or provisioning.
  • Provide troubleshooting steps and automation examples for Linux/macOS environments.
  • Clearly indicate which steps or mechanisms are Windows-only, and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.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 references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions and provides examples focused on these Windows images. There is no mention of Linux container images, Linux-specific cleanup patterns, or parity for Linux container scenarios. The examples and descriptions prioritize Windows containers and tools, potentially creating friction for Linux/macOS users deploying Linux containers on Service Fabric.
Recommendations
  • Add examples and explanations for Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
  • Clarify whether the cleanup and management features apply equally to Linux containers and Service Fabric clusters running on Linux VMs.
  • Include sample configurations and descriptions relevant to Linux container scenarios.
  • Explicitly state any limitations or differences between Windows and Linux container image management in Service Fabric.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation provides a comprehensive overview of X.509 certificate-based authentication in Service Fabric clusters, but there is evidence of Windows bias. Windows-specific tools and terminology (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI2 logging, and error codes) are mentioned first or exclusively, with Linux equivalents only briefly referenced (e.g., 'var/lib/sfcerts'). Troubleshooting sections focus on Windows event logs and tools, with little guidance for Linux users. Examples and configuration snippets use Windows-centric paths and concepts.
Recommendations
  • Provide Linux-specific troubleshooting guidance, including log locations and relevant tools (e.g., journalctl, syslog, Service Fabric logs on Linux).
  • Expand on Linux certificate store handling, including how certificates are provisioned and managed in Linux clusters.
  • Include Linux/macOS equivalents for error codes and diagnostic steps.
  • Ensure that configuration examples and explanations mention Linux paths and behaviors alongside Windows, not as an afterthought.
  • Clarify any differences in certificate handling or validation between Windows and Linux nodes.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. However, it exclusively uses PowerShell for CLI-based scripting examples and does not provide equivalent Azure CLI (az) or bash examples, which are preferred by Linux/macOS users. There is no mention of cross-platform tools or scripting approaches outside of PowerShell, and PowerShell is presented as the only scripting option. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown only with PowerShell (add, remove, scale, configure placement properties, etc.).
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell is required, and provide installation guidance for Linux/macOS if relevant.
  • Reorder sections or provide parallel examples so that Azure CLI and ARM template approaches are shown before or alongside PowerShell.
  • Clarify in notes when a feature or command is only available in PowerShell and provide workarounds or alternatives for Linux/macOS users where possible.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page presents RunToCompletion semantics in Service Fabric, but all code examples and container references are Windows-specific (Windows Server containers, Windows NanoServer images, Windows command syntax). Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux CLI or Bash equivalents. There are no examples or guidance for Linux containers or non-Windows environments, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • Provide guidance for querying deployment status using Linux tools (such as Bash, sfctl CLI, or REST APIs).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, include relevant code samples.
  • Present examples for both Windows and Linux environments, or explicitly state if RunToCompletion is Windows-only.
  • Mention Linux container compatibility considerations alongside Windows container version compatibility.
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_tools ⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation contains evidence of Windows bias, notably in the warning that recommends using Visual Studio to open the ServiceFabricServiceModel.xsd file located at a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). Additionally, the ApplicationManifest.xml section references the ServiceFabric PowerShell module for creating service instances, without mentioning Linux equivalents or cross-platform CLI options. Windows tools and patterns are mentioned first and exclusively, with no Linux/macOS alternatives or parity guidance.
Recommendations
  • Provide instructions for validating XML schema ordering using cross-platform tools (e.g., VS Code, xmllint, or other editors) and note the location of the schema file on Linux/macOS installations.
  • Mention and provide examples for using Azure CLI or Service Fabric CLI (sfctl) for service management, especially for creating service instances, alongside PowerShell examples.
  • Clarify any differences in file paths or tooling between Windows and Linux/macOS environments.
  • Ensure that cross-platform development environments are referenced, not just Visual Studio and Windows-specific paths.
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-specific commands or cross-platform CLI options are given, and Windows tools are referenced first and exclusively.
Recommendations
  • Add equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, if available.
  • Clarify whether Service Fabric Explorer is accessible from Linux/macOS or provide alternative cross-platform management tools.
  • Include Linux/macOS-compatible instructions or note any limitations for non-Windows users.
  • Explicitly state if certain operations are Windows-only, to help set expectations for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Migrate an Azure Service Fabric cluster to availability zone support ...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page provides migration guidance for Azure Service Fabric clusters to availability zone support. While the main content is platform-neutral and focuses on Azure Resource Manager templates, the step-by-step migration for nonmanaged clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell scripts and cmdlets (e.g., New-AzureRmResourceGroupDeployment, Connect-ServiceFabricCluster, Disable-ServiceFabricNode, Remove-ServiceFabricNodeState, Remove-AzureRmVmss, Remove-AzureRmLoadBalancer, Remove-AzureRmPublicIpAddress, Set-AzureRmPublicIpAddress). These are Windows-centric tools, and no equivalent Azure CLI or Bash examples are provided. Additionally, the PowerShell examples are given exclusively and prominently, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell steps, especially for resource deployment, node disabling/removal, and DNS updates.
  • Add Bash script examples or reference how to perform these actions using Azure CLI on Linux/macOS.
  • Clarify which steps require Windows/PowerShell and offer alternatives or links for cross-platform users.
  • Mention that Service Fabric management can be done from Linux/macOS using Azure CLI or REST API where applicable.
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 monitoring Azure Service Fabric on both Windows and Linux clusters, but there are several areas where Windows tools and patterns are mentioned first or exclusively. Windows-specific tools (such as Event Log/Event Viewer, ETW, Diagnostics Agent) are described in detail, while Linux equivalents (such as LTTng, Syslog) are referenced but not explained as thoroughly. Some example/tutorial links focus on .NET applications, which are more common on Windows, and Windows cluster monitoring is often described before Linux. Linux-specific configuration and examples are less prominent, and in some cases, only referenced via links rather than explained inline.
Recommendations
  • Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and event collection.
  • Ensure that Linux tools (LTTng, Syslog, Azure Monitor agent configuration) are described with equal detail and clarity as Windows tools (ETW, Event Log, Diagnostics Agent).
  • Add explicit Linux sample queries, configuration steps, and troubleshooting tips where Windows instructions are given.
  • When referencing tutorials or examples, clarify whether they apply to both Windows and Linux, and provide Linux alternatives if not.
  • Avoid listing Windows tools or patterns first unless they are more widely used; consider parallel presentation or clear separation.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation covers Azure Service Fabric application security in a generally platform-agnostic manner, but several sections exhibit Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned without Linux equivalents or with Linux options listed after Windows. Some examples and links are Windows-centric, and disk encryption is only described for Windows clusters, with Linux disk encryption left as a TODO. Linux-specific guidance is missing or less prominent in several areas.
Recommendations
  • Add explicit Linux examples and guidance for disk encryption, including supported tools and Azure integration.
  • Ensure parity in describing how to run services under different accounts on Linux clusters, including relevant Linux user/group management and security practices.
  • Provide Linux-specific instructions or links for certificate management and container security, matching the detail given for Windows features like gMSA.
  • When listing options (e.g., container certificate access), mention Linux and Windows equally, not Windows first.
  • Clarify which features are Windows-only and provide alternative recommendations for Linux users where possible.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation frequently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and cmdlets are often mentioned first or exclusively, with little to no explicit mention of Linux/macOS equivalents or cross-platform CLI usage (such as sfctl or Azure CLI). This creates friction for Linux/macOS users, who may need to infer or search for alternative commands.
Recommendations
  • Add explicit examples using sfctl (Service Fabric CLI), which is cross-platform, for each lifecycle operation (deploy, upgrade, remove, etc.).
  • Where PowerShell cmdlets are referenced, also provide equivalent Azure CLI or sfctl commands, and mention their applicability to Linux/macOS.
  • Reorder examples so that cross-platform tools (REST API, sfctl, Azure CLI) are presented before or alongside Windows/PowerShell examples.
  • Clarify which tools are Windows-only and which are cross-platform, to help users select the right approach for their environment.
  • Include a section or table summarizing tool parity for Windows, Linux, and macOS users.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is heavily focused on PowerShell cmdlets for Service Fabric management and upgrade operations, with all command-line examples using PowerShell syntax. There are no examples or references to equivalent Linux tools (such as sfctl or Azure CLI), nor are cross-platform instructions provided. This creates friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI) for Linux/macOS users alongside PowerShell examples.
  • Where possible, mention Azure CLI or REST API alternatives for upgrade and management operations.
  • Clarify in the introduction that PowerShell is used for examples, but cross-platform tools are available.
  • Link to documentation for sfctl and Azure CLI for users on non-Windows platforms.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides a PowerShell-only example for removing Service Fabric application resources and references PowerShell before CLI in the 'Next steps' section. There are no equivalent CLI (az or sfctl) or REST/cURL examples for Linux/macOS users, and the PowerShell script is presented as the primary method for resource removal.
Recommendations
  • Add equivalent Azure CLI (az) and/or Service Fabric CLI (sfctl) examples for removing application resources, alongside the PowerShell example.
  • When referencing deployment/removal tools, mention CLI and PowerShell together, or list CLI first to avoid Windows-first bias.
  • Provide REST API examples using cURL for cross-platform parity.
  • Clarify in the text that all operations can be performed from Linux/macOS using CLI or REST, not just PowerShell.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page on Azure Service Fabric architecture references PowerShell cmdlets as a primary management interface and mentions Windows security as a transport option. PowerShell is a Windows-centric tool, and its mention as the main example creates friction for Linux/macOS users. However, the page is largely conceptual and does not provide explicit command-line examples or Windows-only instructions.
Recommendations
  • Mention cross-platform management options, such as Azure CLI or REST APIs, alongside PowerShell cmdlets.
  • Clarify that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide links to Linux/macOS-specific guidance.
  • When referencing security options, note Linux-compatible alternatives (e.g., X509 certificates) and their parity.
  • Ensure that any tooling or management references are inclusive of non-Windows platforms where possible.
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 for on-demand backup in Azure Service Fabric is heavily focused on PowerShell and Windows tooling. All code examples use PowerShell, including REST API calls, and there are no equivalent Linux/macOS command-line examples (such as Bash/cURL or Azure CLI). The prerequisite section requires installation of a PowerShell module, and the workflow assumes Windows environments. REST API usage is demonstrated only via PowerShell, not via cross-platform tools. This creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Bash/cURL examples for REST API calls, showing how to trigger backups and track progress from Linux/macOS.
  • Mention Azure CLI commands if available for backup/restore operations.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all environments, or if REST API calls can be made directly from any platform.
  • Reorder examples so that cross-platform approaches (REST API via cURL, Azure CLI) are presented before or alongside PowerShell.
  • Explicitly note platform requirements and alternatives for Linux/macOS users.
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 shows a notable Windows/PowerShell bias. The only concrete example for performing an upgrade uses PowerShell cmdlets, with no equivalent CLI or Linux/macOS example provided. References to Windows-specific tools (e.g., PowerShell, http.sys) are present, and the 'Next steps' section prioritizes Visual Studio and PowerShell tutorials, both of which are primarily Windows-centric. There is no mention of cross-platform tools (such as Azure CLI or REST API) for Linux/macOS users, making it harder for non-Windows users to follow or replicate the documented procedures.
Recommendations
  • Add equivalent examples using Azure CLI, REST API, or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
  • When referencing PowerShell, explicitly note if the same operation can be performed via sfctl or Azure CLI, and provide links or code samples.
  • In the 'Next steps' section, include tutorials or documentation for upgrading applications using cross-platform tools.
  • Clarify any Windows-only limitations (e.g., http.sys behavior) and provide Linux/macOS-specific guidance where applicable.
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 ⚠ī¸ windows_first
Summary
The documentation page is generally cross-platform, but the 'File share' backup storage section exclusively describes Windows-style UNC paths (\\StorageServer\BackupStore) and Windows authentication methods, without mentioning Linux-compatible alternatives (e.g., SMB mounts on Linux, NFS, or Azure Files usage from Linux). Additionally, Windows authentication is presented first, and no Linux-specific guidance is provided for file share access.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux nodes, such as using SMB mounts, NFS, or Azure Files.
  • Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide Linux-compatible path formats and authentication methods.
  • Mention Azure Files as a cross-platform file share solution and provide instructions for Linux access.
  • Where authentication methods are discussed, include Linux approaches (e.g., mount options, credential files) alongside Windows authentication.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is used exclusively for cluster upgrade operations. Windows-specific registry settings and VM configuration properties are discussed without Linux equivalents. There are no Linux shell (bash) or cross-platform scripting examples for key operations, and Windows-specific instructions (e.g., registry edits, PowerShell commands) are presented without parallel Linux guidance.
Recommendations
  • For every PowerShell example, provide an equivalent bash or Azure CLI example where possible, especially for cluster upgrade operations.
  • When discussing Windows-specific VM configuration (e.g., registry keys, Windows Update settings), clarify if and how these steps apply to Linux clusters, or provide Linux equivalents if relevant.
  • Clearly indicate when a step or configuration is Windows-only, and provide links or references to Linux-specific guidance.
  • Consider reordering examples to present cross-platform (CLI, ARM templates) or Linux-first examples where appropriate, or at least present both together.
  • For application package creation, mention or link to Linux/macOS-compatible tooling or scripts if available.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page exclusively provides PowerShell-based examples and instructions for restoring backups in Azure Service Fabric. All code samples, module installation steps, and REST API calls are shown using PowerShell, with no mention of Linux/macOS-compatible tools or CLI alternatives. The Microsoft.ServiceFabric.Powershell.Http module is required, and there are no Bash, Azure CLI, or cross-platform REST client examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for REST API calls.
  • Document how to perform REST API operations using curl or other cross-platform tools.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is available on Linux/macOS PowerShell Core, or provide alternatives.
  • Include guidance for Linux/macOS users on connecting to Service Fabric clusters and authenticating REST calls.
  • Consider providing sample JSON payloads and HTTP headers for manual REST calls.
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, but Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are mentioned first or exclusively in several sections. Windows examples and terminology often precede Linux equivalents, and some sections (e.g., Windows Defender, DSC) are Windows-only without Linux alternatives or parity guidance.
Recommendations
  • Where possible, present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
  • For sections like Windows Defender and DSC, add explicit notes or links to Linux security best practices or equivalent tools (e.g., recommend Linux antivirus solutions or configuration management tools).
  • Expand Linux guidance for certificate management and secret encryption, ensuring parity in detail and clarity with Windows instructions.
  • Clarify when a feature or recommendation is Windows-only and provide Linux alternatives or workarounds where feasible.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology (e.g., 'certificate store', 'MY', 'LocalMachine', 'NTLM', 'Windows Fabric Replicator') is used throughout, and Windows-centric defaults (e.g., ContainerNetworkSetup default TRUE for Windows, FALSE for Linux) are mentioned. References to Windows tools and patterns (certificate stores, NTLM authentication, Windows Defender Firewall) are frequent, while Linux equivalents are not always explained or are mentioned second. Some settings are described as 'Windows only' without Linux alternatives or guidance. Linux-specific settings (e.g., LinuxExternalExecutablePath, EnforceLinuxMinTlsVersion, X509Folder) are present but less prominent, and there are few explicit Linux/macOS examples or guidance for certificate management, firewall, or authentication. The page is not Windows-only, but Linux parity could be improved.
Recommendations
  • Add explicit Linux/macOS guidance for certificate management, including how to configure and locate certificates and stores on Linux.
  • Provide Linux/macOS equivalents for NTLM authentication, or clarify if/how these features are supported on Linux.
  • Where Windows-specific defaults or tools are mentioned (e.g., 'MY', 'LocalMachine', Windows Defender Firewall), add Linux/macOS equivalents or note differences.
  • Ensure Linux-specific settings are described with equal detail and visibility as Windows settings.
  • Add examples or links for Linux/macOS cluster configuration and upgrade processes, not just Windows.
  • Clarify which settings are cross-platform and which are Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides some cross-platform coverage (e.g., mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode' in the extension type), but several sections and examples show a Windows-first bias. The 'dataPath' example uses a Windows-style path ('D:\\SvcFab') without a Linux equivalent. The 'Next steps' section links to PowerShell scripts for RDP port changes and admin credential updates, which are Windows-specific tasks, with no Linux/SSH equivalents referenced. There are no explicit Linux/macOS command-line examples or guidance for Linux-based clusters.
Recommendations
  • Provide Linux-specific examples for properties like 'dataPath' (e.g., '/var/lib/sfdata').
  • Add guidance or links for SSH access and Linux admin credential management in the 'Next steps' section, parallel to the RDP/PowerShell links.
  • Clarify when instructions or scripts are Windows-only, and offer Linux alternatives where possible.
  • Include at least one Linux-focused walkthrough or screenshot if the feature is supported on Linux.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation consistently provides PowerShell examples for managing Service Fabric Application Groups, but does not offer equivalent CLI or Bash examples for Linux/macOS users. All command-line instructions use PowerShell cmdlets, which are native to Windows. There is no mention of cross-platform tools or Azure CLI alternatives, and the PowerShell examples are always presented before the C# code samples.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlet usage, if supported.
  • If Azure CLI does not support these operations, clarify this limitation and suggest any available cross-platform workarounds.
  • Mention whether PowerShell Core (pwsh) can be used on Linux/macOS for these cmdlets, and provide guidance if so.
  • Consider including Bash or REST API examples for relevant operations.
  • Explicitly state platform requirements for Service Fabric management tools.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell, but does not offer equivalent Linux/macOS CLI examples (e.g., Azure CLI, Bash, or REST API). PowerShell commands are featured prominently, and no Linux-native tools or cross-platform command-line patterns are shown. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tooling.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for relevant operations, enabling users on any OS to automate tasks.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Bash scripts or Azure CLI, and link to their documentation.
  • Clarify which operations require PowerShell and which can be performed using other tools.
  • Consider reordering examples so that cross-platform options are shown first, or at least alongside PowerShell.
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 PowerShell examples for configuring auto scaling policies, but does not offer equivalent Linux/macOS CLI or scripting examples (e.g., Bash, Azure CLI). Windows-specific tools (PowerShell) are presented alongside C# and manifest examples, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users, who must translate PowerShell commands or rely on C# APIs.
Recommendations
  • Add Azure CLI or Bash script examples for configuring scaling policies, especially for Linux/macOS users.
  • Explicitly mention whether PowerShell commands can be run cross-platform (e.g., PowerShell Core), or provide guidance for Linux users.
  • Clarify any limitations or differences for Linux clusters, especially regarding resource monitoring and scaling.
  • Consider including REST API examples, which are platform-agnostic.
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 ⚠ī¸ windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific XML examples are consistently presented first, and the only explicit platform reference in the infrastructure example is <WindowsServer>. PowerShell examples are included for service creation and updating, but there are no Linux shell or CLI equivalents. The documentation does not mention Linux-specific tools or patterns, nor does it clarify Linux/macOS support or differences. The bias is moderate: Linux users can complete the tasks using JSON configuration and .NET APIs, but Windows tools and patterns are prioritized.
Recommendations
  • Add explicit examples and guidance for Linux-based Service Fabric clusters, including references to Linux node configuration and supported OS types.
  • Provide Azure CLI or Bash shell examples alongside PowerShell for service creation and updates.
  • Clarify whether the XML manifest applies only to Windows clusters, and if so, provide Linux equivalents or links.
  • Mention any platform-specific limitations or considerations for Linux/macOS users.
  • Ensure parity in ordering: present JSON (cross-platform) examples before or alongside Windows XML examples.
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-style paths and commands. No equivalent Linux/macOS CLI or REST API example is given, and the PowerShell example appears as the only practical demonstration of interacting with the cluster. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform management but only Windows tooling is shown.
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-agnostic.
  • Mention that PowerShell is one option, but highlight cross-platform alternatives for cluster management.
  • Ensure paths and command prompts are not Windows-specific unless the feature is Windows-only.
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 Azure CLI). PowerShell is presented as the primary scripting interface, and no mention is made of cross-platform alternatives or Linux-specific guidance. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI or Bash examples for all PowerShell commands, especially for service creation and updates.
  • Clarify whether PowerShell commands are supported cross-platform or provide guidance for Linux/macOS users.
  • Mention any limitations or alternative approaches for Linux/macOS users in relevant sections.
  • Consider referencing REST API endpoints or SDKs that are platform-agnostic.
GitHub Create Pull Request
Service Fabric Azure Service Fabric dynamic node tags ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for managing node tags and service tag requirements, but does not include equivalent Linux/bash/CLI examples. PowerShell is presented first in each example section, and there is no mention of cross-platform CLI tools or REST API usage for these operations, despite Service Fabric supporting REST APIs and having a CLI. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI workflows.
Recommendations
  • Add Azure CLI or Service Fabric CLI (sfctl) examples for managing node tags and service tag requirements.
  • Include REST API usage examples for tag operations, as REST APIs are platform-agnostic.
  • Clarify which PowerShell commands are available cross-platform (e.g., in PowerShell Core) and which are Windows-only.
  • Present examples in a platform-neutral order, or group by platform, to avoid implicit Windows-first bias.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page on scaling Azure Service Fabric standalone clusters exhibits 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' guide is Windows Server-focused, and there is no mention of Linux tooling or procedures for scaling standalone clusters on Linux hosts.
Recommendations
  • Add examples and instructions for scaling standalone Service Fabric clusters running on Linux, including relevant CLI commands (e.g., sfctl) and configuration steps.
  • Mention cross-platform tools and approaches where possible, or clarify if certain procedures are Windows-only.
  • Provide parity in documentation structure, ensuring Linux users can follow the same scaling guidance with appropriate commands and references.
  • Link to Linux-specific scaling documentation if available, or note limitations if Linux standalone clusters are not supported.
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 patterns primarily using PowerShell and C#. PowerShell is a Windows-centric tool, and no equivalent Linux command-line examples (e.g., Bash, CLI) are given. Administrative actions are described using Windows tools first, and Linux alternatives are not mentioned. This creates friction for Linux users, who may not have access to PowerShell or may need to use Service Fabric CLI or REST APIs instead.
Recommendations
  • Add equivalent Linux-friendly examples using Service Fabric CLI (sfctl) or REST API calls alongside PowerShell examples.
  • Explicitly mention which administrative actions can be performed on Linux and provide guidance for Linux users.
  • Reorder examples to avoid always presenting Windows/PowerShell first, or clearly indicate platform-specific steps.
  • Clarify any platform limitations or differences in tooling for administrative tasks.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific tools (such as PowerShell and Visual Studio) are mentioned before Linux equivalents, Windows services and executables are described in detail, and standalone cluster creation is only supported on Windows. Linux examples and tools are less prominent, and some sections lack Linux-specific guidance or parity.
Recommendations
  • Ensure Linux tools (such as Bash, Linux CLI usage, and Linux-specific installation instructions) are mentioned alongside Windows tools, not after or omitted.
  • Provide Linux-specific examples and workflows where possible, especially for cluster creation, management, and health monitoring.
  • Clarify which features are Windows-only and which are cross-platform, and link to Linux documentation where available.
  • Add parity in example commands (e.g., show both PowerShell and Bash/CLI equivalents).
  • Highlight Linux support in introductory and next steps sections, not just Windows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page primarily references Windows-specific logging channels (ETW/Windows Event logs) and the Windows Azure diagnostics agent for accessing Service Fabric events. There are no explicit examples or instructions for accessing events on Linux-based Service Fabric clusters, nor are Linux tools or patterns mentioned. Windows tools and approaches are presented first and exclusively.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including relevant logging channels (e.g., stdout, syslog, or other Linux-native mechanisms).
  • Provide Linux-specific instructions or examples for configuring diagnostics and accessing logs, including any differences in agent configuration or log storage.
  • Mention cross-platform tools or APIs (such as EventStore REST APIs) earlier and emphasize their applicability to both Windows and Linux clusters.
  • Clarify which features or instructions are Windows-only and provide Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on PowerShell and Visual Studio workflows. PowerShell is mentioned first for application creation, and Visual Studio parameter files are discussed, both of which are primarily Windows-centric tools. Linux/macOS equivalents (such as sfctl and shell scripts) are mentioned, but not as prominently or in as much detail.
Recommendations
  • Provide Linux/macOS-specific examples and workflows alongside PowerShell/Visual Studio instructions.
  • Expand on the use of sfctl and shell scripts for parameter management, including detailed examples.
  • Ensure that Linux/macOS tools are given equal prominence and explanation as Windows tools.
  • Consider reordering sections so that cross-platform tools (sfctl, shell scripts) are presented before or alongside Windows-specific tools.
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 ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page provides networking patterns for Azure Service Fabric clusters, but all deployment and scripting examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. Windows-specific concepts like RDP and Windows-style paths are referenced, and Windows command-line examples (e.g., ping) are shown. There are no Linux/macOS equivalents or guidance for non-Windows users, creating friction for those deploying Service Fabric clusters from Linux or macOS.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include Bash shell command examples for template deployment and resource management.
  • Mention SSH as an alternative to RDP for accessing VMs, and provide Linux/macOS instructions for connecting to jump boxes.
  • Use generic file paths or note the differences between Windows and Linux/macOS file systems.
  • Provide guidance or links for Linux/macOS users on how to install and use Azure tools for Service Fabric cluster management.
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, mentions ApplicationManifest.xml (a Windows-centric deployment artifact), and references Visual Studio. While Linux support is discussed, Linux-specific instructions and examples are missing, especially for non-containerized services. Portal-based enablement is Windows-only, and Linux users must use ARM templates, but no Linux-focused example or CLI guidance is given.
Recommendations
  • Add Linux-specific instructions for enabling DNS service, including CLI (az CLI) or REST API examples.
  • Provide examples for setting DNS names using Linux-compatible tools (e.g., az CLI, YAML, or other deployment methods).
  • Clarify which steps are Windows-only and provide Linux alternatives where possible.
  • Include guidance for Linux users on how to verify DNS service status without relying on Service Fabric Explorer (if it is Windows-centric).
  • Explicitly state limitations and workarounds for Linux users in relevant sections.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is generally OS-neutral in its explanations of Service Fabric activation and deactivation lifecycle, but there is a subtle Windows/PowerShell bias. The only explicit tooling reference for deployment/removal is to PowerShell, and the 'Next steps' section links to PowerShell-based guides without mentioning Linux/CLI alternatives. There are no Linux-specific examples or cross-platform command-line instructions.
Recommendations
  • Add references to cross-platform deployment/removal guides using Azure CLI or Service Fabric CLI (sfctl), especially in the 'Next steps' section.
  • Where PowerShell is mentioned, clarify if the instructions are Windows-only and provide equivalent steps for Linux/macOS if available.
  • Consider including at least one Linux/macOS example or note on how to perform common lifecycle operations on non-Windows platforms.
  • Link to documentation for Service Fabric on Linux, if relevant, to help non-Windows users.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. It references Windows-specific concepts (e.g., NETWORKSERVICE account, Setup.bat, .exe files), and mentions the ServiceFabric PowerShell module as a way to create service instances, without offering Linux equivalents or examples. The manifest examples use Windows-style executables (.exe, .bat), and the security principal examples reference Windows system groups (Administrators, NetworkService). No Linux-specific guidance, tools, or examples are provided.
Recommendations
  • Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of .bat files, and referencing Linux user/group concepts.
  • Mention cross-platform tools (e.g., Azure CLI, sfctl) for managing Service Fabric applications, alongside or instead of PowerShell.
  • Clarify which features and manifest settings are supported on Linux clusters, and highlight any differences.
  • Provide sample manifests or code snippets that use Linux-compatible entry points and security principals.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no equivalent Linux/macOS tooling or examples provided. Additionally, PowerShell is highlighted as a primary upgrade method, which may create friction for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or REST APIs.
  • Mention Linux/macOS-compatible development environments (e.g., Visual Studio Code, JetBrains Rider) alongside Visual Studio.
  • Clarify if PowerShell examples are cross-platform (PowerShell Core), or provide Bash/Azure CLI alternatives.
  • Explicitly state platform requirements for upgrade tutorials, so Linux/macOS users know what is supported.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, it exhibits Windows bias by: (1) giving detailed attention to HTTP.sys, a Windows-only technology, including endpoint configuration and port sharing, (2) referencing Windows-specific tools (e.g., netsh) and APIs, (3) mentioning Windows features and HTTP.sys before Kestrel in several sections, and (4) lacking explicit Linux/macOS example snippets or guidance (such as how to configure Service Fabric for Linux, or how to debug/deploy on Linux/macOS). While Kestrel is recommended for cross-platform scenarios, Linux-specific considerations are not addressed, and all code samples are generic or Windows-centric.
Recommendations
  • Add explicit Linux/macOS guidance for Service Fabric and ASP.NET Core integration, including any OS-specific configuration steps.
  • Include example snippets or troubleshooting tips for Linux/macOS environments (e.g., directory paths, permissions, firewall configuration).
  • Clarify in each section which features are Windows-only (e.g., HTTP.sys, netsh) and which are cross-platform.
  • Provide links to Linux/macOS documentation for Service Fabric and ASP.NET Core where relevant.
  • Ensure Kestrel (cross-platform) examples are shown first or highlighted for Linux users.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and screenshots based on Windows tooling. There is no mention of Linux/macOS equivalents, nor are cross-platform CLI or SDK usage patterns discussed. The documentation assumes familiarity with Windows administrative tools and does not clarify whether the described APIs or features are available or usable on Linux-based Service Fabric clusters.
Recommendations
  • Explicitly state whether the PowerShell APIs are available on Linux/macOS, or provide equivalent CLI/SDK usage examples for those platforms.
  • Include examples using cross-platform tools such as Azure CLI, REST API, or .NET Core SDK (FabricClient) for managing replicas.
  • Clarify any platform limitations for the soft delete feature (e.g., if it is Windows-only, state so clearly).
  • Add screenshots or command output from Linux environments if applicable.
  • Reorder sections or examples to avoid always presenting Windows/PowerShell first.
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 in Service Fabric, with explicit Windows paths and commands (e.g., 'PS C:\>'). There are no equivalent Linux/bash CLI examples, and PowerShell is presented before REST and API options. This creates friction for Linux/macOS users, as Service Fabric supports cross-platform clusters and REST/CLI usage, but the documentation does not demonstrate parity.
Recommendations
  • Add equivalent bash/CLI examples for health reporting, using Azure CLI or Service Fabric CLI tools where available.
  • Clarify which PowerShell commands are available cross-platform (e.g., PowerShell Core) and which are Windows-only.
  • Present REST and API examples before or alongside PowerShell, emphasizing their cross-platform nature.
  • Explicitly mention Linux/macOS support and link to relevant tools or documentation for those environments.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page primarily uses Windows/PowerShell tooling for deployment examples (e.g., New-ServiceFabricApplication), references Windows file paths for schema files, and generally presents Windows-specific details before Linux equivalents. Linux-specific information is minimal and often relegated to brief notes.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI or sfctl) examples alongside or in place of PowerShell commands for deploying Service Fabric applications.
  • When referencing file paths (such as schema locations), include both Windows and Linux paths where applicable.
  • Ensure that Linux-specific behaviors (such as certificate store locations) are given equal prominence and explanation, not just brief notes.
  • Consider adding a dedicated section or callouts for Linux/macOS users, especially for deployment and certificate management steps.
  • Where possible, alternate the order of Windows and Linux examples to avoid implicit prioritization.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page focuses exclusively on Visual Studio workflows and features (such as Build/Rebuild/F5/Ctrl+F5/Publish) for Service Fabric applications, which are Windows-centric. It does not provide examples or guidance for Linux/macOS users, nor does it mention alternative tools or workflows for those platforms. References to PowerShell are present, but only as a passing mention, and no Linux equivalents (such as Bash or CLI commands) are provided.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide examples using Azure CLI, Bash, or other cross-platform tools for deploying Service Fabric applications.
  • Clarify which features are Visual Studio/Windows-only and suggest alternative workflows for non-Windows environments.
  • Include sample commands or scripts for Linux-based Service Fabric clusters, if supported.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page provides examples for using the Fault Analysis Service via C# and PowerShell, but does not mention or provide equivalent examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). The PowerShell example assumes Windows environments and tools, and there is no guidance for Linux users on how to interact with the Fault Analysis Service.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
  • Mention any prerequisites or SDKs for Linux/macOS environments, if available.
  • If PowerShell Core is supported on Linux/macOS, clarify this and provide relevant instructions.
  • Ensure that documentation sections do not assume Windows-only tools unless the feature is Windows-specific.
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 and Linux information, but there is a notable Windows bias in several areas. Windows-specific properties and configuration options are discussed first and in greater detail. PowerShell examples are presented before Azure CLI examples, and ARM/Bicep template snippets default to Windows images. Some explanations reference Windows tools and concepts (e.g., drive letters, Windows Update) without equivalent Linux context. However, Linux is supported and referenced throughout, and CLI examples are present.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first for cross-platform parity.
  • Provide ARM/Bicep template snippets that default to a Linux image, or show both Windows and Linux examples.
  • When discussing OS-specific configuration (e.g., drive letters, Windows Update), add equivalent Linux context (e.g., mount points, package managers).
  • Clarify in requirements and configuration sections which steps are Windows-specific and which apply to Linux, to avoid confusion.
  • Ensure Linux-specific troubleshooting and error scenarios are covered alongside Windows examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides examples and references that are either Windows-centric or lack explicit Linux parity. For instance, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, but no Linux/CLI equivalent is mentioned. The only command-line example uses Azure CLI, which is cross-platform, but there are no explicit Linux-specific examples or notes. Additionally, in the Managed Identity section, the link references a Windows VMSS portal guide, which may confuse Linux users. Overall, the documentation assumes Windows familiarity in some areas and omits Linux-specific guidance.
Recommendations
  • Add explicit Linux/CLI equivalents for features currently described as 'via PowerShell', such as Azure Site Recovery.
  • Ensure that links and examples for Managed Identity and other features reference both Windows and Linux documentation or clarify applicability.
  • Include Linux-specific examples or notes where relevant, especially in sections referencing command-line tools or extensions.
  • Review feature tables and FAQs to ensure Linux parity is clearly stated for each feature.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ powershell_heavy
Summary
The documentation covers both Windows and Linux VMs in its scope and provides Azure CLI, PowerShell, Portal, API, and ARM template instructions. However, there are signs of Windows bias: ARM template and some examples default to Windows images, and PowerShell is given equal prominence to CLI (which is cross-platform), but there are no explicit Bash or Linux shell script examples. The ARM template only shows Windows image configuration, and password-based admin setup is described, which is more common for Windows VMs. Linux-specific details (e.g., SSH keys, Linux image references) are missing in ARM and Portal steps.
Recommendations
  • Add explicit Linux ARM template examples, including a Linux image reference and SSH key authentication.
  • In the ARM template, provide a parameter or example for a Linux image (e.g., Ubuntu) and show how to configure SSH authentication.
  • In the Portal steps, mention SSH key setup for Linux VMs, not just username/password.
  • Where PowerShell is shown, clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider adding Bash script examples for common tasks.
  • Ensure that examples and screenshots (if any) alternate or show parity between Windows and Linux VM creation and management.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks. However, PowerShell examples are extensive, use Windows-specific patterns (e.g., ConvertTo-SecureString, System.Management.Automation.PSCredential), and are presented immediately after the Azure CLI section. Resource Manager Template examples are also shown using PowerShell commands for deployment, rather than cross-platform CLI or ARM template JSON. The 'Next steps' section links to a PowerShell-focused sample repository. There is no explicit Linux/macOS bias, but Windows/PowerShell tools and patterns are featured heavily and often first.
Recommendations
  • Add explicit Linux/macOS guidance for running Azure CLI commands, including notes about shell differences and SSH key generation.
  • Provide Resource Manager Template deployment examples using Azure CLI (az deployment group create) instead of only PowerShell.
  • Clarify that PowerShell examples are for Windows users, and suggest cross-platform alternatives for Linux/macOS users.
  • Link to cross-platform sample repositories or documentation in 'Next steps', not only PowerShell-focused resources.
  • Consider balancing the order of examples so that CLI and PowerShell are presented equally, or alternate which comes first.
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 provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links appear first and more prominently. The custom RBAC role section links only to a PowerShell-based guide, potentially creating friction for Linux/macOS users. However, CLI options are mentioned for some tasks, and the feature itself is not Windows-specific.
Recommendations
  • Add links and examples for creating custom RBAC roles using Azure CLI and/or Azure Portal, not just PowerShell.
  • Ensure CLI and PowerShell options are presented equally, ideally side-by-side or with CLI first for cross-platform parity.
  • Where possible, provide Linux/macOS-specific guidance or clarify that CLI commands work across platforms.
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 a Windows VM image (Win2016Datacenter) and Windows-style admin credentials. There are no explicit Linux VM deployment examples, and the PowerShell examples are inherently Windows-centric. This may cause confusion or extra work for Linux users, who must adapt the instructions to deploy Linux VMs.
Recommendations
  • Add explicit Linux VM deployment examples in the Azure CLI sections, using a popular Linux image (e.g., UbuntuLTS) and Linux-style admin credential setup.
  • Clarify in each CLI example that the VM image and authentication method can be changed for Linux VMs, and provide sample variable values for Linux scenarios.
  • Consider adding a short section or note explaining how to adapt the instructions for Linux VMs, including differences in admin username, password/SSH key authentication, and image selection.
  • Ensure that the 'Next steps' links to Linux-specific guides are more prominent or referenced earlier in the workflow.
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 strongly associated with Windows environments. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and provides installation instructions using cmd.exe and PowerShell. While Azure CLI examples are included, the PowerShell section is much more detailed and appears first. There are no explicit Linux shell (bash) examples or instructions for Linux-native package managers or tools. However, the feature itself is cross-platform and the documentation does mention Linux VMs and Linux disk managers (LVM, MDADM).
Recommendations
  • Add bash shell examples for Azure CLI usage, showing how to enable Write Accelerator from a Linux/macOS terminal.
  • Provide instructions for installing 'armclient' or equivalent REST API tooling on Linux/macOS, such as via pip, npm, or manual download, instead of only Chocolatey.
  • Reorder sections so Azure CLI examples appear before PowerShell, or provide parity in detail between PowerShell and CLI.
  • Explicitly mention that all PowerShell commands can be run on Linux/macOS via Azure PowerShell (if true), or clarify any OS limitations.
  • Include troubleshooting or configuration notes specific to Linux environments, such as SELinux, udev, or disk naming conventions.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment. .../includes/virtual-machines-disks-shared-limitations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA tools). The proximity placement groups section links to a Windows-specific URL, even though PPGs are not exclusive to Windows. The clustering limitations are always described in terms of Windows tools, with no Linux parity or examples.
Recommendations
  • Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
  • Provide links to Linux clustering documentation or Azure guidance for Linux HA scenarios.
  • Clarify if limitations apply to both Windows and Linux, or only Windows, and add Linux-specific notes where relevant.
  • Update proximity placement group links to reference a cross-platform or generic Azure documentation page, not a Windows-specific one.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows-centric tools and workflows (notably Hyper-V and the Convert-VHD PowerShell cmdlet) as the primary or sole method for creating and converting VHDs. Linux-native alternatives for VHD creation and conversion are not provided, and Hyper-V/PowerShell steps are described before or instead of Linux equivalents. This creates friction for Linux users who may not have access to Windows tools.
Recommendations
  • Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
  • List Linux and Windows tools side-by-side, or present Linux-first examples given the Ubuntu/Linux focus.
  • Clarify that Hyper-V/PowerShell are optional and not required if using Linux-native tooling.
  • Link to or include instructions for extracting and manipulating VHDs on Linux systems.
  • Explicitly mention cross-platform alternatives wherever a Windows-only tool is referenced.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally platform-neutral, but there are some subtle Windows biases. The description of nodes mentions an 'auto-start Windows service, FabricHost.exe,' and focuses on EXE/DLL file types in code packages. Windows terminology and tools (such as Windows services and EXE/DLLs) are referenced before or more prominently than Linux equivalents. However, Linux support is acknowledged in several places, and container support for both Windows and Linux is described. No critical Linux examples or tools are missing, and Linux users can complete the tasks described.
Recommendations
  • Clarify that the node startup process differs on Linux, and mention the equivalent Linux process/service names or startup mechanism.
  • When describing code packages, note that Linux services may use ELF binaries and other file types, not just EXE/DLL.
  • Where Windows-specific terminology (e.g., 'Windows service') is used, add a brief note about the Linux equivalent (e.g., systemd service or daemon).
  • Consider alternating the order of Windows and Linux mentions, or explicitly state parity where applicable.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized or exclusively featured. The CLI examples (using Azure CLI) are cross-platform and shown before PowerShell. However, PowerShell is included as a separate tab, which may imply a slight Windows bias, but the overall structure ensures Linux parity. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks using the CLI or REST API examples.
Recommendations
  • Ensure that CLI examples are clearly labeled as cross-platform and are shown before PowerShell.
  • Consider adding a note clarifying that Azure CLI works on Windows, Linux, and macOS.
  • If possible, add Bash shell scripting examples for advanced scenarios, to further demonstrate Linux parity.
  • Maintain the current tabbed structure, but avoid implying PowerShell is required for any step.
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, in the Windows section, PowerShell and Windows Command Prompt examples are given, and the Windows steps are presented after the Linux steps. There is minor bias in that Windows-specific tools (Sysprep, Set-AzVm) are shown, but Linux equivalents (waagent, az CLI) are also covered. The order of sections (Linux first, Windows second) avoids 'windows_first' bias, but the Windows section uses PowerShell and Windows command-line tools exclusively, which is expected for Windows VMs.
Recommendations
  • Ensure parity in detail and clarity between Linux and Windows sections.
  • Consider adding explicit notes about cross-platform CLI tools (e.g., az CLI works on Windows, Linux, macOS).
  • Where possible, mention that az CLI commands are available on all platforms.
  • If any step is platform-specific, clarify it to avoid confusion.
GitHub Create Pull Request
Virtual Machines Expand Virtual Hard Disks on a Linux VM ...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ powershell_heavy
Summary
The documentation is focused on expanding disks for Linux VMs and provides comprehensive Linux-specific guidance and examples. However, in the section about classic VM SKU support for 'expand without downtime', only a PowerShell script is provided to check SKU compatibility, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
  • Add an Azure CLI or Bash example for checking classic VM SKU support for 'expand without downtime', so Linux users can perform the same check without needing PowerShell.
  • Where PowerShell scripts are given, provide cross-platform alternatives or note if the check can only be performed from Windows.
  • Clarify if the PowerShell script is required due to Azure API limitations, and link to any relevant CLI documentation if available.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the document, Hyper-V (a Windows-centric hypervisor) is consistently presented first in each major section and example. The structure and ordering may subtly prioritize Windows users, but all Linux-centric workflows (KVM, VMware, Kickstart) are fully documented with detailed steps and parity.
Recommendations
  • Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
  • Add a short introductory note clarifying that all workflows are equally supported, and that the order does not imply preference.
  • Consider grouping instructions by task (e.g., 'Prepare VM', 'Convert disk', 'Upload to Azure'), then provide hypervisor-specific details, rather than leading with Hyper-V.
  • Ensure that references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) are balanced with Linux-native alternatives (e.g., qemu-img, guestfish) in the introductory notes.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before addressing Linux-specific mechanisms. This creates a minor 'windows_first' bias in the narrative, but all technical guidance and examples are Linux-centric.
Recommendations
  • Move or minimize the Windows Server 2016 discussion to a background or context section, clarifying its relevance to Azure hosts rather than VM configuration.
  • Begin the page with Linux-specific time sync mechanisms and configuration options, referencing Windows host infrastructure only as necessary for understanding Azure's time source.
  • Ensure that Linux guidance is always presented first and Windows references are clearly marked as context, not actionable steps for Linux users.
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation primarily references the Azure portal for role assignment and troubleshooting, which is a cross-platform web interface. However, when mentioning SDKs for interacting with the Runtime View API, 'PowerShell' is listed before 'CLI', subtly prioritizing Windows tooling. No Linux/macOS-specific examples or tools (such as Azure CLI or Bash scripts) are provided for role assignment or API interaction, and PowerShell is mentioned before CLI in the troubleshooting section.
Recommendations
  • Provide Azure CLI examples for role assignment and API interaction, as CLI is cross-platform and widely used on Linux/macOS.
  • When mentioning SDKs or tools, list Azure CLI before PowerShell or equally, to avoid subtle Windows-first bias.
  • Include Bash or shell script examples where appropriate, especially for API calls.
  • Explicitly note that all steps can be performed on Linux/macOS using Azure CLI or REST API tools.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ minor_windows_examples
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a mild bias toward Windows: PowerShell is mentioned as the primary API client, Windows-specific tools and examples (e.g., 'netsh', Windows container networking) are referenced, and Windows examples or terminology often appear before Linux equivalents. Some example links and ARM templates are Windows-focused, and Windows-specific operational notes (e.g., patching) are included. Linux is referenced, but often as a secondary consideration.
Recommendations
  • Provide Linux CLI (az CLI) and Bash examples alongside PowerShell, especially for cluster management and networking tasks.
  • When referencing API usage, mention Linux-compatible tools (e.g., Azure CLI, REST API, sfctl) equally with PowerShell.
  • Ensure ARM template examples and links include Linux cluster templates, not just Windows.
  • Where Windows-specific commands (e.g., 'netsh') are mentioned, provide the Linux equivalent or clarify if not applicable.
  • Balance the order of Windows and Linux mentions in guidance and examples.
  • Clarify which features or recommendations are platform-specific, and offer Linux alternatives where possible.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally avoids platform-specific bias. However, in the 'Upgrading OS images for cluster nodes' section, the only linked guidance is for patching Windows operating systems, with no mention of Linux node patching or upgrade guidance. Additionally, PowerShell is mentioned alongside Azure CLI for cluster management tasks, but Linux tools (such as Bash or Linux-specific CLI usage) are not referenced or shown. Overall, the bias is minor and mostly limited to the OS patching section.
Recommendations
  • Add guidance or links for patching/upgrading Linux node OS images in Service Fabric clusters, if supported.
  • When mentioning PowerShell/Azure CLI, clarify that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (Bash).
  • Ensure that references to Windows-specific tools or documentation are balanced with Linux equivalents where applicable.
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. However, there is a slight bias toward Windows: Windows container runtimes and tools are listed in more detail, Windows scenarios (like IIS lift-and-shift) are described first, and Windows tutorials are sometimes mentioned before Linux equivalents. Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted, while Linux only mentions Docker. Overall, Linux support is present and referenced, but Windows examples and tools are more prominent.
Recommendations
  • Ensure Linux and Windows tutorials/examples are always presented together or alternate their order.
  • Expand Linux-specific scenarios (e.g., using NGINX, Apache, or other Linux workloads) to match the detail given to Windows/IIS scenarios.
  • List Linux container runtimes and tools with similar detail as Windows (e.g., mention containerd, Podman if supported).
  • Provide parity in descriptions of isolation and resource governance for Linux containers.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell (a Windows-centric tool) is presented first and in more detail, with the CLI alternative shown after. There are no native Linux shell or Bash examples, but the CLI commands are cross-platform. The bias is minor, mainly in ordering and emphasis.
Recommendations
  • Present the Azure Service Fabric CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation links for non-Windows users.
  • Consider adding a short Bash shell example (e.g., using sfctl in a Bash script) to reinforce Linux parity.
  • Clarify that PowerShell examples are primarily for Windows users, and sfctl is recommended for Linux/macOS.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page exhibits mild Windows bias. It references Visual Studio as a primary tool for packaging and deploying guest executables and mentions the Service Fabric SDK schema location using a Windows file path. There are no explicit Linux/macOS examples or equivalent tooling mentioned, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric guidance. However, the content does not restrict the process to Windows and mentions running Node.js and Java, which are cross-platform.
Recommendations
  • Add explicit Linux/macOS instructions for packaging and deploying guest executables, including command-line examples using Bash or cross-platform tools.
  • Mention the location of Service Fabric SDK schema files on Linux/macOS, if available, or clarify if the SDK is Windows-only.
  • Provide sample directory structures using cross-platform executable formats (e.g., .sh, .jar, or generic binaries) alongside .exe.
  • Reference cross-platform IDEs or tools (e.g., VS Code, CLI utilities) in addition to Visual Studio.
  • Clarify any Windows-specific requirements or limitations, and highlight Linux/macOS compatibility where applicable.
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, but Windows development tools (Visual Studio, PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). There are no explicit examples or instructions favoring Windows, but the ordering subtly prioritizes Windows. No critical sections are Windows-only, and Linux support is clearly stated.
Recommendations
  • Present Windows and Linux development options in parallel or alternate their ordering.
  • Ensure quickstart and getting started links are available for both Windows and Linux (currently, the quickstart link points to a .NET/Windows page).
  • Add explicit links to Linux quickstart and getting started guides in the 'Next steps' section.
  • Where possible, provide sample commands/examples for both platforms.
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, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and sometimes before CLI. Portal instructions are platform-neutral, but PowerShell examples use Windows-specific extension types (e.g., ApplicationHealthWindows), while CLI uses ApplicationHealthLinux. The PowerShell section is more verbose and detailed, suggesting a Windows-centric audience. However, Linux parity is generally maintained via CLI and REST examples, and the feature itself is not Windows-specific.
Recommendations
  • Ensure that PowerShell and CLI examples are presented in parallel, with CLI (Linux/macOS-friendly) examples shown first where possible.
  • Clarify in PowerShell examples when Windows-specific extensions are used, and provide Linux equivalents if applicable.
  • Add explicit notes about cross-platform support for Azure CLI and REST API, highlighting their suitability for Linux/macOS users.
  • Consider including Bash shell script examples for Linux users, especially for automation.
  • Review the ordering of tabs and sections to avoid subtle prioritization of Windows tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell is featured equally alongside CLI and is presented as a primary automation method. PowerShell is a Windows-centric tool, and its inclusion as a main example (rather than Bash or Linux-native scripting) may create friction for Linux/macOS users. However, the Azure CLI examples are present and complete, and the tasks can be accomplished on Linux/macOS using the CLI. There are no Windows-only tools or patterns, and no critical sections are Windows-exclusive.
Recommendations
  • Consider adding Bash shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
  • If possible, provide links or notes about using PowerShell Core on Linux/macOS for parity.
  • Ensure that CLI examples are always shown before PowerShell, or explicitly note that CLI is recommended for non-Windows platforms.
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
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) show PowerShell commands first or exclusively. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present CLI and PowerShell examples side-by-side or in parallel tabs, rather than consistently listing PowerShell first.
  • Ensure all PowerShell examples have equivalent CLI examples, especially for querying and managing resources.
  • Highlight that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, add Bash scripting examples for advanced scenarios.
  • Review sections where PowerShell is shown exclusively and add CLI equivalents if missing.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is presented before REST API and ARM template examples. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, although it is now cross-platform. The CLI examples are generic and suitable for Linux/macOS, but the documentation does not explicitly highlight Linux-specific workflows or tools. The 'getting started' ARM template section does link to both Linux and Windows quick-starts, which is positive. Overall, the bias is minor and mostly in the ordering and prominence of PowerShell.
Recommendations
  • Ensure Azure CLI examples are always shown before PowerShell, as CLI is the primary cross-platform tool.
  • Add explicit Bash shell examples where relevant, especially for Linux/macOS users.
  • Clarify that PowerShell examples are also valid for Linux/macOS, or provide notes about cross-platform compatibility.
  • Where possible, provide links to Linux/macOS-specific quick-starts or troubleshooting guides.
  • Consider adding a section or note about using Bash or other shells for Linux users.
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 covers backup and disaster recovery for Azure Managed Disks and is intended for both Linux and Windows VMs. However, there are minor signs of Windows bias: Windows-specific tools (e.g., Volume Shadow Service for application-consistent snapshots) are mentioned first and in more detail, while Linux equivalents (e.g., fsfreeze) are referenced briefly and with less explanation. Windows examples and terminology (SQL Server, Always On Availability Groups) appear before Linux options in some sections. There are no missing Linux examples, and the solutions described are generally cross-platform.
Recommendations
  • Provide more detailed guidance and examples for Linux application-consistent backup, including common Linux database/application tools and patterns.
  • Expand on the use of fsfreeze and clarify its limitations compared to Windows VSS.
  • Mention Linux-first or cross-platform solutions in parallel with Windows tools, rather than after.
  • Include references to Linux-specific backup solutions or third-party tools where relevant.
  • Ensure parity in explanations for both OS types, especially in sections about coordinated backups.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but Windows/PowerShell examples are often presented alongside or immediately after Linux examples. In the extension installation section, the PowerShell example uses 'ApplicationHealthWindows' as the extension type, while the CLI example uses 'ApplicationHealthLinux', but neither is clearly explained or prioritized. PowerShell is given equal prominence to Bash, and Windows-specific extension types and tools (PowerShell cmdlets) are referenced. However, Linux parity is generally maintained, and CLI/Bash examples are present throughout.
Recommendations
  • Clarify when to use 'ApplicationHealthLinux' vs 'ApplicationHealthWindows' extension types, and explicitly mention OS-specific requirements.
  • Ensure Linux/Bash examples are presented first, or at least equally, in all sections.
  • Add explicit notes about cross-platform support for Azure CLI and REST API, emphasizing their availability on Linux/macOS.
  • Where PowerShell examples are given, ensure equivalent Bash or CLI examples are always present and clearly labeled.
  • Consider adding a table summarizing which commands/tools are available for each OS.
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, but there are minor instances of Windows bias. For example, in the VM selector section, the recommendation 'Use at least B2 for Windows machines' is given, but no equivalent guidance is provided for Linux machines. In the disk sizing section, Windows is mentioned specifically, while Linux is not. However, Linux pricing links and VM creation guides are referenced alongside Windows, and most recommendations are generic.
Recommendations
  • Where specific guidance is given for Windows (e.g., 'Use at least B2 for Windows machines'), provide equivalent recommendations for Linux, or clarify if no such minimum applies.
  • Ensure disk sizing and performance recommendations are equally explicit for Linux workloads.
  • Review all examples and recommendations to ensure Linux is mentioned wherever Windows is, unless the guidance is genuinely Windows-specific.
  • Consider adding a brief note clarifying when recommendations are OS-specific and when they are general.
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, but otherwise provides parity in describing supported OSes and limitations for both platforms. No Windows-specific tools, examples, or patterns are prioritized, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell, but does not show a preference for Windows tools.
Recommendations
  • Consider listing Linux operating system support before or alongside Windows to avoid implicit prioritization.
  • Ensure that future examples or walkthroughs (linked in 'Next steps') provide both Linux and Windows instructions equally.
  • Clarify in the 'Next steps' section that CLI and Portal are cross-platform, and PowerShell is available on Linux/macOS as well.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure Managed Disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both platforms. However, in several places, Windows/PowerShell examples and links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent (e.g., in key rotation and revoking access), and Windows tools are mentioned first in 'Next steps' and throughout the article. Linux parity is generally maintained, but Windows examples are prioritized in ordering.
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 possible, provide explicit Linux/macOS command examples alongside PowerShell, especially in sections referencing Azure Key Vault operations.
  • Ensure that references to Azure CLI are as prominent as PowerShell, including in 'Next steps' and procedural links.
  • Consider grouping cross-platform instructions together, clarifying which applies to each OS, rather than splitting by Windows/Linux.
  • Review for any subtle language or tool preference and adjust to neutral, platform-agnostic phrasing.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling on-demand disk bursting, but the PowerShell section is presented before the CLI section. PowerShell is primarily associated with Windows environments, which may create friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), but the CLI commands are cross-platform. No Windows-only tools or patterns are mentioned, and the feature itself is not Windows-specific.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples for disk creation and bursting, or clarify that CLI commands can be run in Bash.
  • Mention that Azure Cloud Shell supports both PowerShell and Bash environments.
GitHub Create Pull Request
Virtual Machines Secure Azure Managed Disk Downloads and Uploads ...icles/virtual-machines/disks-secure-upload-download.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for key operations, but PowerShell examples are consistently presented before CLI (which is more cross-platform). Portal instructions are also included, but there is a slight preference for Windows-centric tools and ordering. However, Linux-specific guidance is present in the 'Next steps' section, and CLI examples are included throughout.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS, and provide links to installation instructions for those platforms.
  • Ensure parity in screenshots and instructions for the Azure Portal, noting any OS-specific differences if relevant.
  • Consider adding bash or shell script examples where appropriate, especially for disk upload/download tasks.
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 friction for Linux/macOS users. However, Azure CLI examples are always provided, and the documentation explicitly states applicability to both Linux and Windows VMs. There are no Windows-only tools or patterns, and Linux parity is generally maintained.
Recommendations
  • Consider explicitly stating that Azure CLI commands work cross-platform (Linux, macOS, Windows) and are recommended for non-Windows environments.
  • Where PowerShell is used, clarify that it is primarily for Windows users, and highlight Azure CLI as the preferred option for Linux/macOS.
  • If possible, provide brief guidance or links for installing and using Azure CLI on Linux/macOS.
  • Ensure that any advanced operations (such as mounting disks to VMs) include CLI examples, not just PowerShell.
GitHub Create Pull Request
Virtual Machines Share an Azure Managed Disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux coverage, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific workloads) are consistently presented first and in greater detail. Windows clustering patterns (WSFC, CSV) are described before Linux equivalents (Pacemaker, Corosync), and Windows workloads are listed first with more links and explanations. Linux examples are present but less detailed, and Linux-specific tools (sg_persist, fence_scsi) are mentioned later and with less context. There are no CLI or PowerShell command examples, but Windows tools and templates are referenced more prominently.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
  • Expand Linux workload examples with more detailed descriptions and links, matching the depth of Windows coverage.
  • Add explicit Linux command-line examples (e.g., sg_persist usage) and configuration steps for Pacemaker/Corosync.
  • Reference Linux templates or sample architectures, similar to Windows SoFS and SAP templates.
  • Clarify parity between Windows and Linux features, especially around clustering and disk reservation flows.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is generally cross-platform and neutral, but there are minor signs of Windows bias. Some links and examples reference Windows documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows-specific page, and disk conversion/expansion links show Windows before Linux). Additionally, the 'LastOwnershipUpdateTime' feature mentions Azure PowerShell and portal before Azure CLI, which may be perceived as Windows-centric. However, Linux equivalents are usually present or referenced, and no critical features are Windows-only.
Recommendations
  • Ensure all feature links reference both Windows and Linux documentation equally, ideally linking to a cross-platform overview or listing both OS-specific guides.
  • When mentioning tools (Azure CLI, PowerShell), list them in neutral or alphabetical order, and clarify cross-platform support.
  • Where possible, provide explicit Linux/macOS examples alongside Windows/PowerShell examples, especially for disk management tasks.
  • Review and update any section where only Windows documentation is linked, adding Linux/macOS equivalents.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers both Linux and Windows VMs for ephemeral OS disks, and provides parity in most technical explanations. However, there are minor signs of Windows bias: Windows examples and details (such as page file placement and OS disk sizing) are sometimes mentioned first or in greater detail, and PowerShell is listed before CLI in the section on customer-managed keys. Linux-specific examples and tools are present but not always equally emphasized.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, alternating order or grouping by OS where relevant.
  • When referencing tooling (e.g., PowerShell and CLI), list both together or alternate which comes first.
  • Expand Linux-specific details where Windows-specific technical nuances are discussed (e.g., page file placement, disk sizing).
  • Add explicit Linux command examples or links where only Windows/PowerShell examples are given.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux, but in several sections, Windows-centric tools (Azure PowerShell) are presented before their Linux-friendly equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting are shown first, despite Azure CLI being more native to Linux environments. However, Linux-specific details, paths, and behaviors are well covered, and Azure CLI examples are present throughout.
Recommendations
  • Present Azure CLI examples before Azure PowerShell in deployment and troubleshooting sections, as CLI is more native to Linux users.
  • Add explicit notes clarifying that Azure CLI is recommended for Linux environments, and PowerShell is optional.
  • Ensure troubleshooting commands for Azure CLI are as prominent as PowerShell.
  • Consider adding Bash script examples for common certificate management tasks, if relevant.
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 primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples for deploying the extension, even though PowerShell is a Windows-centric tool. Additionally, in the troubleshooting section, PowerShell commands are shown before Azure CLI commands. There is a brief mention of a Windows extension, but it is clearly separated and not the focus. No Linux examples are missing, and Linux tools and patterns are well represented throughout.
Recommendations
  • Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
  • Clearly indicate that PowerShell is optional and primarily for Windows users, or provide Bash scripting equivalents where appropriate.
  • Consider removing PowerShell examples from Linux-focused documentation, or place them in a separate section for users managing from Windows.
  • In troubleshooting, show Azure CLI commands first, followed by PowerShell, to prioritize Linux user workflows.
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 Windows bias in example ordering and PowerShell usage. In the PowerShell section, Windows is shown first in the example, and Linux is mentioned as an alternative. CLI examples are Linux-first, but PowerShell examples are Windows-first. Both platforms are covered, but Windows examples tend to be prioritized or shown first in some sections.
Recommendations
  • In PowerShell examples, show Linux usage first or provide parallel examples for both OS types.
  • Ensure that example ordering alternates or is neutral (e.g., 'Linux and Windows') rather than 'Windows and Linux'.
  • Explicitly state that all commands and workflows apply equally to Linux and Windows, and highlight any OS-specific differences.
  • Where possible, provide Linux-specific PowerShell examples (e.g., using -OsType Linux) alongside Windows examples.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but the Windows section appears first and is more detailed in its parameter explanations. Both tools are covered with example commands and screenshots, and Linux parity is generally good, but the ordering and depth of parameter explanation may create a minor perception of Windows bias.
Recommendations
  • Consider presenting Linux (FIO) and Windows (DISKSPD) sections in parallel, or alternating their order in different documentation versions.
  • Provide equally detailed parameter explanations for FIO as are given for DISKSPD.
  • Add a summary table comparing DISKSPD and FIO usage for benchmarking across platforms.
  • Explicitly state that both tools are recommended and supported for their respective OSes.
GitHub Create Pull Request
Virtual Machines Enable Azure Disk Encryption for Linux VMs ...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is focused on Linux VMs and provides Linux-specific instructions and examples. However, there is mild evidence of Windows bias in the order and prominence of Azure PowerShell references: PowerShell is mentioned alongside Azure CLI in quickstart links and 'Next steps', and PowerShell cmdlets are listed in the terminology table, even though PowerShell is not a native Linux tool. Azure CLI is the primary Linux-native tool, but PowerShell is given equal visibility, which may create confusion or friction for Linux users.
Recommendations
  • List Azure CLI examples and quickstarts before PowerShell in all sections, as CLI is more native to Linux.
  • Clarify that PowerShell is optional and not required for Linux users, and that Azure CLI is the recommended tool for Linux environments.
  • In the terminology table, note that PowerShell cmdlets are available for cross-platform use, but Azure CLI is the default for Linux.
  • Consider adding a brief section explaining the difference between Azure CLI and PowerShell for Linux users, including installation and usage guidance.
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 examples and terminology are often presented first or with greater detail. PowerShell cmdlets are referenced in critical backup and encryption steps, sometimes before CLI equivalents. The documentation occasionally uses Windows-centric language (e.g., 'PowerShell session') and emphasizes PowerShell-specific requirements (like sequence version generation) more than CLI. However, Linux parity is generally maintained, and CLI examples are present throughout.
Recommendations
  • Ensure Azure CLI and PowerShell examples are presented in parallel, with equal prominence and detail.
  • Avoid Windows-centric terminology (e.g., 'PowerShell session') when referring to cross-platform tools; clarify that Azure CLI can be used in Bash, Zsh, etc.
  • Where PowerShell-specific requirements are discussed (such as sequence version generation), provide equivalent CLI explanations or clarify differences.
  • Consider starting sections with Azure CLI examples, as CLI is more native to Linux users.
  • Explicitly mention that both Azure CLI and PowerShell are fully supported on Linux/macOS, and link to installation instructions for Bash/Zsh environments.
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 balanced overview of Azure Managed Disks for both Linux and Windows VMs, with explicit applicability to both platforms. However, there are minor signs of Windows bias: Windows terminology and links are sometimes presented first or exclusively (e.g., references to Sysprep, MBR/GPT partitioning, and Windows drive letters), and some links point to Windows-specific documentation before Linux equivalents. The section on uploading VHDs does provide both Azure CLI (Linux) and PowerShell (Windows) links, but Windows terminology (drive letters, Sysprep) is more prominent in some explanations.
Recommendations
  • Ensure Linux-specific terminology and examples are presented alongside Windows ones, not after or instead of them.
  • When referencing partitioning (MBR/GPT), include links to Linux partitioning documentation (e.g., fdisk, parted) and explain Linux default behaviors.
  • When discussing OS disk and drive letters, clarify Linux mount points and device names (e.g., /dev/sda, /dev/disk/azure/resource) in parallel to Windows drive letters.
  • For image creation, mention Linux generalization methods (e.g., waagent -deprovision) alongside Sysprep.
  • Where possible, provide links to Linux documentation before or alongside Windows links, especially in sections where Windows links are currently dominant.
GitHub Create Pull Request
Virtual Machines Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines ...ion/migrate-from-elastic-compute-cloud-architecture.md
Low 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 migration guide from Amazon EC2 to Azure Virtual Machines, covering architecture, storage, networking, and image translation. While the guide is generally platform-neutral, there are subtle signs of Windows bias: Windows-specific tools (Sysprep) are mentioned before Linux equivalents, and some image preparation steps highlight Windows patterns first. There are no explicit PowerShell examples, but Windows-centric terminology and processes are referenced before Linux alternatives. Linux-specific migration steps (such as waagent installation) are mentioned, but often after Windows steps or with less detail.
Recommendations
  • Ensure Linux and Windows migration steps are presented with equal prominence and detail.
  • When describing image generalization, mention Linux steps (waagent installation) before or alongside Windows steps (Sysprep), rather than after.
  • Provide explicit Linux migration examples or references (e.g., shell commands, Linux agent installation, troubleshooting).
  • Include links to Linux-specific Azure documentation and migration tools.
  • Avoid defaulting to Windows terminology (e.g., 'RDP' before 'SSH') in networking and access sections.
GitHub Create Pull Request