Scan Details - Linux-first Docs for Azure

1343

Pages Scanned

17

Pages Flagged

1343

Changed Pages

1.3%

% Pages Flagged

Scan Information

Started At: 2025-09-09 00:00:08

Finished At: 2025-09-09 00:27:45

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

Summary:

The documentation provides a PowerShell example for configuring password expiry duration using the Microsoft Graph PowerShell module, but does not offer equivalent command-line examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST with curl). The focus on PowerShell and lack of cross-platform command-line instructions introduces a Windows bias.

Recommendations:

Provide equivalent examples using Azure CLI or Bash scripts (with curl) for Linux/macOS users alongside PowerShell commands.
Explicitly mention that the PowerShell module can be used on non-Windows platforms, if applicable, and provide installation instructions for those platforms.
Where possible, present REST API calls with sample commands using curl or HTTPie to demonstrate platform-agnostic approaches.
Ensure that any references to tools or commands are balanced, giving equal prominence to both Windows and Linux/macOS workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a bias towards Windows by exclusively providing PowerShell scripts for testing the REST API, referencing Microsoft PowerShell as the primary HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The only terminal-based example for making HTTP requests is in PowerShell, and there is no mention of Linux-native tools or cross-platform alternatives. This may hinder Linux/macOS users from following the guide seamlessly.

Recommendations:

Provide equivalent Linux/macOS command-line examples using curl or HTTPie alongside the PowerShell script.
When referencing HTTP clients, mention cross-platform tools (e.g., curl, HTTPie, Postman) before or alongside Microsoft PowerShell.
Explicitly state that the steps and tools are cross-platform where possible, or provide platform-specific instructions as needed.
Ensure that all code snippets and instructions are tested and applicable on both Windows and Linux/macOS environments.
Consider adding a table or section summarizing how to perform key steps (such as making HTTP requests) on different operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It explicitly instructs users to generate GUIDs using Microsoft PowerShell before mentioning online alternatives, and the first scripting example for obtaining tokens is in PowerShell. While a cURL (cross-platform) example is provided, the ordering and language suggest a Windows-first approach. There are no Linux-specific tools or shell examples, and the PowerShell method is referenced as the default for certain tasks.

Recommendations:

When instructing users to generate GUIDs, mention both PowerShell and Linux/macOS equivalents (e.g., `uuidgen`), or list the cross-platform/online method first.
Provide scripting examples in both PowerShell and Bash (or at least shell-agnostic cURL) side by side, or clearly indicate that both are supported.
Avoid presenting Windows-specific tools or commands as the default or only method; always include Linux/macOS alternatives.
Consider adding a table or section summarizing equivalent commands for common tasks (e.g., GUID generation, HTTP requests) across Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically targeting WPF (Windows Presentation Foundation) desktop applications and requiring Visual Studio 2019 for development. There are no references to Linux or cross-platform alternatives, and all instructions and code samples assume a Windows environment. No Linux-compatible frameworks, tools, or development environments are mentioned or suggested.

Recommendations:

Include a section or note clarifying that WPF is Windows-only, and suggest cross-platform alternatives (such as .NET MAUI or Avalonia) for Linux/macOS users.
Provide equivalent instructions and code samples for a cross-platform desktop application (e.g., using Avalonia or .NET MAUI) that can run on Linux.
Mention and provide guidance for using cross-platform IDEs (such as Visual Studio Code or JetBrains Rider) and the .NET CLI, instead of only Visual Studio 2019.
If possible, provide sample projects and setup instructions that work on Linux, including package restore and build/run commands using the .NET CLI.
Explicitly state the platform limitations early in the documentation to set expectations for non-Windows developers.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and by linking only to IIS setup instructions. There are no equivalent examples or instructions for deploying or testing with a Linux-based web application (such as Apache or Nginx). Additionally, the documentation does not mention or provide guidance for Linux tools or environments, and all application setup references are Windows-centric.

Recommendations:

Provide parallel instructions for setting up a test web application on Linux (e.g., Apache, Nginx) alongside the IIS example.
Include links to official documentation for deploying and configuring Linux-based web servers.
When referencing application setup, use neutral language (e.g., 'a web application such as IIS, Apache, or Nginx') and provide examples for both Windows and Linux platforms.
Ensure troubleshooting and configuration steps are applicable to both Windows and Linux environments, or clearly indicate platform-specific differences.
If scripts or commands are provided, include both PowerShell (Windows) and Bash (Linux) equivalents where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as a method for preparing a self-signed certificate. There are no Linux or cross-platform alternatives (such as OpenSSL) provided for certificate generation, and no Linux command-line examples are present. The rest of the documentation is largely platform-neutral, focusing on Azure portal steps and XML configuration, but the omission of Linux tooling for a key security step is a notable gap.

Recommendations:

Add Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL, alongside the PowerShell example.
Explicitly mention that certificate generation can be performed on any OS, and provide equivalent commands for macOS and Linux.
Wherever PowerShell or Windows-specific tooling is referenced, provide a parallel example for Linux/macOS users.
Consider including a table or section summarizing certificate creation options for Windows, Linux, and macOS, with links to official documentation for each.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally platform-neutral for most tasks, as it focuses on using the Azure portal (web interface). However, in the 'Revoke a consumer user's session' section, only Microsoft Graph PowerShell is provided as a command-line example, and the instructions explicitly reference 'Windows PowerShell' without mentioning cross-platform compatibility or alternatives for Linux/macOS users. There are no CLI, Bash, or platform-agnostic command examples, nor is it clarified that Microsoft Graph PowerShell is available on non-Windows platforms.

Recommendations:

Clarify that Microsoft Graph PowerShell is cross-platform and can be used on Linux and macOS, not just Windows.
Replace references to 'Windows PowerShell' with 'PowerShell' or 'a PowerShell terminal', and provide installation instructions for Linux/macOS if needed.
Provide equivalent examples using Azure CLI, Bash, or direct Microsoft Graph API calls with curl or HTTPie for Linux/macOS users.
Explicitly state that all command-line instructions are platform-agnostic where possible, or provide separate instructions for each major OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no examples or instructions for Linux or cross-platform desktop frameworks, nor are alternative tools or workflows mentioned for non-Windows users.

Recommendations:

Include equivalent instructions for running the sample on Linux and macOS, such as using .NET Core/MAUI or Avalonia UI for cross-platform desktop development.
Provide guidance for using alternative IDEs like VS Code or JetBrains Rider, which are available on Linux and macOS.
Add steps for restoring NuGet packages and running the application via the command line (dotnet CLI), not just through Visual Studio.
Mention any platform-specific limitations or requirements, and offer alternative sample applications or code for non-Windows environments.
Explicitly state the Windows-only nature of the WPF sample and link to cross-platform alternatives if available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio (a Windows-centric IDE), uses Windows solution files (.sln), and describes steps using Visual Studio UI elements (e.g., Solution Explorer, right-click actions, F5 to debug). There are no instructions or examples for running the sample on Linux or macOS, nor are alternative tools (such as VS Code, JetBrains Rider, or command-line .NET tools) mentioned.

Recommendations:

Add instructions for running the sample using cross-platform tools such as Visual Studio Code or JetBrains Rider.
Include steps for building and running the application using the .NET CLI (dotnet build, dotnet run), which works on Linux and macOS.
Mention prerequisites for Linux/macOS users, such as installing the .NET SDK and any required dependencies.
Provide equivalent screenshots or terminal output for Linux/macOS environments where relevant.
Clarify that Visual Studio is optional and provide parity in guidance for non-Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell script example for accessing audit logs programmatically, with no equivalent example for Linux or cross-platform shells (e.g., Bash/cURL). The script uses PowerShell-specific cmdlets and patterns, and there is no mention of Linux-native tools or guidance for non-Windows users. The only automation example is Windows-centric, and the documentation does not acknowledge or address Linux or macOS environments.

Recommendations:

Provide a Bash/cURL example for accessing the Microsoft Graph API to retrieve audit logs, including authentication and pagination handling.
Explicitly mention that the API can be accessed from any platform and provide cross-platform code samples.
Include instructions or links for using common Linux tools (e.g., wget, curl, jq) to perform the same tasks as the PowerShell script.
Reorganize the automation section to present both Windows (PowerShell) and Linux/macOS (Bash/cURL) examples side by side, or lead with a platform-neutral API example.
Add a note clarifying that the PowerShell script can be run in Azure Cloud Shell (which supports PowerShell and Bash), but also provide a Bash example for parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is largely platform-neutral, focusing on HTTP requests and protocol details. However, in the section on testing POST HTTP requests, only Microsoft PowerShell is mentioned as an example HTTP client, with no mention of Linux or cross-platform alternatives. There are no explicit examples or instructions for Linux users, nor are Linux-native tools (such as curl or httpie) referenced.

Recommendations:

When suggesting HTTP clients for testing, mention cross-platform and Linux-native tools such as curl, httpie, or wget alongside PowerShell.
Provide example commands using curl or httpie for making POST and GET requests, ensuring Linux users have clear, ready-to-use examples.
Avoid referencing only Windows-specific tools or interfaces; always include at least one cross-platform or Linux-native alternative when demonstrating command-line interactions.
Consider adding a short section or callout noting that all HTTP requests can be performed using standard tools available on Linux, macOS, and Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation contains a subtle Windows bias. In the few places where platform-specific instructions are referenced (such as securing REST APIs with OAuth2 bearer tokens), the documentation links to instructions with a 'tabs=windows' parameter, and does not mention or provide Linux-specific examples or parity. There are no explicit PowerShell or Windows-only tool examples, but the guidance assumes the reader is using Windows as the default environment for certain steps.

Recommendations:

Wherever documentation links include platform-specific tabs (e.g., 'tabs=windows'), ensure that Linux (and macOS, if applicable) tabs are also referenced or mentioned, so users on those platforms know equivalent instructions exist.
Explicitly mention that the steps for securing REST APIs, obtaining tokens, and other platform-sensitive operations can be performed on Linux and macOS, and provide direct links or notes to those instructions.
Review all linked documentation to ensure Linux parity and add clarifying notes in this guide if any steps differ between Windows and Linux.
If any scripts, CLI commands, or setup steps are provided in the future, ensure both Windows (PowerShell/CMD) and Linux (Bash/CLI) examples are included side-by-side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by referencing Visual Studio (a primarily Windows tool) before Visual Studio Code in the prerequisites, and by not providing explicit Linux/macOS instructions or examples for running or building the sample application. There are no PowerShell-specific commands or Windows-only tools mentioned, but the lack of Linux/macOS parity in setup and execution steps may disadvantage non-Windows users.

Recommendations:

Explicitly include instructions for Linux/macOS users, such as using the dotnet CLI to build and run the project (e.g., 'dotnet build', 'dotnet run').
Clarify that Visual Studio Code and the .NET SDK are cross-platform, and provide terminal commands for common tasks (restoring dependencies, running the app) on Linux/macOS.
Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, HTTPS development certificates, path length differences).
Where screenshots or UI steps are shown for Visual Studio, consider including equivalent steps for Visual Studio Code or CLI usage.
Mention any platform-specific requirements or differences, such as installing the .NET SDK on Linux/macOS, or handling HTTPS development certificates.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally provides cross-platform guidance, but there are subtle signs of Windows bias. The instruction to extract the sample to a folder with a path length of 260 or fewer characters references a Windows-specific limitation. Additionally, in the 'Run the sample web app' section, the Windows example uses 'py' instead of 'python', which is a Windows-specific launcher, and the order of examples places Linux and macOS before Windows, but the path length warning appears before any OS-specific instructions.

Recommendations:

Clarify that the 260-character path length limitation is specific to Windows, and note that Linux/macOS users are not affected.
In the 'Run the sample web app' section, explicitly state that 'py' is the Windows Python launcher, and that 'python' should be used on Linux/macOS.
Consider providing a note or table summarizing OS-specific differences (such as path length limits and Python launcher usage) to improve clarity for all users.
Ensure that any filesystem or tool limitations are clearly attributed to their respective platforms to avoid confusion.
Continue to provide parallel examples for all major platforms, and avoid assuming Windows-specific behaviors apply to all users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias, particularly in the certificate creation and upload steps, where only Windows-specific instructions or links are provided. There are no explicit Linux or cross-platform examples for tasks such as certificate management, and the application example for OIDC is based on ASP.NET MVC (a Windows-centric technology), with no mention of Linux or open-source alternatives.

Recommendations:

Provide Linux and macOS instructions for certificate creation and management (e.g., using OpenSSL) alongside or before Windows-specific instructions.
Include examples of registering and configuring applications using cross-platform frameworks (e.g., Node.js, Python Flask/Django, Java Spring) in addition to ASP.NET MVC.
Ensure that all referenced documentation (such as certificate upload and management) includes tabs or sections for Linux, macOS, and Windows.
When referencing command-line tools or scripts, offer both PowerShell/Windows and Bash/Linux equivalents.
Explicitly state that the process is platform-agnostic where possible, and highlight any steps that are unique to a particular OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio Code and its Azure Functions extension as the primary development environment, and by mentioning 'terminal or command prompt' without explicitly referencing Linux or macOS shells. There are no explicit Linux-specific instructions or examples, and all tooling references (e.g., Visual Studio Code, Azure portal) are platform-neutral but implicitly assume familiarity with Windows-centric workflows. There are no PowerShell-specific commands, but the lack of Linux/macOS terminal examples or explicit parity is notable.

Recommendations:

Explicitly mention that all steps can be performed on Linux and macOS, not just Windows.
Provide example commands for common Linux/macOS shells (e.g., bash, zsh) where relevant, especially for environment variable management and local development.
Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and provide installation links/instructions for Linux/macOS.
Where 'terminal or command prompt' is mentioned, add 'or shell' and clarify with examples for bash/zsh.
If screenshots or UI flows differ on Linux/macOS, provide alternative visuals or notes.
Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific command-line examples or tooling references (such as PowerShell or Windows tools), but it also does not include any Linux-specific examples or mention of Linux command-line tools. All instructions are given via the Azure Portal UI or Microsoft Graph API, which are platform-agnostic. However, the absence of any CLI or scripting examples (for either Windows or Linux) means there is a lack of parity for users who may prefer or require automation via shell scripts or Linux-native tools.

Recommendations:

Add examples for managing policy keys using cross-platform command-line tools, such as Azure CLI and Microsoft Graph API via curl or HTTPie, with explicit Linux and macOS shell examples.
If scripting is discussed in future updates, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are provided.
Mention that the Azure Portal and Microsoft Graph API are accessible from any operating system, and provide links to relevant CLI documentation for both Windows and Linux users.
Include troubleshooting or automation tips that are relevant for Linux environments, such as using cron jobs for key rotation automation.

Create pull request

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