31
Pages Scanned
3
Pages Flagged
31
Changed Pages
9.7%
% Pages Flagged

Scan Information

Started At: 2025-07-20 00:13:07

Finished At: 2025-07-20 17:44:04

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

Bias Types:
⚠️ powershell_heavy
⚠️ windows_tools
⚠️ missing_linux_example
⚠️ windows_first
Summary:
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell sections are prominent and detailed, while Linux-native or cross-platform command-line options are not mentioned. This may hinder accessibility for Linux and macOS users who prefer or require Azure CLI or Bash scripting.
Recommendations:
  • Add Azure CLI examples alongside all PowerShell examples for creating and managing managed identities, including resource creation, updates, and assignments.
  • Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
  • Where PowerShell is referenced, add a parallel section for Azure CLI (or Bash) and ensure both are kept up-to-date.
  • In introductory sections and step-by-step guides, avoid assuming PowerShell as the default tool; instead, present both PowerShell and CLI options or let users choose.
  • Review all references to Windows-specific tools or patterns and provide Linux/macOS equivalents where applicable.
GitHub Create pull request
Bias Types:
⚠️ windows_first
⚠️ powershell_heavy
⚠️ missing_linux_example
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving outbound IP addresses, but PowerShell examples are always included alongside CLI, and there are no Linux- or bash-specific examples for tasks that could be performed with native Linux tools (e.g., using curl or dig for DNS/IP queries). The documentation refers to 'local terminal' for nslookup but does not clarify cross-platform alternatives or mention Linux-specific tools. Outbound IPv6 support is noted as being available only for Windows apps, but this is a platform limitation, not a documentation bias.
Recommendations:
  • For all command-line examples, ensure that bash/Linux-native equivalents are provided where possible (e.g., using dig or host for DNS lookups, or curl for HTTP requests).
  • When listing multiple command-line options, present Azure CLI (cross-platform) examples before PowerShell, or clearly indicate that both are supported on all platforms.
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and clarify any platform-specific differences.
  • Where PowerShell is shown, consider also showing bash or shell script equivalents for common administrative tasks.
  • In sections referencing 'local terminal', clarify that commands work on both Windows and Linux/macOS, and suggest alternative tools if needed.
GitHub Create pull request
Bias Types:
⚠️ missing_linux_example
⚠️ windows_first
Summary:
The documentation assumes a development environment based on .NET and Azure App Service, which are cross-platform, but it implicitly favors Windows-centric workflows. It references GitHub Codespaces (which is Linux-based) but does not provide any explicit Linux or macOS terminal commands, troubleshooting, or deployment guidance. There are no examples or notes for Linux users regarding environment setup, file paths, or alternative tools. The use of Azure Developer CLI (azd) and dotnet CLI is cross-platform, but the lack of explicit Linux guidance or parity checks may leave Linux users with unanswered questions.
Recommendations:
  • Explicitly state that all CLI commands (dotnet, azd) work on Linux, macOS, and Windows, and provide any necessary prerequisites for Linux (e.g., installing .NET SDK, azd).
  • Add a section or notes for Linux/macOS users, including common troubleshooting tips (e.g., file permissions, case sensitivity, environment variables).
  • If referencing 'Open in Browser' or similar UI actions, clarify how to do this from a Linux terminal or Codespaces environment.
  • Where file paths are mentioned, use forward slashes or note that paths are the same on all platforms.
  • If there are any platform-specific differences (e.g., environment variable syntax, deployment steps), call them out explicitly.
GitHub Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧