← Back to Dashboard
39
Pages Scanned
7
Pages Flagged
39
Changed Pages
17.9%
% Pages Flagged

Scan Information

Started At: 2026-01-15 00:00:09

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 39

Files Completed: 39

Problematic Pages

7 issues found
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on Windows-specific tools and workflows, particularly SignTool and PowerShell. All setup instructions, installation commands, and examples are for Windows environments, with no mention of Linux or macOS alternatives or parity. Even in sections referencing cross-platform integrations (e.g., GitHub Actions, SDK), no Linux/macOS-specific guidance or examples are provided.
Recommendations
  • Clearly state at the beginning if Artifact Signing integration via SignTool is Windows-only, and provide alternative guidance for Linux/macOS users if available.
  • If cross-platform SDKs or CLI tools exist, add explicit Linux/macOS installation and usage instructions.
  • For GitHub Actions and Azure DevOps, include Linux/macOS runner examples and clarify any platform-specific limitations.
  • If PowerShell is required, note whether PowerShell Core (pwsh) on Linux/macOS is supported, and provide corresponding examples.
  • For each integration, provide parity in examples and setup steps for Linux/macOS where possible, or clearly state if not supported.
GitHub Create Pull Request
Reliability Reliability in Azure Storage Mover ...rticles/reliability/reliability-azure-storage-mover.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 example for updating job definitions but does not offer equivalent examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). The only explicit command-line example is PowerShell, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all management operations, especially for updating job definitions and agent assignments.
  • Explicitly mention that the same operations can be performed via the Azure portal, Azure CLI, or REST API, and provide links or references to relevant documentation.
  • Where possible, provide Bash or cross-platform scripting examples to ensure parity for Linux/macOS users.
GitHub Create Pull Request
App Service Inbound/Outbound IP Addresses .../articles/app-service/overview-inbound-outbound-ips.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 finding outbound IP addresses, but PowerShell examples are always shown immediately after CLI, and there are no explicit Linux/macOS shell examples (e.g., bash scripts) for interacting with Azure outside of Azure CLI. The use of PowerShell is not strictly necessary for cross-platform users, and its inclusion immediately after CLI may suggest a Windows-first approach.
Recommendations
  • Ensure that Azure CLI examples are clearly marked as cross-platform and are shown before PowerShell examples, as is currently the case.
  • Consider explicitly stating that Azure CLI commands work on Windows, Linux, and macOS, and that PowerShell is optional.
  • If possible, add bash or shell script examples for common tasks, or clarify that Azure CLI is the recommended cross-platform tool.
  • Where PowerShell is shown, clarify that it is available cross-platform (via PowerShell Core), or provide a note for Linux/macOS users.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, especially in the 'Premium v4 availability' section, where both Windows and Linux SKU availability commands are provided. However, there is a subtle 'windows_first' bias: Windows examples and instructions are consistently presented before Linux equivalents. Additionally, the 'Automate with scripts' section provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but does not mention Bash scripting or Linux-native automation tools. The Azure portal instructions are platform-neutral. No critical Linux gaps are present.
Recommendations
  • When listing both Windows and Linux commands, alternate the order or explicitly state that both are equally supported.
  • In the 'Automate with scripts' section, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users, and consider adding a Bash script example for Linux automation.
  • Where PowerShell is shown, note that PowerShell Core is available cross-platform, or provide Bash equivalents if relevant.
  • Continue to ensure that all features and instructions are clearly marked if they are Windows- or Linux-specific.
GitHub Create Pull Request
Azure App Configuration How to use Agent Framework in a Python app with Azure App Configuration ...zure-app-configuration/howto-ai-agent-config-python.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. The only other minor Windows bias is a link to Python setup instructions specifically for Windows in the prerequisites.
Recommendations
  • Present environment variable instructions for all platforms together, or list macOS/Linux first to avoid implicit prioritization of Windows.
  • In the prerequisites, provide links for setting up Python on all major platforms (Windows, macOS, Linux), or link to the official Python download page which covers all OSes.
  • Consider using a tabbed or side-by-side format for platform-specific commands to improve parity and clarity.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally presents a cross-platform approach, but there are several areas where Windows tools and patterns are mentioned before or more prominently than Linux equivalents. Windows-specific configuration steps and CLI commands are often shown first, and Azure PowerShell is listed as a primary resource creation method, while Bash or Linux shell examples are not always equally highlighted. Some sections (e.g., ReadyToRun, deployment, and preview SDK configuration) provide Windows instructions first or in more detail, and PowerShell is referenced as a main automation tool.
Recommendations
  • Ensure that Linux and macOS equivalents are always presented alongside Windows examples, with equal detail and prominence.
  • When listing resource creation or deployment methods, alternate the order or explicitly state that all platforms are supported, and provide Bash/Azure CLI examples before or alongside PowerShell.
  • Where CLI commands are shown, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) syntax, or clarify that the Azure CLI commands are cross-platform.
  • In sections like ReadyToRun and deployment, ensure Linux examples are as detailed as Windows examples, and avoid defaulting to Windows-first explanations.
  • Review all code snippets and automation instructions to ensure parity for Linux/macOS users, including troubleshooting and debugging steps.
GitHub Create Pull Request
Migrate Support for VMware vSphere migration in Azure Migrate ...les/migrate/migrate-support-matrix-vmware-migration.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 Windows and Linux coverage for VMware vSphere migration to Azure, including supported OS versions, requirements, and post-migration steps. However, there is a mild Windows bias: PowerShell is mentioned as the only CLI automation method for configuring replication, and in some tables and sections, Windows instructions or details are listed before Linux equivalents. All critical Linux information is present, but Linux automation and tooling parity could be improved.
Recommendations
  • When referencing automation or scripting (e.g., configuring replication), mention cross-platform tools such as Azure CLI or REST API if available, not just PowerShell.
  • Where PowerShell is referenced for appliance deployment or configuration, clarify if PowerShell Core (pwsh) on Linux/macOS is supported, or provide equivalent Bash/CLI instructions.
  • In tables and instructional sections, alternate the order of Windows and Linux details, or present them in parallel, to avoid the perception of Windows-first bias.
  • Explicitly mention Linux/macOS support for any scripts or tools where applicable, and provide links to Linux-specific guidance if it exists.
GitHub Create Pull Request