← Back to Dashboard
26
Pages Scanned
7
Pages Flagged
26
Changed Pages
26.9%
% Pages Flagged

Scan Information

Started At: 2026-01-13 22:27:42

Finished At: 2026-01-13 23:13:48

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 26

Files Completed: 26

Problematic Pages

7 issues found
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not offer explicit Linux/macOS shell examples (e.g., Bash), nor does it mention Linux-specific considerations. PowerShell examples are given equal prominence to CLI, and the CLI examples use Bash syntax but do not clarify Linux compatibility. There are no references to Linux tools or patterns, and the order of examples sometimes places PowerShell before CLI. No Linux-specific troubleshooting or parity notes are present.
Recommendations
  • Explicitly state that Azure CLI examples are compatible with Linux/macOS and provide sample Bash commands where appropriate.
  • Add a dedicated Bash example tab for Linux users, clarifying environment setup and shell differences.
  • Include notes on any Linux/macOS-specific considerations, such as authentication, file permissions, or environment variables.
  • Ensure CLI examples appear before PowerShell to emphasize cross-platform support.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell is referenced.
GitHub Create Pull Request
Virtual Machines Ebdsv6 size series ...rtual-machines/sizes/memory-optimized/ebdsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where the link for Nested Virtualization points only to the Windows/Hyper-V guide, and in the 'Bandwidth/Throughput testing' resource, which references NTTTCP—a Microsoft tool primarily associated with Windows. Additionally, Windows and Linux disk encryption support are mentioned together, but the Windows link appears after the Linux one.
Recommendations
  • Provide equivalent Linux documentation or links for Nested Virtualization (e.g., KVM/QEMU guides for Linux VMs).
  • Mention and link to Linux-native network throughput testing tools (such as iperf3) alongside NTTTCP.
  • Ensure that any feature support or tooling references include both Linux and Windows options, or clarify platform applicability.
  • Where possible, present Linux and Windows resources in parallel, rather than referencing Windows tools first or exclusively.
GitHub Create Pull Request
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.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 retrieving the health state of the standby pool, but PowerShell is given a dedicated section, which is primarily a Windows tool. The CLI example is cross-platform, but the presence of a PowerShell example may signal a Windows-centric approach. No Linux/macOS-specific shell examples (e.g., Bash/cURL) are provided, and the order of examples (CLI, then PowerShell, then REST) is typical but could be improved for parity.
Recommendations
  • Add explicit Bash/cURL examples for Linux/macOS users to query the REST API.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide platform-specific installation links.
  • If PowerShell is included, consider also showing how to use PowerShell Core on Linux/macOS.
  • Ensure troubleshooting and next steps reference tools available on all platforms.
GitHub Create Pull Request
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.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 retrieving prediction results, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. There is no mention of Linux/macOS-specific tools or shell patterns (e.g., Bash), nor are there any examples tailored for those platforms. The CLI example is cross-platform, but PowerShell is highlighted separately, which may suggest a Windows-first approach.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users, demonstrating how to use the Azure CLI in those environments.
  • Clarify that the Azure CLI example works on Windows, Linux, and macOS.
  • Consider adding notes or links for installing and using Azure CLI on Linux/macOS.
  • If PowerShell is shown, consider also showing Bash or zsh equivalents for parity.
  • Avoid giving Windows/PowerShell examples more prominence than cross-platform tools.
GitHub Create Pull Request
Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.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 mentions deployment via Azure portal, Azure CLI, PowerShell, and ARM templates, but lists PowerShell explicitly and does not mention Bash, Linux shell, or macOS-specific instructions. The order of tools puts PowerShell before ARM templates and does not clarify parity for Linux/macOS users. No Linux/macOS-specific examples or guidance are provided.
Recommendations
  • Explicitly mention Bash and Linux/macOS shell usage alongside PowerShell.
  • Provide example commands for Azure CLI in both Windows (PowerShell) and Linux/macOS (Bash).
  • Clarify that ARM templates and Azure CLI are cross-platform and provide links or examples for Linux/macOS users.
  • Avoid listing Windows-centric tools (PowerShell) before cross-platform tools unless justified.
  • Add a note or section on Linux/macOS compatibility and any platform-specific considerations.
GitHub Create Pull Request
Container Instances Quickstart - create a container instance - Bicep ...iner-instances/container-instances-quickstart-bicep.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 commands, but PowerShell (a Windows-centric tool) is always presented as the only alternative to the CLI, and is shown immediately after the CLI in every section. No mention is made of Bash, Linux-native scripting, or macOS-specific considerations. The CLI examples are cross-platform, but the exclusive alternative is PowerShell, which may suggest a Windows-first perspective.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell is optional.
  • Consider adding Bash script equivalents or mentioning that the CLI commands can be run in Bash, zsh, or other Unix shells.
  • If PowerShell is shown as an alternative, also mention Bash or shell scripting for parity.
  • Add a note clarifying that all tasks can be completed on Linux/macOS using the Azure CLI, and that PowerShell is not required.
GitHub Create Pull Request
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation demonstrates mild Windows bias by presenting PowerShell commands first for critical provider registration steps and by including both PowerShell and Azure CLI examples for pool creation, but listing PowerShell before CLI. There is no explicit Linux example for provider registration, and the use of 'Azure Cloud Shell' may imply PowerShell usage, which is more familiar to Windows users. However, CLI and REST examples are present for pool creation, and JSON configuration is platform-neutral.
Recommendations
  • Add explicit Azure CLI examples for provider registration alongside PowerShell, with CLI shown first or equally.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/CLI commands where appropriate.
  • Ensure that all critical steps (such as provider registration and pool creation) have both CLI and PowerShell examples, with equal prominence.
  • Consider adding notes or examples for macOS/Linux users where command syntax or tooling differs.
GitHub Create Pull Request