1139
Pages Scanned
4
Pages Flagged
1139
Changed Pages
0.4%
% Pages Flagged

Scan Information

Started At: 2025-07-26 00:01:00

Finished At: 2025-07-26 00:05:11

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 instructions, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The 'devx-track-azurepowershell' tag and repeated references to PowerShell samples reinforce this bias. No Linux- or macOS-specific instructions or examples are present, and the PowerShell approach is presented before or instead of any cross-platform alternatives.
Recommendations:
  • Add Azure CLI examples alongside all Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell scripts or command snippets where appropriate, especially for ARM template deployments.
  • Reference Azure CLI installation and usage guides in addition to PowerShell guides.
  • Where possible, use neutral language (e.g., 'command-line' or 'terminal') instead of 'PowerShell' when introducing sections, unless the content is truly PowerShell-specific.
  • Consider adding a table or section comparing PowerShell and Azure CLI commands for common tasks.
  • Ensure screenshots and UI walkthroughs do not assume a Windows environment unless unavoidable.
GitHub Create pull request
Bias Types:
⚠️ powershell_heavy
⚠️ windows_first
⚠️ missing_linux_example
Summary:
The documentation page demonstrates a Windows bias in the automation section by providing a PowerShell script directly in the main content, while the Azure CLI (cross-platform) automation is only linked and not shown inline. There is no mention of Linux-specific tools or workflows, and no Linux shell (bash) examples are provided. The documentation also references PowerShell before the CLI, reinforcing a Windows-first approach.
Recommendations:
  • Provide inline Azure CLI and bash examples alongside PowerShell scripts in the automation section.
  • Ensure that Linux and cross-platform workflows are mentioned and demonstrated equally, not just linked.
  • Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI, and provide sample commands.
  • Where relevant, include screenshots or instructions from both Windows and Linux environments.
  • Avoid listing PowerShell or Windows-specific tools before their cross-platform or Linux equivalents.
GitHub Create pull request
Bias Types:
⚠️ windows_first
⚠️ missing_linux_example
Summary:
The documentation page is generally cross-platform and avoids OS-specific instructions, but there is a subtle Windows bias in the troubleshooting section. Specifically, when advising users to clear the DNS cache, only the Windows command (`ipconfig /flushdns`) is provided, with no equivalent instructions for Linux or macOS users. No PowerShell-specific or Windows-only tools are otherwise mentioned, and the rest of the content is platform-neutral.
Recommendations:
  • When providing troubleshooting steps such as clearing the DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
  • Explicitly state that the instructions apply to all platforms, or provide platform-specific tabs or notes where OS-specific actions are required.
  • Review other sections for subtle OS-specific terminology or screenshots, ensuring parity for Linux/macOS users where relevant.
GitHub Create pull request
Bias Types:
⚠️ windows_first
Summary:
The documentation page exhibits a subtle 'windows_first' bias. In the 'Deployment considerations' section, the minimum charge for the App Service plan is specifically described as 'one instance of Windows Isolated v2,' with no mention of Linux equivalents or pricing. No command-line examples (PowerShell, Bash, CLI) are present, but the only OS-specific reference is to Windows, and Linux is not mentioned at all in deployment or pricing contexts.
Recommendations:
  • Explicitly mention Linux support and pricing for App Service Environment, especially in the 'Deployment considerations' section.
  • If there are differences in minimum charges or instance types for Linux, document them alongside Windows information.
  • Add a section or note clarifying OS support (Windows and Linux) for App Service Environment v3.
  • Where possible, provide parity in examples, terminology, and guidance for both Windows and Linux users.
GitHub Create pull request

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