Scan Details - Linux-first Docs for Azure

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias in several areas: certificate generation and upload steps link to Windows-specific instructions, and there are no Linux or cross-platform alternatives provided for these steps. Application code samples and configuration focus on ASP.NET MVC (a Windows-centric framework), and there is no mention of Linux-based application frameworks or tools. The documentation assumes the use of Windows tools and patterns, omitting equivalent Linux guidance.

Recommendations:

Provide Linux and cross-platform instructions for certificate generation and upload (e.g., using OpenSSL for certificate creation, with command-line examples).
Include alternative application samples using popular Linux-friendly frameworks (such as Node.js/Express, Python/Flask, or Java/Spring) for the OpenID Connect integration.
When referencing documentation links (such as for certificate management), ensure both Windows and Linux tabs are present and linked, or provide explicit cross-platform guidance.
Clarify that the steps and tools are not limited to Windows, and provide notes or links for Linux users where appropriate.
Add example commands and configuration snippets for Linux environments (e.g., bash commands for file operations, Docker usage, etc.).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell-specific instructions and examples (e.g., using the Update-MgDomain cmdlet from the Microsoft Graph PowerShell module) without offering equivalent command-line examples for Linux or macOS users. The documentation references Windows tools and patterns exclusively, with no mention of cross-platform alternatives such as Azure CLI, Bash scripts, or REST API usage from non-Windows environments. All step-by-step instructions and code snippets assume the use of the Azure Portal or PowerShell, both of which are more familiar to Windows users.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell commands, especially for updating password expiry settings.
Include REST API examples using curl or HTTPie for PATCH operations, demonstrating usage from Linux/macOS terminals.
Explicitly mention that the Microsoft Graph PowerShell module is available cross-platform, or provide installation instructions for Linux/macOS.
Where possible, structure instructions so that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
Add a section or note clarifying that all operations can be performed from any OS, and link to relevant cross-platform tool documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes setting up and running a WPF (Windows Presentation Foundation) desktop application using Visual Studio, a Windows-only tool. All instructions, screenshots, and workflow steps are tailored for Windows environments, with no mention of Linux or cross-platform alternatives. There are no Linux or macOS instructions, nor are there references to cross-platform frameworks or tools.

Recommendations:

Provide equivalent instructions for running a cross-platform desktop application (e.g., using .NET MAUI or Avalonia UI) that works on Linux and macOS.
Include setup and run instructions for Linux (and optionally macOS), such as using Visual Studio Code or JetBrains Rider, and relevant .NET CLI commands.
Add Linux/macOS-specific prerequisites, such as installing the .NET SDK and any required dependencies.
Offer alternative screenshots and workflow steps for Linux/macOS environments.
Clarify in the introduction that the current quickstart is Windows-specific, and link to cross-platform guides if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a bias towards Windows environments, particularly in the section on creating self-signed certificates, where only PowerShell is mentioned as a method. There are no examples or instructions for Linux or cross-platform tools (such as OpenSSL) for certificate creation. The documentation assumes the use of Windows tooling and does not provide parity for Linux or macOS users.

Recommendations:

Add instructions and examples for creating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
Wherever PowerShell is referenced, provide equivalent bash or shell commands for Linux/macOS environments.
Explicitly mention that the certificate creation steps can be performed on any OS, and provide links or references to cross-platform tooling.
Review other sections for similar tool-specific assumptions and ensure parity in examples and guidance for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform shells (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) may disadvantage Linux users or those preferring non-Windows scripting environments. There is no mention of how to perform the same tasks using common Linux tools or languages.

Recommendations:

Provide a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, including authentication via client credentials.
Include a Python script example using the requests library to demonstrate cross-platform access.
Explicitly mention that the API can be accessed from any platform and provide guidance for Linux/macOS users.
Where PowerShell is used, add a note or section for equivalent Linux/macOS commands or scripts.
Consider referencing platform-agnostic tools (e.g., HTTPie, curl, Python) before or alongside PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides PowerShell-only examples for disabling certificate chain validation, with no equivalent examples for Linux-native tools (such as Azure CLI, Bash, or REST API via curl). The use of PowerShell cmdlets as the only code sample assumes a Windows environment or Windows PowerShell Core, and there is no mention of Linux command-line workflows or tools. This may hinder Linux users or those who prefer cross-platform tooling.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for tasks like disabling certificate chain validation.
Include REST API usage examples with curl or HTTPie to demonstrate cross-platform approaches.
Explicitly mention that PowerShell Core is cross-platform if relevant, or clarify if the examples require Windows PowerShell.
Where possible, provide Bash script snippets or references for Linux users.
Ensure that any tool or workflow mentioned (such as certificate management) is accompanied by both Windows and Linux-compatible instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards the Azure portal UI and Microsoft Entra ID, with all examples and instructions assuming use of the Azure web portal. There are no command-line examples (neither PowerShell nor CLI), but all tool references are Microsoft/Azure-specific, with no mention of Linux, cross-platform, or open-source alternatives. The documentation does not provide parity for Linux users or those who prefer CLI-based workflows.

Recommendations:

Include Azure CLI examples for all steps that can be performed via command line, ensuring instructions are cross-platform.
Where possible, provide REST API examples for automation and scripting, which are OS-agnostic.
Mention and link to open-source OAuth 2.0 providers or tools (such as Keycloak, Auth0, or generic OAuth 2.0 servers) and show how to configure API Management with them.
Explicitly state that the Azure portal is web-based and accessible from any OS, but also provide alternatives for users who prefer not to use a GUI.
Add a section or callout for Linux/macOS users, clarifying that all steps can be performed from any OS, and providing any OS-specific considerations if necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation references a link for securing REST APIs with a query parameter '?tabs=windows', suggesting that Windows-specific instructions are prioritized or presented first. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux tooling or parity in the referenced sections. The documentation assumes a Windows environment for certain setup steps, which may hinder Linux users.

Recommendations:

Ensure that all referenced links (such as 'secure-rest-api.md?tabs=windows') provide Linux/macOS tabs or examples, and mention this in the documentation.
Explicitly state that the instructions are cross-platform where applicable, or provide parallel Linux/macOS instructions if differences exist.
Avoid using Windows-specific query parameters or language in documentation unless absolutely necessary; instead, use neutral or multi-platform phrasing.
Where command-line or scripting is referenced, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
Audit all referenced guides for similar bias and update them to ensure Linux parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Visual Studio and path length limitations (260 characters) that are primarily relevant to Windows. While Visual Studio Code is mentioned as a cross-platform alternative, there are no explicit Linux/macOS-specific instructions or examples (e.g., for running, building, or troubleshooting the .NET app on Linux). The documentation assumes familiarity with Windows tooling and omits Linux-specific considerations, such as file permissions, environment variables, or alternative editors/IDEs.

Recommendations:

Explicitly mention that Visual Studio Code and .NET SDK are cross-platform, and provide links or notes for Linux/macOS installation.
Include Linux/macOS-specific instructions or notes for running and building the sample (e.g., using the dotnet CLI in a terminal).
Clarify that the 260-character path length limitation is a Windows-specific constraint, and note that Linux/macOS users are not affected.
Provide troubleshooting tips or common issues for Linux/macOS users (e.g., file permissions, HTTPS development certificates).
Consider including example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash) where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and by linking to IIS-specific setup instructions. There are no equivalent examples or guidance for Linux-based web servers or applications, and no mention of Linux tools or deployment patterns. All other instructions are platform-agnostic, focusing on Azure, F5 BIG-IP, and browser-based configuration.

Recommendations:

Provide Linux-based application examples (e.g., Apache, Nginx) alongside the IIS example for testing.
Include links or references to documentation for setting up a test web application on Linux.
Clarify that the solution is compatible with both Windows and Linux back-end applications.
Where possible, use neutral language (e.g., 'web application') instead of referencing only IIS.
Add troubleshooting notes or configuration tips relevant to common Linux web servers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform neutrality but exhibits subtle Windows bias in the DNS configuration section. The hosts file path is listed as '%SystemDrive%\drivers\etc\hosts' (Windows) before '/etc/hosts' (Linux, macOS), and a related link in 'Related content' points to a Windows 2000 Server DNS article. No Linux-specific tools or commands are mentioned, and no Linux-first or Linux-only examples are provided.

Recommendations:

List Linux and Windows hosts file paths in parallel or alternate the order to avoid 'windows_first' bias.
Provide links to cross-platform or Linux/macOS-specific DNS configuration documentation, not just Windows resources.
Include example commands for editing the hosts file on both Windows (e.g., using Notepad with admin rights) and Linux/macOS (e.g., using sudo nano or vi).
Where possible, reference cross-platform tools or provide equivalent instructions for both operating systems.
Review 'Related content' to ensure Linux and macOS users are equally supported with relevant links.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell, but there is also a complete absence of Linux (or cross-platform) CLI examples (such as Azure CLI or Bash). This omission can be considered a subtle form of Windows bias, as the Azure portal is often associated with Windows-centric workflows and many users on Linux or macOS prefer CLI-based instructions. Additionally, the lack of CLI parity may hinder automation and scripting, which are common in Linux environments.

Recommendations:

Add Azure CLI examples for all major steps, such as importing an API, configuring authentication, and testing endpoints.
Provide Bash script snippets for downloading and editing the OpenAPI specification.
Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide cross-platform instructions where possible.
Include references to relevant Azure CLI documentation and ensure that screenshots or UI instructions are supplemented with equivalent CLI commands.

Create pull request

Scan Information

Problematic Pages