986
Pages Scanned
13
Pages Flagged
986
Changed Pages
1.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:10
Scan Information
Started At: 2025-12-22 00:00:10
Finished At: In Progress
Status: cancelled
Target Repo: Azure
Current Phase: discovery
Files Queued: 13786
Files Completed: 977
Problematic Pages
13 issues found
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific pivots (Visual Studio, PowerShell, CLI) before Linux equivalents, and by providing dedicated sections for Windows tools (PowerShell, Visual Studio) without clear Linux parity (e.g., Bash, Linux CLI). The presence of multiple Windows pivots and tools suggests a prioritization of Windows workflows and technologies.
Recommendations
- Ensure Linux pivots (e.g., VS Code, Azure Portal, CLI) are presented before or alongside Windows pivots to avoid perceived prioritization.
- Add or highlight Linux-native tools and workflows (e.g., Bash scripts, Linux CLI examples) where Windows tools (PowerShell, Visual Studio) are featured.
- Balance the number of Windows and Linux pivots/examples to provide equal coverage for both platforms.
- Explicitly mention Linux alternatives whenever a Windows-specific tool or pattern is introduced.
- Review included files to ensure Linux instructions are as detailed and prominent as Windows instructions.
Create Pull Request
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/devops-api-development-templates.md
...les/api-management/devops-api-development-templates.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a bias towards Windows and Azure-centric tools and workflows. It exclusively references Azure DevOps, Azure Pipelines, and Visual Studio Code, with no mention of Linux-specific tools, shell examples, or alternative CI/CD platforms commonly used in Linux environments (e.g., Jenkins, GitLab CI, or native bash scripting). The documentation assumes the use of Azure and Windows-oriented tools, and does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
- Include examples and references for Linux-native tools and workflows, such as bash scripts for deployment, or using Jenkins/GitLab CI for CI/CD pipelines.
- Mention and provide examples for cross-platform CLI tools (e.g., Azure CLI) with explicit Linux usage instructions.
- Add alternative editor suggestions (e.g., Vim, Emacs, JetBrains IDEs) alongside Visual Studio Code.
- Provide explicit Linux shell command examples for common tasks (e.g., deploying ARM templates or using Terraform from bash).
- Reference and link to documentation for running Azure DevOps pipelines or GitHub Actions runners on Linux hosts.
- Balance the order of tool presentation, ensuring Linux-friendly options are mentioned alongside or before Windows-centric ones.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview.md
.../azure-docs/blob/main/articles/app-service/overview.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page displays a Windows bias, particularly in the 'Managed Instance on App Service (preview)' section, which focuses exclusively on Windows-specific features (COM, registry, MSI, drive mapping, PowerShell, RDP) and tools. Windows tools and patterns (PowerShell, RDP, registry, MSI) are mentioned without Linux equivalents or alternatives. While the general overview claims support for both Windows and Linux, concrete examples and advanced features are Windows-centric, and Linux/container support is only mentioned as 'not supported' in the Managed Instance context. There are no Linux-specific examples or advanced scenarios provided.
Recommendations
- Provide Linux-specific advanced scenarios or features, especially in sections where Windows features are highlighted (e.g., Managed Instance).
- Include Linux command-line examples (e.g., Bash scripts) alongside PowerShell examples where relevant.
- Mention Linux tools and patterns (such as systemd, cron, or Linux package managers) when discussing automation or configuration.
- Clarify feature parity and limitations for Linux and containers, and link to Linux/container-specific documentation for advanced use cases.
- Ensure that when listing command-line tools, Linux-native tools (e.g., Azure CLI in Bash) are given equal prominence to Azure PowerShell.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-generic-saml-options.md
...irectory-b2c/identity-provider-generic-saml-options.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the 'Debug SAML protocol' section, where Windows-specific tools (Microsoft Edge and Internet Explorer developer tools) are mentioned alongside browser extensions, and the Windows tools are listed last but with a dedicated link. No Linux-specific SAML debugging tools or command-line utilities are referenced, and there are no examples using Linux-native tools or patterns throughout the page. The documentation does not provide parity for Linux users in troubleshooting or debugging SAML integrations.
Recommendations
- Add references to Linux-compatible SAML debugging tools, such as command-line utilities (e.g., curl, openssl, xmlsec1) for inspecting SAML requests/responses.
- Include guidance or examples for using Linux browser developer tools (e.g., Chrome/Firefox DevTools on Linux) for SAML tracing.
- Mention cross-platform browser extensions explicitly as available on Linux, macOS, and Windows.
- Provide troubleshooting steps using Linux shell commands to parse or inspect SAML XML files.
- Avoid listing Windows tools exclusively or giving them prominence; ensure Linux and macOS users are equally supported in all example and tooling recommendations.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-azure-database.md
...les/app-service/tutorial-connect-msi-azure-database.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation exhibits a Windows bias by presenting Visual Studio for Windows instructions before macOS and VS Code, emphasizing Windows-integrated authentication, and providing explicit Azure PowerShell examples. Windows-specific tools and patterns (Visual Studio for Windows, Azure PowerShell) are described in greater detail, while Linux-native or cross-platform alternatives (such as Linux IDEs or shell environments) are not mentioned. The macOS and VS Code sections rely on Azure CLI, but Linux is not referenced directly as a development environment, nor are Linux-specific tools or workflows discussed.
Recommendations
- Add explicit instructions for setting up development environments on Linux, including common IDEs (e.g., JetBrains Rider, VS Code on Linux, or command-line workflows).
- Provide parity in authentication setup examples for Linux users, such as using Azure CLI and environment variables.
- Mention Linux as a supported platform in the prerequisites and environment setup sections.
- Include troubleshooting tips and code samples relevant to Linux environments (e.g., bash shell, Linux file paths, package managers).
- Ensure that cross-platform tools (Azure CLI, VS Code) are presented before or alongside Windows-specific tools to avoid Windows-first ordering.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md
...ain/articles/app-service/configure-custom-container.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several Windows-centric biases. Windows-specific details, examples, and tooling (such as PowerShell and Windows Server image recommendations) are often presented first or exclusively, while Linux equivalents are sometimes less detailed or omitted. PowerShell commands are frequently included alongside Bash, and Windows-specific concepts (like IIS, .NET Framework, and C:\home) receive more thorough coverage. Some advanced configuration and troubleshooting sections are richer for Windows than for Linux, and certain Linux instructions (e.g., SSH setup) are relegated to later sections.
Recommendations
- Ensure Linux examples and instructions are presented with equal prominence and detail as Windows, including parent image recommendations and troubleshooting steps.
- Where PowerShell commands are provided, always include equivalent Bash or shell commands for Linux users, and consider listing Bash first in Linux-focused sections.
- Expand Linux-specific guidance for advanced topics such as persistent storage, diagnostic logging, and environment variable management to match Windows coverage.
- Avoid Windows-first ordering in general sections; use neutral or parallel presentation for cross-platform features.
- Clarify differences in default behaviors (e.g., persistent storage enabled/disabled) in a comparative table or summary for quick reference.
- Add more Linux-specific troubleshooting tips and references, similar to the depth given for Windows containers.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several ways: Windows tools and terminology (Command Prompt, PowerShell) are mentioned first and explicitly, while Linux equivalents are not described or are only implied. There are no explicit Linux shell examples or instructions for Linux-specific environments. The Azure CLI example is presented generically, but the context and instructions assume a Windows environment. The documentation lacks parity in step-by-step guidance for Linux users, such as using Bash or Linux-specific file paths and shell commands.
Recommendations
- Explicitly mention Linux and macOS as supported environments in prerequisites and steps.
- Provide Linux/Bash shell examples alongside Windows Command Prompt/PowerShell instructions.
- Use neutral terminology such as 'terminal' or 'command shell' instead of 'Windows Command Prompt, PowerShell'.
- Include notes or examples for Linux-specific Azure CLI installation and usage.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, path separators).
- Ensure all file paths and commands are cross-platform or provide platform-specific variants.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/quickstart-template-review-resources.md
...enter/includes/quickstart-template-review-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools to review deployed resources, but does not provide explicit Linux-specific examples or mention Linux shell usage. Azure PowerShell is primarily a Windows tool, and its mention before any Linux alternatives (such as Bash or shell scripting) suggests a Windows-first perspective.
Recommendations
- Include explicit examples using Azure CLI in Bash or other Linux shells.
- Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (PowerShell) and Linux (Bash).
- Mention Linux-native tools or patterns where appropriate.
- Avoid listing Windows-specific tools (like Azure PowerShell) before cross-platform alternatives unless contextually justified.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md
...to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation displays mild Windows bias by referencing Windows-specific tools (PowerShell, Azure portal) before Linux alternatives and using Windows-style path separators (e.g., .\opentelemetry-collector-config.yml) in command examples. However, most technical steps use cross-platform tools (Helm, kubectl, curl), and Linux users can follow along with minimal adaptation.
Recommendations
- Present Linux and Windows options equally when listing tools (e.g., mention Azure CLI before PowerShell or in parallel).
- Use platform-neutral path separators in command examples (e.g., './opentelemetry-collector-config.yml' instead of '.\opentelemetry-collector-config.yml').
- Explicitly note that all commands work on Linux, macOS, and Windows, and provide any necessary adaptations for each platform.
- Where PowerShell or Azure portal is mentioned, also provide direct Linux CLI equivalents or links.
- Add a note in prerequisites clarifying that Helm, kubectl, and curl are available on all major platforms.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/inject-vnet-v2.md
...cs/blob/main/articles/api-management/inject-vnet-v2.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Windows and Linux/macOS locations for the hosts file when describing DNS testing, but lists the Windows path first. No PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples are present. The overall instructions are platform-neutral except for the ordering in the hosts file example.
Recommendations
- List both Windows and Linux/macOS hosts file paths together, or alternate the order in which they are presented to avoid implicit prioritization.
- Explicitly provide example commands for editing the hosts file on both platforms (e.g., using Notepad on Windows, nano/vim on Linux/macOS).
- Ensure future examples and screenshots show parity between Windows and Linux environments where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/quickstart-python/deploy-zip-azure-portal-2.md
...ncludes/quickstart-python/deploy-zip-azure-portal-2.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions for setting a configuration value using a dialog, but does not specify or illustrate how to perform this action on Linux systems (e.g., via CLI, environment variables, or configuration files). There are no explicit Windows tools mentioned, but the lack of Linux-specific guidance may hinder Linux users.
Recommendations
- Add examples for setting the configuration using the Azure CLI, which is cross-platform.
- Include instructions for setting environment variables directly in Linux shells (e.g., export SCM_DO_BUILD_DURING_DEPLOYMENT=true).
- Clarify whether the dialog is available on all platforms, or provide alternative methods for Linux users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-workspaces-resources.md
...api-management/virtual-network-workspaces-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Windows and Linux/macOS locations for the hosts file, but lists the Windows path first. No command-line examples (PowerShell, Bash, etc.) are given, and no Windows-specific tools or patterns are emphasized. However, the ordering of the hosts file paths is a subtle instance of Windows-first bias.
Recommendations
- List Linux/macOS hosts file location before Windows, or present both simultaneously (e.g., '/etc/hosts (Linux/macOS), %SystemDrive%\drivers\etc\hosts (Windows)').
- Provide explicit examples for updating the hosts file on both Windows and Linux/macOS, including sample commands (e.g., using 'echo' or 'notepad' on Windows, 'echo' or 'nano' on Linux).
- Ensure future documentation includes parity in examples and tool references for both platforms, especially when manual configuration steps are described.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-connect-to-azure-storage.md
...cles/app-service/configure-connect-to-azure-storage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows code and container examples before Linux container examples, indicating a 'windows_first' bias. However, Linux content is present and not missing.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel tabs to avoid implying priority.
- Explicitly mention that both Windows and Linux are supported at the top of the page.
- Ensure that Linux examples are as detailed and accessible as Windows examples.
- Consider adding a summary table comparing Windows and Linux approaches for quick reference.