Scan Details - Linux-first Docs for Azure

332

Pages Scanned

44

Pages Flagged

332

Changed Pages

13.3%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

20:32:51 Scan started

Scan Information

Started At: 2025-07-13 20:32:51

Finished At: In Progress

Status: cancelled

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

Current Phase: discovery

Problematic Pages

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. There are no examples or guidance for developing or running equivalent applications on Linux or macOS, nor are cross-platform .NET or authentication approaches discussed. All tooling and code samples assume a Windows environment.

Recommendations:

Provide equivalent instructions and code samples for cross-platform .NET desktop applications (e.g., using .NET MAUI or Avalonia UI) that can run on Linux and macOS.
Include guidance for setting up the development environment and running the sample on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI).
Mention and demonstrate how to use the Microsoft Authentication Library (MSAL) in a cross-platform context.
Clarify which steps are Windows-specific and offer alternatives or notes for non-Windows users.
If WPF is required, explicitly state that the sample is Windows-only and link to cross-platform alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias toward Windows by providing only PowerShell scripts for testing the REST API, mentioning Microsoft PowerShell as the example HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). Additionally, the documentation references Windows-centric tools (PowerShell) without mentioning or prioritizing cross-platform or Linux-native alternatives.

Recommendations:

Provide equivalent Linux/macOS examples using common tools such as curl or httpie alongside PowerShell scripts.
When referencing PowerShell, clarify that it is available cross-platform, or provide Bash/zsh alternatives.
List cross-platform or Linux-native tools (curl, wget, httpie) before or alongside Windows tools in all example sections.
Explicitly mention that all steps can be performed on Linux/macOS, and note any OS-specific differences.
Consider including screenshots or terminal output from both Windows and Linux environments to reinforce parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a strong Windows bias by exclusively providing PowerShell scripts and instructions, with no mention of Bash, shell scripts, or cross-platform alternatives. All automation and deployment steps are described using PowerShell, which is traditionally associated with Windows environments, and there are no Linux-specific or cross-platform examples. The use of PowerShell as the only scripting language and the absence of any reference to Linux-native tools or commands may hinder users working in Linux-based CI/CD environments.

Recommendations:

Provide equivalent Bash or shell script examples for deploying policies, ensuring Linux users can follow along without needing PowerShell.
Explicitly mention that PowerShell Core is cross-platform and provide guidance for installing and running scripts on Linux/macOS, if PowerShell must be used.
Include notes or sections on how to adapt the deployment process for Linux agents in Azure Pipelines, such as using Bash tasks or alternative scripting languages.
List both Windows and Linux prerequisites, including any required tools or dependencies for each platform.
Where possible, use platform-agnostic language and tools, or clearly indicate when a step is specific to Windows or PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias by providing command-line instructions and examples that implicitly or explicitly target Windows users. The only explicit shell example for running the application is labeled as 'powershell', and there is no mention of Linux or macOS-specific shell commands, nor any guidance for non-Windows environments. There are no references to Windows-only tools, but the use of 'powershell' and lack of Linux parity in command-line instructions may confuse or exclude Linux/macOS users.

Recommendations:

Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples for all shell instructions, especially for installing dependencies and running the app.
Use neutral shell syntax (e.g., $ npm install, $ node index.js) or provide tabs for different OSes.
Avoid labeling generic npm or node commands as 'powershell' unless there are actual PowerShell-specific commands.
Explicitly state that the instructions work on Windows, Linux, and macOS, and mention any OS-specific considerations if applicable.
Add a note or section for Linux/macOS users, clarifying any differences (such as using 'node index.js' instead of 'npm ./index.js', which is not standard npm usage).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (such as Server Manager and AD FS Management MMC), and does not provide any Linux-based alternatives or command-line instructions for managing AD FS. All configuration steps for AD FS are described using GUI tools available only on Windows Server, with no mention of PowerShell, CLI, or cross-platform approaches. There are no Linux or non-Windows examples for AD FS setup, and the documentation implicitly assumes the administrator is operating in a Windows environment.

Recommendations:

Provide PowerShell command-line equivalents for all AD FS configuration steps, as PowerShell can be run on Windows Server Core and remotely.
Explicitly mention that AD FS is a Windows Server feature, but clarify what steps (if any) can be performed from non-Windows environments (e.g., via remote PowerShell, REST APIs, or Azure CLI).
If possible, reference or link to any open-source or third-party tools that allow AD FS management from Linux or macOS, or clarify that such options are not available.
Add a note early in the prerequisites section stating that AD FS management is only supported on Windows Server, and suggest alternatives for Linux-based identity providers if relevant.
Where possible, provide parity by showing how to configure a generic OpenID Connect provider using Linux-based identity solutions (such as Keycloak or IdentityServer) as a comparative example.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily oriented towards Windows environments, specifically referencing Windows-only tools (AD FS Management snap-in, Event Viewer, Server Manager) and PowerShell cmdlets for configuration and troubleshooting. There are no Linux or cross-platform alternatives or examples provided for key steps such as certificate creation, AD FS management, or log inspection. All procedural instructions assume a Windows server environment and do not mention or address Linux-based AD FS alternatives or how to interact with AD FS from non-Windows systems.

Recommendations:

Provide equivalent command-line or UI instructions for managing AD FS from non-Windows environments, if possible (e.g., via REST APIs, if available).
Include examples for certificate creation and management using cross-platform tools such as OpenSSL.
Document how to interact with AD FS from Linux or macOS clients, or clarify that AD FS is a Windows-only technology if that is the case.
For PowerShell commands, suggest alternatives using cross-platform scripting or remote management tools, or note the requirement for Windows.
Where troubleshooting steps reference Windows Event Viewer, suggest how to access logs remotely or via command-line tools that may be available on other platforms.
Clearly state any platform limitations early in the documentation, and provide guidance for users on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page is largely platform-neutral in its technical content, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, it lists Windows-specific tools (Microsoft Edge or Internet Explorer developer tools) alongside browser extensions, and provides a link to a Microsoft blog post about using Edge/IE developer tools. There are no explicit Linux or cross-platform debugging tool examples given, nor is there mention of command-line tools or approaches common on Linux (such as curl, openssl, or SAML-specific CLI utilities). The order of tool presentation also puts Microsoft/Windows tools last, but their inclusion without Linux equivalents suggests a mild Windows bias.

Recommendations:

Add examples or references to Linux-compatible SAML debugging tools, such as using curl, openssl, or SAML-specific CLI tools (e.g., saml2aws, xmlsec1) for inspecting SAML messages.
Mention browser extensions as cross-platform tools more prominently, emphasizing their availability on Linux, macOS, and Windows.
If referencing developer tools for browsers, clarify that Chrome and Firefox DevTools are available on Linux and macOS as well.
Consider adding a section or note on how to capture and inspect SAML traffic using command-line tools or network analyzers (e.g., tcpdump, Wireshark) on Linux.
Avoid linking exclusively to Microsoft/Windows-specific resources for debugging; provide equivalent Linux/macOS guidance or links where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for cryptographic key and certificate generation, referencing Windows-specific tools (e.g., New-SelfSignedCertificate), and omitting equivalent Linux/macOS commands or guidance. All code snippets for key/certificate generation assume a Windows environment, and there is no mention of cross-platform alternatives or ordering that gives Linux parity.

Recommendations:

For every PowerShell example (e.g., generating a symmetric key or self-signed certificate), provide equivalent commands for Linux/macOS, such as using OpenSSL or relevant shell commands.
Explicitly mention that the steps can be performed on non-Windows platforms, and provide links or references to cross-platform tooling.
When introducing tooling or code snippets, present both Windows and Linux/macOS options together, or alternate the order to avoid always listing Windows first.
Add a section or note on cross-platform considerations, including any differences in file paths, certificate stores, or command-line utilities.
Where possible, use language-neutral or platform-neutral pseudocode for generic steps, and only provide platform-specific details as needed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily focuses on using the Azure portal, which is cross-platform, but in the section on revoking a user's session, it exclusively provides instructions and examples for Microsoft Graph PowerShell, specifically referencing 'Windows PowerShell' and omitting any Linux or cross-platform alternatives. There are no CLI, Bash, or platform-neutral examples for this task, and the language implies a Windows-first approach.

Recommendations:

Provide equivalent instructions and examples for revoking user sessions using the Microsoft Graph CLI, Azure CLI, or Bash scripts, which are cross-platform and work on Linux and macOS.
Replace references to 'Windows PowerShell' with 'PowerShell', and clarify that PowerShell Core is available on Linux and macOS, or provide explicit instructions for those platforms.
Wherever PowerShell is mentioned, add a note or section for Linux/macOS users, including any prerequisites or differences in command usage.
Consider including REST API examples (e.g., using curl) for tasks currently only shown with PowerShell, to ensure platform neutrality.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows (e.g., Visual Studio, .sln files, Web.config), omitting any mention of Linux-compatible editors, build tools, or configuration patterns. There are no Linux-specific instructions or examples, and the guidance assumes a Windows development environment.

Recommendations:

Include instructions for opening and editing the project using cross-platform editors such as VS Code or JetBrains Rider, and mention how to build and run the project using .NET CLI commands (dotnet build/run) instead of only referencing Visual Studio.
Provide examples for editing configuration files on Linux (e.g., using nano, vim, or gedit) and clarify file path differences (forward slashes vs. backslashes).
Mention how to run and debug the sample application on Linux and macOS, including any prerequisites (e.g., installing the .NET SDK on Linux).
If the sample is Windows-specific (e.g., uses Windows-only libraries), clearly state this and, if possible, provide or reference a cross-platform alternative.
Ensure that all code snippets and instructions are platform-agnostic where possible, or provide parallel instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric tool) for publishing the API, without mentioning cross-platform alternatives or providing Linux/macOS instructions. There are no command-line or non-Windows deployment examples, and the workflow assumes the user is operating in a Windows environment.

Recommendations:

Provide alternative instructions for deploying the API using cross-platform tools such as the .NET CLI (dotnet publish) and Azure CLI, which work on Linux and macOS.
Include examples or references for uploading certificates and configuring App Service settings using Azure CLI, PowerShell, and the Azure Portal, making clear which methods are cross-platform.
Explicitly state that Visual Studio is optional and provide equivalent steps for Linux/macOS users.
Review all steps for hidden Windows dependencies and ensure parity in documentation for Linux and macOS environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting any mention of Linux-based web servers (such as Apache or Nginx) as alternatives. No Linux-specific tools, commands, or deployment patterns are discussed, and all example application guidance assumes a Windows environment. There are no PowerShell commands, but the only concrete application example is Windows-centric.

Recommendations:

Include Linux-based web application examples (e.g., Apache, Nginx, or Tomcat) alongside or in place of IIS.
Provide links to documentation for setting up test applications on Linux, such as guides for deploying Apache or Nginx.
Mention that the solution is platform-agnostic and can be used with both Windows and Linux back-end applications.
Where application setup is referenced, offer both Windows and Linux instructions or note any differences.
Explicitly state that the configuration steps for F5 BIG-IP and Azure AD B2C are not limited to Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell scripts for critical steps (such as creating self-signed certificates and random keys), referencing Visual Studio for deployment, and omitting equivalent Linux/macOS commands or tooling. There are no Bash, OpenSSL, or cross-platform alternatives, which may hinder users on non-Windows systems.

Recommendations:

Provide equivalent Bash/OpenSSL commands for creating self-signed certificates and random strings, suitable for Linux/macOS users.
Include deployment instructions using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code, not just Visual Studio.
Explicitly mention that PowerShell examples are for Windows and offer alternatives for other platforms.
Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented equally, rather than Windows-first.
Add notes or links to official Microsoft documentation for cross-platform certificate and key management.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions for enabling Saviynt to delete users in Azure AD B2C. It explicitly instructs users to install the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or cross-platform examples, and the use of Windows tools and terminology is prioritized.

Recommendations:

Provide equivalent instructions using Microsoft Graph CLI (az cli or msgraph-cli), which are cross-platform and work on Linux, macOS, and Windows.
Include Bash or shell script examples for Linux users, especially for authentication and role assignment steps.
Clarify that the Microsoft Graph PowerShell module is available on non-Windows platforms via PowerShell Core, and provide installation instructions for Linux/macOS.
Avoid language that implies Windows is required (e.g., 'on a Windows workstation or server'); instead, use 'on your workstation' and specify cross-platform compatibility.
Add a section or note explicitly addressing Linux/macOS users, ensuring parity in setup and troubleshooting guidance.

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. All instructions, screenshots, and tooling references are Windows-centric, with no mention of Linux or cross-platform alternatives. There are no Linux or macOS instructions, nor are there any examples using cross-platform frameworks or tools.

Recommendations:

Provide equivalent instructions for running the sample on Linux and macOS, such as using .NET Core/MAUI or other cross-platform UI frameworks.
Include examples for building and running the application using command-line tools (dotnet CLI) instead of only Visual Studio.
Mention and provide guidance for alternative editors (e.g., VS Code) and package management approaches that work on Linux.
Add screenshots and workflow steps for Linux/macOS environments.
Clarify in the prerequisites and introduction whether the sample is Windows-only, and if so, provide or link to cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a primarily Windows IDE) and providing instructions that assume the use of Windows-specific tools and workflows (such as Solution Explorer, right-click context menus, and F5 debugging). There are no examples or guidance for running or developing the sample application on Linux or using cross-platform tools like VS Code or the .NET CLI.

Recommendations:

Add instructions for running the sample using the .NET CLI (dotnet build/run) to support Linux and macOS users.
Include examples for setting up and debugging the application in Visual Studio Code, which is cross-platform.
Mention alternative editors and workflows for non-Windows environments, such as JetBrains Rider or command-line tools.
Clarify which steps are specific to Visual Studio on Windows and provide equivalent steps for Linux/macOS where possible.
Explicitly state the platform requirements and provide links to cross-platform .NET documentation.

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 it explicitly recommends using Azure Key Vault or a PowerShell module for creating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) for certificate generation. The only scripting tool mentioned for local certificate creation is PowerShell, which is Windows-centric. No Linux or macOS equivalents are referenced, and no cross-platform CLI instructions are provided for key tasks like certificate generation.

Recommendations:

Add Linux/macOS-friendly instructions for generating self-signed certificates, such as using OpenSSL, alongside or before PowerShell examples.
Explicitly mention that certificate generation can be performed on any OS and provide cross-platform command-line examples.
Where PowerShell is referenced, offer equivalent bash or shell commands for Linux/macOS users.
Review other sections for any implicit Windows-first assumptions and ensure parity in tool recommendations and example commands.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation provides only a PowerShell script for monitoring directory quota, with no equivalent example or guidance for Linux or cross-platform environments. It assumes the use of Windows tools and patterns (PowerShell, Invoke-RestMethod), and does not mention or prioritize Linux-compatible alternatives such as Bash, curl, or Python. This creates a Windows-first experience and excludes users on Linux or macOS.

Recommendations:

Provide a Bash or shell script example using curl or httpie to demonstrate how to perform the same API calls on Linux/macOS.
Include a cross-platform example using a language like Python, which is available on both Windows and Linux.
Explicitly mention that the PowerShell script is for Windows, and direct Linux/macOS users to equivalent instructions.
Consider reordering the examples or providing both Windows and Linux/macOS options side-by-side to ensure parity.
Reference platform-agnostic tools (e.g., Azure CLI, Microsoft Graph CLI) if available, or provide links to relevant documentation 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 users (e.g., Bash/cURL). The script assumes use of PowerShell, which is traditionally a Windows tool, and there is no mention of Linux-native tools or cross-platform alternatives. This may disadvantage users on Linux or macOS platforms.

Recommendations:

Add a Bash/cURL example for querying the Microsoft Graph API to retrieve audit logs, demonstrating how to authenticate and paginate results.
Explicitly mention that PowerShell Core is cross-platform and can be used on Linux/macOS, or provide installation instructions for non-Windows users.
Where possible, provide both Windows (PowerShell) and Linux (Bash/cURL or Python) script examples side by side.
Reference Linux-native tools (e.g., jq for JSON processing) in the context of handling API responses.
Clarify in the documentation that the API can be accessed from any platform, not just Windows, and provide guidance for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. While it claims that Azure CLI command examples can run in both PowerShell and bash, the only explicit command example is given in a generic CLI format without showing both PowerShell and bash syntax where they might differ. There is mention that separate examples are provided 'where needed,' but no Linux-specific (bash) example is actually shown. The documentation also references running CLI commands in PowerShell first, and the prerequisite section for Azure CLI setup is ambiguous about Linux-specific steps or differences.

Recommendations:

Provide explicit bash/Linux command examples alongside PowerShell examples wherever variable syntax or command usage differs.
Ensure that CLI setup instructions include Linux-specific prerequisites and installation steps, not just generic or Windows-focused guidance.
If referencing the ability to use both PowerShell and bash, demonstrate this parity by including both sets of examples where relevant.
Avoid language that defaults to Windows-first (e.g., mentioning PowerShell before bash), or alternate the order to show neutrality.
Include troubleshooting or environment notes for Linux users, such as common issues with Azure CLI on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral, focusing on HTTP requests and OAuth 2.0 protocol details. However, there is a subtle Windows bias in the section suggesting 'Microsoft PowerShell' as an example HTTP client for testing POST requests, without mentioning Linux or cross-platform alternatives. No Linux-specific tools (such as curl or httpie) are referenced, and no Linux command-line examples are provided.

Recommendations:

When suggesting tools for testing HTTP requests, mention cross-platform and Linux-native tools such as 'curl' or 'httpie' alongside PowerShell.
Provide example commands using 'curl' or 'httpie' for Linux/macOS users in addition to any PowerShell examples.
Explicitly state that any HTTP client can be used, and offer at least one example for both Windows and Linux environments.
Review other documentation pages for similar subtle tool recommendations and ensure Linux parity throughout.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates mild Windows bias. While it provides separate command examples for Linux, macOS, and Windows when running the sample app, there are subtle indications of Windows-first thinking. Notably, the instruction to 'Extract the sample file to a folder where the total length of the path is 260 or fewer characters' references the Windows MAX_PATH limitation, which is not relevant to Linux/macOS. Additionally, the Windows example uses 'py' instead of 'python', which is a Windows-specific launcher. However, the documentation does provide parity in command examples for all platforms and does not omit Linux/macOS instructions.

Recommendations:

Clarify that the 260-character path length limitation applies only to Windows, and that Linux/macOS users are not affected.
Consider listing Linux/macOS examples before Windows, or in parallel, to avoid a Windows-first impression.
Where possible, use cross-platform commands (e.g., 'python' instead of 'py') in generic instructions, and explain platform-specific differences in a note.
Review the documentation for any other implicit Windows assumptions (such as file path separators, environment variable syntax, etc.) and clarify or provide Linux/macOS equivalents as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by focusing exclusively on ASP.NET (a Microsoft technology) and development environments like Visual Studio and Visual Studio Code, but does not provide explicit instructions or examples for Linux users. There are no references to Linux-specific tools, shell commands, or deployment considerations, and the prerequisites and steps assume a Windows-centric workflow.

Recommendations:

Include explicit instructions for running the sample on Linux, such as using the .NET CLI (dotnet run) in a terminal.
Provide Linux-specific prerequisites, such as installation steps for .NET SDK on Ubuntu or other distributions.
Mention and show examples of using editors and tools common on Linux (e.g., JetBrains Rider, Vim, or Emacs) in addition to Visual Studio and VS Code.
Clarify that Visual Studio Code and the .NET SDK are cross-platform, and provide any necessary Linux-specific configuration notes (e.g., HTTPS development certificates).
Add troubleshooting tips for common Linux issues, such as file permissions or path length differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on ASP.NET Core development, which is cross-platform, but the examples and instructions implicitly assume a Windows development environment. There are no explicit Linux or macOS instructions, and the tooling references (such as Visual Studio and Visual Studio Code) are presented in a way that prioritizes Windows workflows. Package installation commands for Visual Studio Code use Install-Package, which is a PowerShell/NuGet Package Manager Console command, not a cross-platform dotnet CLI command. There are no mentions of Linux-specific considerations, file paths, or development environments.

Recommendations:

Provide explicit instructions and examples for Linux and macOS environments, including terminal commands and any OS-specific prerequisites.
Use cross-platform commands (such as 'dotnet add package') consistently in all tooling sections, especially for Visual Studio Code, which is widely used on Linux/macOS.
Mention and show file paths in both Windows (\) and Unix (/) formats where relevant.
Include a note or section on running and debugging the application on Linux/macOS, including any differences in launching the development server or accessing localhost.
Clarify that ASP.NET Core and the Microsoft Identity Web libraries are fully supported on Linux and macOS, and provide links to relevant cross-platform documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is focused exclusively on ASP.NET Core web apps, which are cross-platform, but the only development environments mentioned are Visual Studio and Visual Studio Code. The package installation instructions are split between 'Visual Studio' (using dotnet CLI) and 'Visual Studio Code' (using Install-Package), but both are available cross-platform. However, there are no explicit instructions or examples for Linux or macOS users, such as using terminal/bash, nor is there any mention of Linux-specific tooling or considerations. The documentation implicitly assumes a Windows-centric development environment by referencing Visual Studio and Windows-style file paths (e.g., Views\Shared\_Layout.cshtml).

Recommendations:

Add explicit instructions or notes for Linux and macOS users, including any differences in file paths, commands, or environment setup.
Include examples using bash or terminal commands for package installation and project creation, not just Visual Studio/Visual Studio Code.
Mention cross-platform compatibility of ASP.NET Core and clarify that all steps can be performed on Linux/macOS as well as Windows.
Use platform-neutral file path notation (e.g., Views/Shared/_Layout.cshtml) throughout the documentation.
If referencing IDEs, include cross-platform options such as JetBrains Rider or command-line editors (vim, nano) alongside Visual Studio and Visual Studio Code.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on ASP.NET Core and C# development patterns, which are traditionally associated with Windows environments. There are no explicit instructions, examples, or notes for Linux or cross-platform development, and all file references and code samples (e.g., Startup.cs, appsettings.json) assume a .NET/Windows-centric workflow. There is no mention of Linux-specific tools, deployment, or configuration steps.

Recommendations:

Add explicit notes or sections clarifying that ASP.NET Core is cross-platform and can be developed and deployed on Linux and macOS, not just Windows.
Include Linux/macOS equivalents for file paths, command-line instructions, and environment setup (e.g., using bash instead of PowerShell, using environment variables in Linux).
Provide examples or links for deploying and running ASP.NET Core applications on Linux (e.g., using systemd, Nginx/Apache reverse proxy).
Mention cross-platform development tools (e.g., Visual Studio Code, JetBrains Rider) in addition to Visual Studio.
If referencing Windows-specific tools or patterns, ensure Linux alternatives are mentioned with equal prominence.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively describes steps using the Azure portal web interface and does not provide any command-line examples. There is no mention of platform-specific tools, but where command-line or automation might be relevant (e.g., scripting registration or configuration), no examples are given for either Windows (PowerShell) or Linux (CLI). However, the overall workflow and terminology (e.g., 'click', 'select', 'portal') are more familiar to users of Windows environments and Azure's web UI, which is often associated with Windows-centric workflows. There is no mention of Azure CLI or cross-platform automation, and no Linux-specific guidance or parity.

Recommendations:

Provide Azure CLI examples for all steps that can be automated, including application registration, client secret creation, and identity provider configuration.
Explicitly mention that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
Where possible, include both GUI and CLI instructions side-by-side, so Linux and automation-focused users are equally supported.
Reference documentation for scripting or automating these tasks on Linux/macOS as well as Windows.
If PowerShell or Windows tools are ever referenced, ensure equivalent Bash/Azure CLI examples are provided.

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 the use of the Azure portal, terminal, or command prompt without explicitly referencing Linux or cross-platform alternatives. There are no explicit Linux-specific instructions, examples, or screenshots, and no mention of Linux-native tools or shell environments. All environment variable and deployment steps are described generically or with a Windows-centric perspective, omitting Linux-specific guidance.

Recommendations:

Explicitly mention that Visual Studio Code and Azure Functions Core Tools are cross-platform and provide installation links for Linux and macOS.
Include Linux-specific instructions or examples for running and deploying Azure Functions, such as using bash/zsh shells and common Linux package managers.
Show how to set environment variables in Linux (e.g., export commands or .env files) in addition to the local.settings.json approach.
Add screenshots or terminal snippets from Linux environments to demonstrate parity.
Clarify that the Azure portal and related tools are accessible from any OS, and provide links to CLI-based alternatives (e.g., Azure CLI) with Linux usage examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by specifically mentioning Windows Hello as the primary example of biometric authentication, both in the introduction and in the scenario walkthrough. Windows Hello is referenced before any mention of Android or other platforms, and no Linux or cross-platform biometric solutions are discussed. There are no Linux-specific examples or references to Linux-compatible biometric tools.

Recommendations:

Include explicit references to biometric authentication options available on Linux (e.g., fprintd, libfprint, or desktop environment integrations) alongside Windows Hello and Android.
Provide example scenarios or walkthroughs for enrolling and using biometrics on Linux devices, not just Windows and Android.
Use neutral, platform-agnostic language when describing biometric authentication, mentioning Windows Hello, Android biometrics, and Linux solutions together.
If possible, add troubleshooting or support notes for Linux users to ensure parity with Windows and Android guidance.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by referencing Visual Studio as the publishing tool for the API and suggesting Azure Storage Explorer for managing Azure storage, both of which are traditionally Windows-centric tools. No Linux-specific tools or cross-platform alternatives are mentioned, and there are no command-line examples (e.g., Azure CLI, PowerShell, Bash) for Linux users. The documentation does not provide explicit instructions or examples for Linux environments.

Recommendations:

Include instructions for deploying the API using cross-platform tools such as the Azure CLI, .NET CLI, or GitHub Actions, in addition to Visual Studio.
Mention and provide examples for using Azure Storage Explorer on Linux, or suggest alternative methods such as the Azure CLI or azcopy for uploading files to blob storage.
Add command-line examples for common tasks (e.g., uploading files, configuring CORS) using tools available on Linux.
Explicitly state that the steps can be performed on Linux, macOS, or Windows, and highlight any platform-specific considerations.
Where GUI tools are referenced, provide equivalent command-line or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page shows mild Windows bias by referencing 'windows' explicitly in the SAML application registration link (saml-service-provider.md?tabs=windows), suggesting that Windows is the default or primary environment. There are no explicit Linux or cross-platform examples or tabs mentioned, and no Linux-specific tools or instructions are provided.

Recommendations:

Wherever platform-specific instructions or tabs are provided (such as for SAML apps), ensure that Linux (and macOS, if relevant) tabs/examples are available and mentioned equally.
Avoid using Windows as the default or only tab in links; instead, provide a neutral or cross-platform default, or mention all supported platforms.
Explicitly state when instructions are cross-platform, or provide clear guidance for both Windows and Linux users.
Review linked tutorials to ensure parity in examples, screenshots, and command-line instructions for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes management tasks using the Azure Portal web interface, with no mention of command-line tools or automation. However, where command-line or scripting might be relevant (e.g., bulk user creation, role assignment, or auditing), there are no examples for PowerShell, CLI, or any platform-specific tools. The only interface described is the Azure Portal, which is cross-platform via browser, but the documentation implicitly assumes a GUI-first, Windows-centric workflow by not mentioning or providing parity for Linux or cross-platform automation tools (such as Azure CLI or REST API). There are no explicit Windows-only tools, but the lack of CLI or automation examples can disadvantage Linux users who may prefer or require non-GUI workflows.

Recommendations:

Add examples using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
Where appropriate, provide PowerShell examples alongside Azure CLI, but do not make PowerShell the only automation example.
Include REST API references or examples for tasks that can be automated, to support users on any platform.
Explicitly mention that all tasks can be performed via browser on any OS, but also provide links or examples for automation and scripting.
For bulk operations (e.g., user creation), provide sample scripts or commands for both Azure CLI and PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both bash and PowerShell syntax for Azure CLI commands, but consistently lists bash first and PowerShell second. While this is a positive step toward cross-platform parity, the explicit labeling of 'PowerShell syntax' and the inclusion of both syntaxes in every example may subtly reinforce a Windows-centric perspective. There are no Linux-specific tools, editors, or workflows mentioned, and the only editor referenced is Visual Studio Code, which is cross-platform but often associated with Windows. No explicit Linux bias or missing Linux examples are present, but the documentation could do more to highlight Linux-native workflows or tools.

Recommendations:

Explicitly mention that all CLI examples work on Linux, macOS, and Windows, and consider alternating the order of bash and PowerShell examples to avoid implicit prioritization.
Include references to Linux-native editors (e.g., Vim, Emacs) or terminal workflows where appropriate, or at least acknowledge their use.
Add a short section or note confirming that all steps are fully supported on Linux and macOS, not just Windows.
If possible, provide a sample workflow or screenshot from a Linux environment to visually reinforce parity.
Avoid over-emphasizing PowerShell by only including it where syntax differences are significant, and otherwise default to bash for cross-platform clarity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled and formatted explicitly, suggesting a Windows-centric approach. The PowerShell examples are always presented immediately after the Bash examples, indicating a slight 'windows_first' bias. There are no missing Linux examples, but the explicit PowerShell formatting and comments may make Windows users feel more directly supported.

Recommendations:

Clearly label both Bash and PowerShell examples as 'Linux/macOS' and 'Windows' respectively to highlight cross-platform parity.
Present Bash (Linux/macOS) and PowerShell (Windows) examples in parallel tabs or sections, rather than always listing PowerShell after Bash.
Ensure that introductory text does not implicitly prioritize Windows or PowerShell usage.
Consider adding a brief note explaining that Azure CLI works identically on all platforms, and that users should choose the example matching their shell environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. There is no explicit mention of Linux or macOS, and the PowerShell examples may suggest a Windows-first or Windows-heavy audience. However, Linux users are supported via Bash examples, and no Windows-only tools are referenced.

Recommendations:

Explicitly label Bash examples as suitable for Linux/macOS and PowerShell examples as suitable for Windows to clarify cross-platform applicability.
Present Bash (Linux/macOS) and PowerShell (Windows) examples in parallel tabs or sections, rather than always listing Bash first, to avoid implicit prioritization.
Add a short note at the top of the CLI section explaining that both Linux/macOS (Bash) and Windows (PowerShell) users are supported, and how to choose the appropriate example.
Ensure that any platform-specific nuances (such as line continuation characters or variable assignment syntax) are briefly explained for both environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and mentions it before providing any Linux-specific alternatives or examples. There are no explicit Linux examples or mentions of Linux-native tools, which may suggest a subtle Windows bias.

Recommendations:

Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Provide example commands for both Azure CLI and Azure PowerShell, making clear which are suitable for Linux users.
If referencing PowerShell, clarify that PowerShell Core is available cross-platform, or provide Bash shell equivalents.
Consider listing Azure CLI before Azure PowerShell to avoid the impression of Windows-first bias.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively provides instructions using the Azure portal UI, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform tooling. This may disadvantage users who prefer or require automation or command-line approaches, especially on Linux or macOS.

Recommendations:

Add equivalent Azure CLI examples for enabling managed identities and assigning roles, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that the Azure portal can be accessed from any OS, not just Windows.
Provide PowerShell and Bash script examples where appropriate, ensuring parity between Windows and Linux instructions.
Include a section or links for automating these steps using command-line tools for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Visual Studio Code and its Azure API Center extension as prerequisites, which are available cross-platform. However, it only mentions the Visual Studio Code Marketplace link (which is Windows-centric by default) and does not clarify Linux installation steps or alternative editors. There are no explicit Linux examples or mentions of Linux-specific tools or workflows.

Recommendations:

Explicitly mention that Visual Studio Code and the Azure API Center extension are available on Linux and macOS, not just Windows.
Provide installation instructions or links for Visual Studio Code and the extension for Linux users.
If relevant, mention alternative editors or CLI tools that can be used on Linux.
Ensure that all steps and screenshots (if any) are not Windows-specific, or provide Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is not clearly marked as Windows-only. There are no explicit Linux shell (bash) examples, and the PowerShell section may suggest a Windows-first or Windows-heavy approach. However, Azure CLI is cross-platform and is presented first, which helps mitigate bias.

Recommendations:

Clearly indicate that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for cross-platform (Linux, macOS, Windows) environments.
Add explicit bash shell examples (if any commands differ from Azure CLI usage on Windows) to demonstrate Linux parity.
In prerequisite sections, clarify which tools are cross-platform and which are Windows-specific.
Consider providing a table or callout summarizing which deployment tools are best suited for each OS.
If possible, include links or references to Linux-specific guidance for ARM template deployment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively describes how to create an Azure API center using the Azure portal, which is a web-based interface accessible from any OS. However, it omits any command-line instructions (such as Azure CLI or PowerShell), and does not provide Linux-specific or cross-platform examples. If command-line registration or automation is common, the lack of Azure CLI (which is cross-platform) examples may implicitly favor Windows users, as PowerShell is often the default scripting tool in Azure documentation.

Recommendations:

Add Azure CLI examples for registering the Microsoft.ApiCenter provider and creating an API center, as the CLI is cross-platform and widely used on Linux.
If PowerShell examples are provided elsewhere, ensure Azure CLI equivalents are always included and presented with equal prominence.
Explicitly mention that the Azure portal is web-based and accessible from any OS to avoid the impression of Windows bias.
Include links or references to documentation for performing the same tasks via CLI or automation tools, which are popular among Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure Portal, Logic Apps, and Microsoft Teams for workflow automation, all of which are primarily Microsoft/Windows-centric tools. There are no examples or mentions of Linux-native tools, CLI-based automation, or cross-platform notification systems such as Slack or open-source alternatives. The workflow is tightly coupled with the Azure Portal UI and Microsoft Teams, with no guidance for users who may prefer or require Linux-based or open-source solutions.

Recommendations:

Provide equivalent automation steps using Azure CLI and/or Azure PowerShell, and clarify their cross-platform compatibility.
Include examples or references for integrating with non-Microsoft notification systems (e.g., Slack, Mattermost, email via SMTP) to broaden applicability.
Offer guidance for setting up similar workflows using open-source automation tools (such as Apache Airflow, Jenkins, or custom scripts) that can run on Linux.
Explicitly mention that Logic Apps and Teams are not required, and suggest alternatives for organizations using Linux or non-Microsoft collaboration tools.
Add a section or appendix with Linux-first or cross-platform automation patterns, including sample scripts and configuration steps.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation contains a subtle Windows bias by linking to further instructions for securing REST APIs with a URL that explicitly includes a 'tabs=windows' query parameter. This suggests that the default or primary guidance is for Windows environments, with no mention or example for Linux or cross-platform scenarios. No PowerShell-specific commands or Windows-only tools are present, but the reference to Windows-first documentation may disadvantage Linux users.

Recommendations:

Provide explicit Linux (and macOS) instructions or links alongside Windows instructions for securing REST APIs and obtaining tokens.
Use neutral or cross-platform documentation links (e.g., avoid hardcoding 'tabs=windows' in URLs) or clearly indicate how to switch to Linux/macOS tabs.
Wherever platform-specific steps are referenced, include a note or table summarizing differences and parity between Windows and Linux environments.
Audit linked documentation to ensure Linux users are not left without equivalent guidance.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation demonstrates a mild 'windows_first' bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) equivalent, but there is no explicit mention of Linux or macOS. The rest of the documentation is platform-agnostic, focusing on Android Studio and Java/Kotlin code, with no other Windows-specific tools or patterns.

Recommendations:

Explicitly mention Linux/macOS alongside iOS in the signature hash generation step, as the command is the same for all Unix-like systems.
Label the command as 'For Linux/macOS' instead of 'For iOS', or use 'For Linux/macOS/iOS' to be inclusive.
Consider presenting both Windows and Linux/macOS commands together, or in parallel tabs, to avoid implying Windows is the primary or default environment.
Review other documentation pages for similar patterns and ensure parity in platform instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not exhibit explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it exclusively describes GUI-based steps using the Azure portal and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell) for registering applications or granting permissions. This omission results in a lack of parity for Linux or cross-platform users who may prefer or require CLI-based automation.

Recommendations:

Add Azure CLI examples for all major steps (registering the application, granting permissions, assigning roles, creating client secrets) alongside the portal instructions.
Explicitly mention that all operations can be performed via CLI and provide links to relevant Azure CLI documentation.
If PowerShell examples are added, ensure equivalent Azure CLI (Bash-friendly) examples are also present and given equal prominence.
Consider including a table or section comparing portal, Azure CLI, and PowerShell approaches for each task to support all user environments.

Create pull request

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