← Back to Dashboard
1201
Pages Scanned
4
Pages Flagged
1201
Changed Pages
0.3%
% Pages Flagged

Scan Information

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

Finished At: 2025-07-29 00:05:34

Status: completed

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

Current Phase: discovery

Problematic Pages

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-use-managed-service-identity.md [View Details]
High Priority
Bias Types:
⚠️ powershell_heavy
⚠️ windows_first
⚠️ missing_linux_example
⚠️ windows_tools
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention of Azure CLI or Bash scripting alternatives that are cross-platform and commonly used on Linux and macOS. Windows tools and patterns (such as PowerShell and its cmdlets) are mentioned exclusively and before any cross-platform alternatives. There are no Linux-specific or cross-platform command-line instructions, and the documentation does not acknowledge or guide users on how to perform these tasks outside of the Windows/PowerShell ecosystem.
Recommendations:
  • Add equivalent Azure CLI examples (az apim ...) alongside or before PowerShell examples for all operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide guidance for users on different operating systems.
  • Include Bash scripting examples where appropriate, especially for automation scenarios.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Review and update the documentation structure to avoid always presenting Windows/PowerShell first; consider leading with cross-platform tools or presenting them in parallel.
  • Ensure that all screenshots and UI references are not specific to Windows-only environments.
GitHub Create pull request
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md [View Details]
High Priority
Bias Types:
⚠️ powershell_heavy
⚠️ windows_first
⚠️ missing_linux_example
Summary:
The documentation page demonstrates a Windows bias by featuring PowerShell as the only script example in the 'Automate with scripts' section, with no equivalent Bash or Linux shell example. The automation section lists Azure CLI and PowerShell, but only provides an inline code block for PowerShell, not for CLI or Bash. There are no Linux-specific instructions or screenshots, and the overall flow assumes use of the Azure Portal or Windows-centric tools.
Recommendations:
  • Add Bash or Linux shell script examples alongside PowerShell in the 'Automate with scripts' section.
  • Provide explicit Azure CLI command examples inline, not just as links.
  • Include Linux-specific notes or screenshots where relevant, especially for certificate upload or file path conventions.
  • Ensure parity in automation instructions by presenting Windows and Linux approaches side by side.
  • Reference Linux and macOS environments in prerequisites and troubleshooting sections.
GitHub Create pull request
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md [View Details]
Medium Priority
Bias Types:
⚠️ windows_first
⚠️ missing_linux_example
Summary:
The documentation page demonstrates a moderate Windows bias, primarily by presenting .NET/ASP.NET (Windows-centric) code samples first and in greater detail, while not providing any explicit Linux shell (bash) or OpenSSL command-line examples for certificate handling or validation. The focus is on Azure portal, Azure CLI, Bicep, and ARM templates for configuration, which are cross-platform, but the application code samples are heavily weighted toward Windows technologies. There are no examples of using Linux-native tools or patterns for mutual TLS setup or troubleshooting.
Recommendations:
  • Add Linux shell (bash) and OpenSSL command-line examples for generating, inspecting, and validating client certificates, as these are common on Linux systems.
  • Include explicit instructions or examples for configuring mutual TLS in popular Linux web servers (e.g., Nginx, Apache) when running on Azure App Service for Linux.
  • Balance the order of code samples by presenting cross-platform or Linux-first examples (such as Node.js, Python, or Java) before or alongside Windows/.NET examples.
  • Mention Linux-native troubleshooting tools (e.g., curl, openssl s_client) for verifying mutual TLS connections.
  • Clarify that the provided code samples are applicable to both Windows and Linux App Service plans, or note any platform-specific differences.
GitHub Create pull request
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md [View Details]
Medium Priority
Bias Types:
⚠️ windows_first
⚠️ missing_linux_example
Summary:
The documentation page is largely platform-neutral, focusing on Azure Portal and DNS provider interfaces. However, in the troubleshooting section, the only example for clearing the DNS cache is for Windows (`ipconfig /flushdns`), with no mention of the equivalent commands for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
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, and provide parity in examples where OS-specific actions are mentioned.
  • If automation or scripting is referenced, ensure examples are provided for both PowerShell (Windows) and Bash (Linux/macOS) where relevant.
GitHub Create pull request

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