← Back to Dashboard
61
Pages Scanned
6
Pages Flagged
61
Changed Pages
9.8%
% Pages Flagged

Scan Information

Started At: 2026-01-21 00:00:08

Finished At: 2026-01-21 00:02:36

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 61

Files Completed: 61

Problematic Pages

6 issues found
Dev Box Use Customizations to Connect to Azure Resources or Clone Private Repositories ...x/how-to-customizations-connect-resource-repository.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 demonstrates a moderate Windows bias. All YAML examples use Windows-style paths (e.g., C:\workspaces), and the example tasks reference Windows images (Win11, Visual Studio). The main scripting example uses PowerShell and the winget package manager, both Windows-specific tools, without providing Linux/macOS alternatives. There are no Linux/macOS-specific examples, nor any mention of equivalent commands or patterns for non-Windows environments.
Recommendations
  • Provide parallel examples using Linux/macOS base images and POSIX-style paths (e.g., /workspaces).
  • Include alternative scripting examples using Bash or sh, and show how to install Azure CLI on Linux/macOS.
  • Mention cross-platform considerations for Dev Box customizations, clarifying which features/tasks are Windows-only and which are supported on other OSes.
  • If Dev Box supports Linux/macOS images, add explicit examples and guidance for those platforms.
GitHub Create Pull Request
Azure Netapp Files Create an SMB volume for Azure NetApp Files ...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is focused on creating SMB volumes for Azure NetApp Files, which inherently relies on Windows-centric technologies such as Active Directory and SMB. However, the sections on controlling access and modifying permissions exclusively reference Windows tools (MMC, Windows SMB client) and do not provide Linux/macOS equivalents or guidance for managing SMB shares from non-Windows systems. Examples and screenshots are Windows-first, and Linux alternatives are not mentioned, despite SMB clients being available on Linux/macOS.
Recommendations
  • Add instructions or references for managing SMB share and NTFS permissions from Linux/macOS clients (e.g., using smbclient, setfacl, or other tools).
  • Clarify which steps are Windows-only and which can be performed from other platforms.
  • Include examples or links for mounting and accessing SMB volumes from Linux/macOS clients.
  • Provide parity in screenshots and step-by-step guides for non-Windows environments where possible.
GitHub Create Pull Request
Data Factory Copy data from Amazon RDS for SQL Server ...es/data-factory/connector-amazon-rds-for-sql-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page provides several examples and troubleshooting steps that are Windows-centric, such as instructions for using SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall. These tools and configuration patterns are specific to Windows environments and are mentioned exclusively, with no Linux or cross-platform alternatives provided. Windows authentication is described and exampled before SQL authentication, and all troubleshooting steps assume a Windows-based SQL Server instance.
Recommendations
  • Add troubleshooting steps for Amazon RDS for SQL Server instances managed from Linux/macOS, such as using sqlcmd or other cross-platform tools.
  • Include instructions for configuring remote access and TCP/IP on Amazon RDS for SQL Server via AWS Console or CLI, which is platform-agnostic.
  • Provide guidance for managing firewall rules on Linux (e.g., using iptables or firewalld) if self-hosted integration runtime is on Linux.
  • Clarify that SQL authentication is platform-neutral and may be preferable for cross-platform scenarios.
  • Where possible, reference cross-platform management tools (e.g., Azure Data Studio, sqlcmd) alongside Windows-only tools.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for ExpressRoute virtual network gateways demonstrates a moderate Windows bias. The only code example for gateway subnet creation uses Azure PowerShell, with no equivalent Azure CLI (cross-platform) or ARM template example. References to REST APIs and PowerShell cmdlets are provided, but Linux/macOS-friendly tools (Azure CLI, Bash, etc.) are not mentioned or linked. This may create friction for users on Linux or macOS who prefer or require CLI or template-based workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration steps, especially gateway subnet creation.
  • Include links to Azure CLI documentation and examples in the 'REST APIs and PowerShell cmdlets' section.
  • Consider providing ARM/Bicep template snippets for resource creation to support declarative, platform-neutral workflows.
  • Explicitly state that all operations can be performed via Azure CLI on Linux/macOS, and provide guidance or references where appropriate.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. Browser recommendations list Windows browsers first and provide more detail for Windows users. Keyboard layout configuration instructions are given only for Windows workstations, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like setting keyboard layouts or file transfer, despite Bastion supporting SSH and RDP to non-Windows VMs.
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS workstations, alongside the Windows steps.
  • When listing supported browsers, mention Linux compatibility explicitly and provide browser recommendations for Linux users.
  • For file transfer and native client usage, clarify any OS-specific requirements or provide examples for Linux/macOS (e.g., using SSH/SCP, RDP clients).
  • Ensure that any references to local workstation configuration include parity for Linux and macOS environments.
GitHub Create Pull Request
Web Application Firewall CRS and DRS rule groups and rules ...irewall/ag/application-gateway-crs-rulegroups-rules.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ powershell_heavy
Summary
The documentation is generally cross-platform and does not focus on Windows-specific features. However, in the 'Upgrading or changing ruleset version' section, PowerShell is mentioned first among the recommended tools for making ruleset changes, ahead of CLI, REST API, and templates. There are no Windows-only examples, tools, or patterns, and the rule sets themselves are platform-neutral.
Recommendations
  • List CLI, REST API, and template options before PowerShell, or present all options together without prioritizing PowerShell.
  • Ensure that examples and guidance are provided for both Linux/macOS and Windows users when referencing command-line tools.
  • Explicitly mention that all management actions can be performed from any OS using CLI, REST API, or templates.
GitHub Create Pull Request