Scan Details - Linux-first Docs for Azure

269

Pages Scanned

33

Pages Flagged

269

Changed Pages

12.3%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

00:00:55 Scan started

Scan Information

Started At: 2025-08-13 00:00:55

Finished At: In Progress

Status: in_progress

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. It references PowerShell for generating GUIDs and provides a PowerShell script as the first scripting example for obtaining tokens. The mention of PowerShell and Microsoft tools precedes alternatives, and no explicit Linux or cross-platform command-line alternatives are given for all steps (e.g., GUID generation). While a cURL example is provided, the overall pattern puts Windows-centric tools and workflows first.

Recommendations:

When instructing users to generate a GUID, provide a cross-platform alternative (e.g., 'uuidgen' for Linux/macOS) alongside PowerShell.
Present scripting examples in a neutral order or offer both PowerShell and Bash/cURL examples together, clarifying their platform compatibility.
Avoid referencing Microsoft/Windows tools exclusively; always mention or link to Linux/macOS equivalents where relevant.
Explicitly state that steps can be performed on any OS, and provide guidance for users on Linux/macOS for all command-line operations.

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. There are no Linux or cross-platform equivalents mentioned, nor are there instructions or examples for developing, building, or running the sample on Linux or macOS. All tooling and code samples are Windows-specific, and the documentation assumes a Windows development environment throughout.

Recommendations:

Add a section describing how to build and run a similar desktop application using cross-platform frameworks such as .NET MAUI or Avalonia, which support Linux and macOS.
Provide instructions for setting up the development environment on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI) and for restoring NuGet packages and building the project via command line.
Include examples or notes on how to adapt the authentication flow for non-Windows platforms, highlighting any differences in browser invocation or redirect URI handling.
Clarify in the prerequisites and introduction that the guide is Windows-specific, and link to cross-platform alternatives if available.
Offer sample code or links for equivalent authentication flows in Linux-friendly desktop frameworks.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias toward Windows environments by providing only PowerShell examples for testing the REST API, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). The only tool-specific guidance for making HTTP requests is for PowerShell, a Windows-centric tool, and it is mentioned before any cross-platform alternatives. No Linux or macOS-specific instructions or examples are given for testing the Node.js app locally or after deployment.

Recommendations:

Provide equivalent Linux/macOS command-line examples using curl or httpie alongside the PowerShell example for making HTTP requests to the REST API.
When referencing tools, mention cross-platform options (e.g., curl, Postman, httpie) before or alongside Windows-specific tools like PowerShell.
Explicitly state that the Node.js app and instructions are cross-platform, and clarify that all steps can be performed on Linux, macOS, or Windows.
Add a note or section for Linux/macOS users, including terminal commands and any environment-specific considerations.
Where possible, use neutral language (e.g., 'terminal' instead of 'PowerShell') and avoid assuming the user is on Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies, with no mention of Bash, shell, or cross-platform scripting alternatives. All code samples and pipeline task instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for Linux or macOS users. The documentation does not address how to adapt the process for non-Windows agents or provide equivalent examples using other scripting languages or tools.

Recommendations:

Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
Mention that PowerShell Core is cross-platform and clarify if the provided script is compatible with PowerShell Core on Linux/macOS.
Include instructions for running the deployment script on Linux-based Azure Pipeline agents, including any prerequisites (e.g., installing PowerShell Core).
Offer guidance or templates for using other common CI/CD scripting languages (e.g., Python) if possible.
Explicitly state platform requirements and provide troubleshooting tips for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the 'Run your SPA application' section, where only PowerShell commands are shown for running the app (e.g., 'npm install', 'npm ./index.js'), and no Linux/macOS shell equivalents are provided. Throughout the rest of the document, instructions are generally cross-platform, but the explicit use of PowerShell syntax and lack of Linux-specific notes or examples may confuse or exclude non-Windows users.

Recommendations:

Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples wherever commands are shown, especially in the 'Run your SPA application' section.
Use neutral, cross-platform terminology such as 'terminal' or 'command line' instead of 'command shell', and clarify that the instructions apply to all major operating systems.
Where file paths or commands may differ between platforms, explicitly note the differences or provide side-by-side examples.
Test and document the startup commands for Linux/macOS (e.g., 'node index.js' instead of 'npm ./index.js', which is not standard on any platform).
Consider adding a prerequisites note confirming that the instructions are valid for Windows, Linux, and macOS, and link to platform-specific Node.js installation guides if appropriate.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of Windows-based AD FS management tools (Server Manager, AD FS Management console) and provides only GUI-based instructions specific to Windows environments. There are no Linux or cross-platform command-line alternatives, nor any mention of how to perform equivalent steps on non-Windows systems. The documentation also references Windows-specific endpoints and concepts before any mention of general OpenID Connect standards.

Recommendations:

Provide PowerShell and command-line alternatives for AD FS configuration, and clarify if these can be run on non-Windows platforms (e.g., via Windows Admin Center, remote management, or cross-platform tools).
Explicitly state that AD FS is a Windows Server role and clarify any platform limitations early in the prerequisites.
If possible, mention or link to open-source or Linux-compatible alternatives to AD FS for OpenID Connect integration.
Add a note or section explaining that the described steps require access to a Windows Server environment, and offer guidance for users working in mixed or non-Windows environments.
Where possible, use OpenID Connect terminology and standards first, then describe how AD FS implements them, to reduce Windows-centric framing.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page is generally 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) and provides a link to a Microsoft blog post about using these tools, while only briefly mentioning browser extensions for Chrome and Firefox. There are no Linux-specific tools or command-line approaches mentioned, and no PowerShell or Windows command-line examples are present, but the tool recommendations and order of mention show a subtle Windows bias.

Recommendations:

Include Linux-friendly SAML debugging tools, such as command-line utilities (e.g., curl, openssl, xmlsec1) or Linux-compatible browser extensions.
List browser-agnostic tools and extensions first, and group them by browser/platform rather than mentioning Microsoft tools last.
If referencing developer tools, clarify that Chrome and Firefox developer tools are also available on Linux and macOS, and provide equivalent instructions or links.
Consider adding a section or note on how to capture and analyze SAML traffic using cross-platform tools like Wireshark or Fiddler Everywhere.
Avoid linking only to Microsoft/Windows-specific blog posts; provide or link to platform-neutral guidance where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a clear Windows bias by providing only PowerShell examples for key generation and certificate creation, referencing Windows-specific tools (e.g., PowerShell's New-SelfSignedCertificate), and omitting equivalent Linux/macOS commands or guidance. All code samples for cryptographic operations are Windows-centric, and there is no mention of cross-platform alternatives or parity for non-Windows environments.

Recommendations:

For every PowerShell or Windows-specific example, provide equivalent Linux/macOS commands (e.g., using OpenSSL for key and certificate generation).
Explicitly mention that the steps can be performed on Linux/macOS and provide sample shell commands.
Reference cross-platform tools (such as OpenSSL, or .NET CLI commands) alongside Windows tools.
Reorder sections or add notes to avoid implying Windows is the default or only supported environment.
Link to external documentation for Linux/macOS cryptographic operations where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. While it covers a broad range of platforms (iOS, Android, Node.js, Python), .NET and Windows desktop samples are given prominence, with a dedicated sample for Windows Desktop (.NET WPF) but no equivalent Linux desktop application. The .NET samples implicitly target Windows environments, and there is no mention of Linux-specific tools or desktop frameworks. Additionally, the only desktop app sample is for Windows, with no parity for Linux desktop environments.

Recommendations:

Add Linux desktop application samples (e.g., using .NET MAUI, GTK#, or Electron) to provide parity with the Windows desktop sample.
Explicitly mention cross-platform compatibility for .NET samples, and provide instructions or notes for running them on Linux (e.g., using .NET Core on Linux).
Where desktop or console samples are provided, clarify if they are cross-platform or provide Linux-specific instructions and troubleshooting.
Consider including examples or references for common Linux development environments and tools where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page is generally platform-neutral when describing Azure portal operations, but introduces Windows bias in the section on revoking user sessions. Only Microsoft Graph PowerShell is mentioned, with explicit references to 'Windows PowerShell' and no mention of Linux/macOS equivalents or cross-platform instructions. There are no CLI or bash examples, and PowerShell is presented as the primary (and only) scripting tool, which may exclude Linux users.

Recommendations:

Explicitly state that Microsoft Graph PowerShell is cross-platform and can be used on Windows, Linux, and macOS.
Replace references to 'Windows PowerShell' with 'PowerShell', or clarify that the instructions apply to all supported platforms.
Provide equivalent examples using Azure CLI, Bash, or direct Microsoft Graph API calls via curl or httpie for Linux/macOS users.
Add a note or section for Linux/macOS users, outlining any prerequisites or differences in running PowerShell or using alternative tools.
Ensure that scripting and automation examples are not Windows-centric, and that parity is maintained for all major operating systems.

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, .sln files, and Web.config (XML), which are Windows-centric tools and patterns. There are no examples or instructions for Linux or cross-platform development environments (e.g., VS Code, command-line builds, or configuration via appsettings.json). The documentation assumes the reader is using Windows and does not mention Linux equivalents or alternatives.

Recommendations:

Include instructions for opening and editing the project using cross-platform tools such as VS Code or JetBrains Rider.
Provide examples for configuring the application using appsettings.json or environment variables, which are commonly used in Linux and containerized environments.
Add guidance for building and running the sample using the .NET CLI (dotnet build/run) instead of relying solely on Visual Studio.
Mention how to locate and edit configuration files on Linux systems, and clarify any OS-specific paths or commands.
Ensure that any screenshots or UI references (e.g., Azure portal) are not Windows-specific, or provide notes for Linux/macOS users if differences exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools and workflows (such as ASP.NET MVC, OWIN middleware, and .NET code samples) without providing equivalent Linux or cross-platform examples. Certificate management and application examples are also Windows-centric, and there is a lack of guidance for Linux-based environments or tools.

Recommendations:

Provide Linux-based or cross-platform examples for application integration, such as using Java (Spring), Python (Flask/Django), or Node.js for OIDC/SAML flows.
Include instructions for certificate generation and management using Linux tools (e.g., OpenSSL) alongside or instead of Windows-specific instructions.
Offer sample configurations and code snippets for popular Linux web servers (e.g., Apache, Nginx) and application frameworks.
Reference cross-platform tools and avoid assuming the use of Windows-only technologies (such as OWIN or ASP.NET MVC) as the default.
Where application examples are given (e.g., header-demo-app), provide deployment and testing steps for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by only referencing Visual Studio (a Windows-centric tool) for publishing code and omitting any Linux/macOS deployment or configuration examples. There are no CLI, VS Code, or cross-platform instructions, and the workflow assumes use of Windows-based tooling and patterns.

Recommendations:

Provide alternative instructions for deploying the API using cross-platform tools such as Azure CLI, Azure DevOps, or GitHub Actions, which work on Linux and macOS.
Include examples for publishing the code from VS Code or command-line interfaces (dotnet CLI), not just Visual Studio.
Explicitly mention that the deployment and configuration steps can be performed from Linux/macOS environments and provide relevant guidance.
Ensure that any references to uploading certificates or configuring app settings in Azure App Service include both portal and CLI/PowerShell methods, with parity for Linux users.

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 or example of Linux-based web servers (such as Apache or Nginx). There are no Linux-specific instructions, tools, or examples, and the only application setup guidance is for a Windows environment.

Recommendations:

Add parallel instructions and examples for deploying and testing with a Linux-based web server (e.g., Apache, Nginx) alongside the IIS example.
Provide links to official documentation for setting up common Linux web servers.
Explicitly mention that the solution is platform-agnostic and can be used with both Windows and Linux applications.
Include troubleshooting tips relevant to Linux environments.
Balance references to Windows tools (like IIS) with Linux equivalents to ensure parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows Hello as the primary example of biometric authentication, both in the introductory explanation and the scenario walkthrough. There is no mention of Linux or macOS biometric solutions, nor are there examples or guidance for users on those platforms. The documentation assumes familiarity with Windows-specific tools and does not provide parity for Linux users.

Recommendations:

Include examples and references to biometric authentication solutions available on Linux (e.g., fprintd, fingerprint-gui) and macOS (e.g., Touch ID).
When describing scenarios, provide equal detail for non-Windows platforms, such as how enrollment and authentication would work on Linux or macOS devices.
Avoid using Windows Hello as the default or only example; instead, mention it alongside other platform-specific solutions.
Add troubleshooting or setup notes for Linux users who may need to configure biometric hardware or software.
Explicitly state platform requirements and provide links to relevant documentation for biometric setup on all major operating systems.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by referencing Visual Studio (a Windows-centric tool) as the primary publishing method for the API, without mentioning cross-platform or Linux alternatives. There are no examples or instructions for deploying the API from Linux or using non-Windows tools, and the only deployment instructions link to Visual Studio documentation. This may create the impression that the integration is best or only supported on Windows environments.

Recommendations:

Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, which can be run from Linux, macOS, or Windows.
Include examples for deploying the API using the 'dotnet publish' and 'az webapp deploy' commands, which are platform-agnostic.
Explicitly mention that the API can be deployed from any OS, and provide links to documentation for Linux/macOS users.
Avoid referencing only Windows-specific tools (like Visual Studio) as the primary or sole method for deployment.
Add a note or section for Linux/macOS users to ensure parity and inclusivity.

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 generating certificates and random keys, with no equivalent Linux or cross-platform instructions. The use of PowerShell and references to Visual Studio for deployment further reinforce a Windows-centric approach, while omitting guidance for users on Linux or macOS platforms.

Recommendations:

Provide equivalent Bash or 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, VS Code, or GitHub Actions, not just Visual Studio.
Explicitly mention that the PowerShell examples are for Windows and offer alternative steps for other operating systems.
Add notes or links to official Microsoft documentation on performing these tasks on Linux/macOS.
Ensure that all code snippets and instructions are platform-agnostic where possible, or present both Windows and Linux/macOS options side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation shows a Windows bias by referencing Visual Studio as the publishing tool for the API, mentioning Azure Storage Explorer (a Windows-centric tool) for managing Azure storage, and omitting any Linux/macOS-specific instructions or alternatives. There are no CLI, PowerShell, or Bash examples, but the only tooling guidance assumes a Windows environment. No Linux or cross-platform deployment or file upload methods are described.

Recommendations:

Include instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, not just Visual Studio.
Provide alternative methods for uploading and managing files in Azure Storage, such as using the Azure CLI (az storage blob upload), AzCopy, or REST API, alongside Azure Storage Explorer.
Explicitly mention that the steps can be performed from Linux/macOS environments and provide any necessary command-line examples.
If referencing GUI tools like Visual Studio or Storage Explorer, also link to or describe equivalent steps using cross-platform or Linux-native tools.
Add notes or sections for developers working on non-Windows platforms to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell-based instructions for enabling Saviynt to delete users, explicitly stating the need for a 'Windows workstation or server' and referencing the Microsoft Graph PowerShell module. There are no equivalent instructions or examples for Linux or cross-platform environments (e.g., using Azure CLI, Bash, or REST API). This may hinder users on non-Windows systems from following the guide effectively.

Recommendations:

Provide equivalent instructions using cross-platform tools such as Azure CLI or Microsoft Graph REST API, which can be used on Linux, macOS, and Windows.
Explicitly mention that the PowerShell module can be used on non-Windows platforms if supported, or clarify platform requirements.
Add Linux/macOS command-line examples (e.g., Bash scripts or curl commands for REST API calls) alongside PowerShell examples.
Rephrase steps to be platform-agnostic where possible, or present Windows and Linux instructions in parallel.
Include a note about cross-platform compatibility and link to relevant documentation for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page suggests using Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention or provide examples for equivalent Linux or cross-platform tools (such as curl or HTTPie). No Linux-specific or cross-platform command-line examples are provided, and the only tool explicitly referenced is Windows-centric.

Recommendations:

Include examples using cross-platform tools such as curl or HTTPie for making HTTP requests.
Mention PowerShell as one option, but also provide equivalent Linux/macOS commands.
Add a note clarifying that any HTTP client can be used, and provide at least one example for each major platform (Windows, Linux, macOS).
Consider including screenshots or command snippets for both PowerShell and bash/zsh shells to ensure parity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral in its HTTP examples and explanations, but it does contain a subtle Windows bias by recommending '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 examples are provided for Linux users. This may unintentionally signal a preference for Windows environments.

Recommendations:

When suggesting tools for testing HTTP requests, include cross-platform and Linux-native options such as 'curl' and 'httpie' alongside PowerShell.
Provide example commands for both Windows (PowerShell) and Linux/macOS (bash with curl or httpie) to ensure parity.
Explicitly state that any HTTP client can be used, and offer links or references to documentation for popular Linux tools.
Avoid mentioning Windows tools exclusively, or ensure that any mention is balanced with Linux equivalents.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform parity, providing explicit Linux, macOS, and Windows instructions for running the sample app. However, 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 filesystem limitation, and this warning is not contextualized as Windows-only. Additionally, the Windows command examples use 'py' instead of 'python', which is a Windows-specific launcher, and this is presented in a dedicated Windows tab, but the path length warning appears before the OS-specific tabs, potentially confusing non-Windows users.

Recommendations:

Clearly indicate that the 260-character path length limitation applies only to Windows, and note that Linux/macOS users are not affected.
Where Windows-specific filesystem or tool limitations are mentioned, explicitly label them as such to avoid confusion.
Continue providing OS-specific command tabs for parity, and ensure that any general instructions are truly cross-platform or are clearly scoped to the relevant OS.
Consider adding troubleshooting notes for common Linux/macOS issues (e.g., permissions, virtual environments) to further balance the documentation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on ASP.NET (a Microsoft stack) and referencing Visual Studio and Visual Studio Code as the only development environments, without mentioning Linux-specific tools or workflows. There are no explicit Linux setup or run instructions, and the only example paths and instructions (such as localhost:44316 and path length warnings) are tailored to Windows environments. No Linux terminal or deployment guidance is provided.

Recommendations:

Add explicit instructions for running the sample on Linux, including any required dependencies or differences in commands (e.g., using the dotnet CLI).
Mention Linux-compatible editors (such as JetBrains Rider or simply using VS Code on Linux) and provide guidance for installing the .NET SDK on Linux distributions.
Include notes about file path limitations that are specific to Windows, and clarify if these do not apply to Linux.
Provide example commands and screenshots from a Linux terminal in addition to or instead of Windows-centric examples.
Clarify that the sample can be run cross-platform and provide troubleshooting tips for common Linux-specific issues (such as HTTPS certificate trust for localhost).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code in prerequisites and usage instructions. There are no explicit Linux-specific instructions or examples, such as using Linux-native editors, command-line tools, or deployment steps. The documentation does not mention or provide guidance for running the sample on Linux, nor does it address potential platform-specific issues (e.g., file permissions, path length limits, HTTPS certificates).

Recommendations:

Provide explicit instructions for running the sample on Linux, including installation of .NET SDK and use of Linux-native editors (e.g., Vim, Emacs, JetBrains Rider) or command-line tools.
Include Linux-specific notes for common issues, such as HTTPS certificate trust, file permissions, and path length differences.
Balance the order of presentation: mention Visual Studio Code (cross-platform) before Visual Studio, or present both options in parallel.
Add Linux and macOS terminal commands for building and running the sample (e.g., using `dotnet run`), not just references to IDEs.
Clarify that the sample is cross-platform and provide troubleshooting tips for non-Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on ASP.NET Core and Visual Studio tooling, which are most commonly used on Windows. While the .NET CLI is cross-platform, the documentation refers to Visual Studio and Visual Studio Code as tabs, but the package installation example for Visual Studio Code uses Install-Package, which is a PowerShell/NuGet Package Manager Console command only available in Visual Studio on Windows, not in VS Code or on Linux/macOS. There are no explicit Linux/macOS instructions or terminal examples, and no mention of Linux-specific considerations (such as file paths, environment variables, or running the app on Linux).

Recommendations:

Ensure all command-line examples use the cross-platform dotnet CLI (e.g., 'dotnet add package ...') for both Visual Studio and Visual Studio Code, since Install-Package is not available in VS Code or on Linux/macOS.
Explicitly mention that the instructions apply to Windows, Linux, and macOS, and provide notes for any OS-specific steps or differences (such as file paths, environment variables, or HTTPS development certificates).
Add a section or callout for running and debugging the application on Linux/macOS, including any prerequisites (e.g., installing the .NET SDK, trusting HTTPS certificates).
Avoid referencing Windows-specific tools or patterns (such as the Visual Studio Package Manager Console) without providing equivalent cross-platform alternatives.
Use forward slashes in file paths or note both Windows and Linux/macOS path conventions when referencing files.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on ASP.NET Core and C# code samples, which are most commonly associated with Windows development environments. There are no examples, instructions, or references for Linux-specific workflows, tools, or deployment patterns. The documentation does not mention cross-platform considerations, nor does it provide parity for developers working on Linux or macOS systems.

Recommendations:

Explicitly mention that ASP.NET Core is cross-platform and can be developed and deployed on Linux and macOS, not just Windows.
Include instructions or links for setting up the development environment on Linux (e.g., installing .NET SDK, configuring with VS Code or JetBrains Rider).
Add examples of running the application and managing configuration files on Linux (e.g., using bash commands, Linux file paths, environment variables).
Reference Linux-compatible tools for development and deployment, such as systemd for service management, or nginx for reverse proxy.
Ensure that all code and configuration examples use platform-agnostic paths and commands, or provide both Windows and Linux variants where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal web interface and does not provide any command-line examples or tooling instructions for Linux environments. There are no mentions of Linux-specific tools, CLI commands, or PowerShell alternatives. All steps are described using GUI navigation, which is platform-agnostic but implicitly assumes a Windows-centric workflow due to the lack of Linux parity examples.

Recommendations:

Add Azure CLI examples for all major steps (e.g., app registration, secret creation, identity provider configuration) to support Linux and cross-platform users.
Include references to automation via scripting (e.g., Bash, PowerShell, or Python) for tasks currently described only via the portal.
Explicitly mention that the Azure portal is accessible from any OS/browser, but provide parity for users who prefer command-line or automated approaches.
Where XML configuration is required, provide guidance on editing files using cross-platform editors and tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal (web UI) and does not provide any command-line examples for configuration. Where command-line instructions are given (e.g., cloning GitHub repositories), only generic 'git' commands are shown, with no mention of platform-specific tools. There is no mention of Powershell, but all portal navigation and configuration steps implicitly assume a Windows-centric workflow, as Azure portal and B2C custom policy management are most commonly performed on Windows. There are no Linux-specific instructions, nor is there any mention of Azure CLI, Bash, or cross-platform automation options.

Recommendations:

Provide Azure CLI and/or Bash examples for key configuration steps, especially for identity provider setup and custom policy uploads.
Explicitly state that all steps can be performed from any OS with a web browser, and clarify any platform-specific requirements.
Include references to Linux-compatible tools for managing Azure AD B2C (e.g., Azure CLI, REST API), and provide example commands.
Where file editing is required (e.g., XML policy files), mention cross-platform editors and workflows.
Add a parity check to ensure all instructions are equally accessible from Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure Portal (a web-based GUI) and providing no command-line examples for configuration or automation. There are no references to Linux tools, shell commands, or cross-platform scripting. All XML and PowerShell snippets assume a Windows-centric workflow, and there is no mention of how to perform these tasks using Linux or cross-platform CLI tools such as Azure CLI or Bash scripts.

Recommendations:

Include Azure CLI command examples for policy key creation, policy uploads, and other configuration steps, ensuring parity for Linux and macOS users.
Explicitly mention that all steps can be performed from any OS using the Azure Portal, and provide links or notes for cross-platform compatibility.
If PowerShell is referenced, provide equivalent Bash or shell commands where possible.
Add a section or callouts for Linux/macOS users, highlighting any differences or confirming that the process is OS-agnostic.
Where file editing is required (e.g., XML files), mention cross-platform editors and tools.

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 includes '?tabs=windows', suggesting that Windows-specific instructions are the default or primary guidance. There are no explicit Linux or cross-platform command-line examples, and the only referenced tab is 'windows'. However, the main content is generally platform-neutral and does not rely on Windows-only tools or PowerShell.

Recommendations:

Provide explicit Linux/macOS examples or instructions where platform-specific steps are referenced, especially in linked documentation.
When linking to further documentation (e.g., for securing REST APIs), use a neutral or multi-tab link (such as '?tabs=linux' or a link to a tabbed page) to avoid suggesting Windows as the default.
If there are command-line or scripting steps, include both Windows (PowerShell/CMD) and Linux/macOS (Bash) equivalents.
Review all linked documentation to ensure Linux parity and that Linux users are not required to adapt Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation displays a mild Windows bias in the instructions for generating the Android signature hash for the redirect URI. The Windows command is presented first and uses Windows-specific environment variables and paths, while the Linux/macOS equivalent is labeled as 'iOS' and provided second. No PowerShell-specific examples, Windows-only tools, or missing Linux equivalents are present elsewhere in the documentation.

Recommendations:

Present platform instructions in parallel (e.g., 'For Windows', 'For Linux/macOS') rather than 'Windows first'.
Label the non-Windows example as 'Linux/macOS' rather than 'iOS', since the command is for Android development on those platforms.
Consider providing a brief explanation of environment variable differences between platforms.
Where possible, provide cross-platform commands or clarify any platform-specific steps.
Ensure parity in tool references and avoid implying Windows as the default development environment.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples or tooling, but it also does not include any command-line or scripting examples at all. There is no explicit Windows bias, but the lack of concrete examples (such as PowerShell, Windows command line, Bash, or Linux tools) means Linux parity is not addressed. If future examples are added, care should be taken to include both Windows and Linux approaches.

Recommendations:

If adding code or command-line examples (e.g., using Microsoft Graph API), provide both PowerShell (Windows) and Bash/cURL (Linux/macOS) examples.
Mention cross-platform tools (such as Azure CLI or REST API via cURL) before or alongside any Windows-specific tools.
Explicitly state that the instructions apply equally to all platforms, or call out any platform-specific differences.
If referencing scripts or automation, provide samples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page provides detailed instructions for registering a Microsoft Graph application in Azure AD B2C, but all steps are described exclusively via the Azure Portal (web UI) and do not include any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users, as no CLI (such as Azure CLI or Microsoft Graph CLI) or scripting examples are provided. This omission may disadvantage users who prefer or require command-line automation, especially on Linux or macOS platforms.

Recommendations:

Add equivalent Azure CLI commands for all portal-based steps, such as application registration, permission assignment, and client secret creation.
Provide Microsoft Graph CLI or REST API examples for registering applications and managing permissions.
Include sample scripts (in Bash or cross-platform scripting languages) to automate the registration and configuration process.
Explicitly mention that all steps can be performed via CLI on Linux/macOS, and link to relevant CLI documentation.
Ensure that any automation guidance is not limited to Windows or PowerShell, but is accessible to users on all platforms.

Create pull request

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