Active Directory B2C

283
Total Pages
224
Linux-Friendly Pages
59
Pages with Bias
20.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

392 issues found
Showing 276-300 of 392 flagged pages
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing Visual Studio (a Windows-first IDE) before Visual Studio Code, and by omitting explicit instructions or examples for running the sample application on Linux (e.g., using the dotnet CLI or Linux-specific setup steps). There are no PowerShell-heavy examples or exclusive use of Windows tools, but the lack of Linux parity in setup and run instructions is notable.
Recommendations
  • Add explicit instructions for running the sample on Linux, including using the dotnet CLI (e.g., 'dotnet build', 'dotnet run') instead of relying solely on Visual Studio/Visual Studio Code.
  • Include notes about installing .NET SDK on Linux distributions and any required dependencies.
  • Provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, HTTPS certificate trust for localhost).
  • Ensure screenshots and examples do not assume the use of Windows-only tools or interfaces.
  • Consider listing Visual Studio Code and CLI instructions before or alongside Visual Studio to avoid Windows-first ordering.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-application.md ...directory-b2c/enable-authentication-web-application.md
Medium Priority View Details →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET web applications and development workflows typical of Windows environments. It references Visual Studio and Visual Studio Code, but does not provide explicit Linux or cross-platform instructions, nor does it mention Linux-specific tools or considerations. There are no examples or guidance for running, debugging, or deploying the application on Linux systems.
Recommendations
  • Explicitly mention that .NET Core and ASP.NET Core are cross-platform and can be developed and run on Linux and macOS as well as Windows.
  • Provide Linux-specific instructions for installing the .NET SDK, creating projects, and running applications (e.g., using apt, yum, or snap for installation).
  • Include terminal commands and examples that are platform-agnostic or show both Windows (cmd/PowerShell) and Linux/macOS (bash) equivalents.
  • Reference popular Linux editors (such as VS Code, Vim, or JetBrains Rider) and include instructions for using them.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, HTTPS certificate trust, environment variables).
  • Clarify that the dotnet CLI commands work the same on Linux, and provide sample output or screenshots from a Linux terminal.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md ...ob/main/articles/active-directory-b2c/access-tokens.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention any Linux or cross-platform alternatives (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.
  • When suggesting tools for testing, mention both PowerShell and common Linux/macOS tools (e.g., 'You can use any HTTP client such as curl, HTTPie, or Microsoft PowerShell').
  • Provide sample command-line invocations for both Windows (PowerShell) and Linux/macOS (bash/curl) environments.
  • Avoid mentioning Windows tools exclusively or first; present cross-platform options or alternate between platforms.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app.md ...ctory-b2c/configure-authentication-in-azure-web-app.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on configuring Azure AD B2C authentication via the Azure Portal UI and does not provide any OS-specific command-line examples. However, it implicitly assumes the use of Azure Web Apps, which are often managed via Windows-centric tools and patterns. There are no explicit examples or instructions for Linux environments, CLI usage, or cross-platform automation (e.g., Azure CLI, Bash scripts). There is also no mention of Linux-specific considerations or parity in deployment or configuration steps.
Recommendations
  • Add Azure CLI examples for all configuration steps, including app registration, secret creation, and authentication provider setup, to ensure Linux and cross-platform parity.
  • Include Bash shell command examples for retrieving and using tokens, in addition to any future PowerShell or Windows command-line examples.
  • Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant cross-platform tooling documentation.
  • If screenshots or UI steps are shown, clarify that the Azure Portal is web-based and OS-agnostic, and provide alternative instructions for headless or automated environments.
  • Highlight any OS-specific caveats or differences, if they exist, especially for developers deploying from Linux environments.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app.md ...rectory-b2c/configure-authentication-sample-web-app.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on ASP.NET and .NET tooling (Visual Studio, Visual Studio Code, .NET SDK) without mentioning Linux-specific instructions or considerations. While Visual Studio Code and .NET Core are cross-platform, the documentation does not provide explicit Linux (or macOS) setup or run instructions, nor does it address common Linux-specific issues (such as file permissions, path separators, or HTTPS certificate setup). The example redirect URI uses a Windows-style localhost port, and there is no mention of Linux package managers or terminal commands beyond 'git clone'.
Recommendations
  • Add explicit instructions for running the sample on Linux (e.g., using the dotnet CLI, installing .NET SDK via apt/yum/pacman, handling HTTPS development certificates).
  • Include Linux/macOS-specific notes for opening the project (e.g., using 'code .' in the terminal, or 'dotnet run' instead of relying on Visual Studio).
  • Mention any platform-specific prerequisites or troubleshooting tips (such as setting executable permissions, or dealing with case-sensitive file systems).
  • Provide example commands for both Windows and Linux environments where relevant.
  • Clarify that the instructions are cross-platform and highlight any differences users might encounter on Linux.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api.md ...irectory-b2c/enable-authentication-web-app-with-api.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on ASP.NET Core and Visual Studio/Visual Studio Code workflows, which are most commonly associated with Windows development. While the .NET CLI commands are cross-platform, the only alternative package installation example uses Install-Package, which is a PowerShell/NuGet Package Manager Console command specific to Windows/Visual Studio. There are no explicit Linux or macOS instructions, terminal examples, or mentions of Linux-specific environments or tools. The documentation implicitly assumes a Windows development environment and omits guidance for Linux users.
Recommendations
  • Ensure all command-line examples use the .NET CLI (dotnet) commands, which are cross-platform, and avoid Windows-specific commands like Install-Package unless also providing Linux/macOS equivalents.
  • Explicitly mention that the instructions work on Windows, Linux, and macOS, and provide any necessary notes for Linux/macOS users (e.g., file path separators, prerequisites, or environment setup).
  • Include a section or callout for Linux/macOS users, highlighting any differences in project setup, running, or debugging.
  • Where Visual Studio is referenced, also mention Visual Studio Code and command-line workflows as equally valid, and provide links to official .NET documentation for Linux/macOS development.
  • If screenshots or UI walkthroughs are included elsewhere, ensure parity by showing Linux/macOS environments as well as Windows.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/integrate-with-app-code-samples.md ...ctive-directory-b2c/integrate-with-app-code-samples.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists a variety of code samples for integrating Azure AD B2C across multiple platforms and languages. However, in the desktop application section, only a Windows Desktop .NET (WPF) sample is provided, with no equivalent Linux or cross-platform desktop sample. Additionally, .NET samples are prominently featured and listed first in several sections, which may give the impression of a Windows-first approach.
Recommendations
  • Add cross-platform desktop application samples (e.g., using .NET MAUI, Electron, or Qt) that run on Linux and macOS, not just Windows.
  • Explicitly note platform compatibility for each sample, and provide Linux/macOS instructions or alternatives where possible.
  • Balance the order of presentation so that non-Windows and cross-platform samples are not consistently listed after Windows/.NET samples.
  • Where .NET is used, clarify if the sample is Windows-only or cross-platform (e.g., .NET Core vs. .NET Framework).
  • Consider adding shell/bash scripts or Linux-specific setup instructions where relevant.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-microsoft-account.md ...e-directory-b2c/identity-provider-microsoft-account.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation exclusively references the Azure portal web UI for configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). There is no mention of Linux-specific tools or workflows, nor are there any cross-platform command-line instructions. The implicit assumption is that users will interact with the Azure portal via a web browser, which is cross-platform, but there is a subtle 'windows_first' bias in the absence of CLI or automation examples that are popular in Linux environments.
Recommendations
  • Add Azure CLI examples for all configuration steps, including app registration, secret creation, and identity provider setup.
  • Where relevant, provide both PowerShell and Bash (or Azure CLI) scripts to ensure parity for Linux and Windows users.
  • Explicitly mention that all portal steps can be performed from any OS with a supported browser, but highlight automation options for Linux users.
  • Include references to documentation for automating these tasks using cross-platform tools.
  • Ensure that any downloadable scripts or code samples are provided in both Windows and Linux-friendly formats.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-grit-authentication.md ...es/active-directory-b2c/partner-grit-authentication.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by 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 biometric options on other platforms, and there are no explicit Linux or macOS examples or tool mentions. The documentation does not provide parity in describing how Linux users might enroll or use biometric authentication, nor does it mention Linux-compatible biometric solutions.
Recommendations
  • Include explicit examples of biometric authentication on Linux (e.g., fingerprint readers using fprintd, or FaceID alternatives).
  • Mention macOS biometric options (such as Touch ID or Face ID) alongside Windows Hello.
  • Rephrase scenario walkthroughs to present platform options in a neutral order, or provide parallel examples for Windows, Linux, and macOS.
  • Add troubleshooting or setup notes for Linux and macOS users regarding biometric enrollment and compatibility.
  • Reference cross-platform biometric standards (such as FIDO2/WebAuthn) and how they are supported on different operating systems.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-idemia.md ...b/main/articles/active-directory-b2c/partner-idemia.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure Portal (a web-based GUI) and providing XML/PowerShell-style configuration snippets without mentioning or providing examples for Linux command-line tools or workflows. There are no references to Linux-specific tools, shell commands, or alternative approaches for Linux administrators. The instructions assume a GUI-based workflow, which is more common among Windows users, and do not address parity for Linux environments.
Recommendations
  • Include CLI-based instructions using Azure CLI (az), which is cross-platform and commonly used on Linux.
  • Explicitly mention that the Azure Portal is accessible from any OS, including Linux, to clarify that the steps are not Windows-specific.
  • Provide examples of editing XML files using common Linux tools (e.g., nano, vim) and uploading them via CLI or REST API, not just through the portal.
  • If PowerShell is referenced, also provide Bash or shell script equivalents for Linux users.
  • Add a section or callout for Linux/macOS users, highlighting any differences or confirming that the process is OS-agnostic.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/register-apps.md ...ob/main/articles/active-directory-b2c/register-apps.md
Medium Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias by referencing SAML application registration with a link that includes '?tabs=windows', suggesting Windows-specific instructions or defaults. There are no explicit Linux or cross-platform examples or tabs mentioned, and no mention of Linux tools or equivalents. This may lead Linux users to feel secondary or unsupported.
Recommendations
  • Ensure that all platform-specific instructions (such as for SAML apps) provide both Windows and Linux (and macOS, if relevant) tabs or examples.
  • Avoid defaulting to Windows tabs or instructions; instead, present a neutral or platform-agnostic default, or clearly offer platform selection.
  • Explicitly mention cross-platform tools or provide parity in examples for Linux environments where applicable.
  • Review linked pages (such as the SAML application guide) to verify that Linux instructions are present and as detailed as Windows instructions.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-arkose-labs.md ...n/articles/active-directory-b2c/partner-arkose-labs.md
Medium Priority View Details →
Scanned: 2025-09-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes the use of Visual Studio Code and Azure Functions extensions, which are cross-platform, but the workflow and terminology (e.g., 'command prompt', 'Visual Studio Marketplace') are more familiar to Windows users. There are no explicit Linux/macOS shell examples or references to Linux-specific tools or workflows. The instructions for running and deploying the API mention 'terminal or command prompt' generically, but all step-by-step guidance and screenshots are based on the Azure Portal and Visual Studio Code UI, with no CLI or Linux-native workflow examples. There is no mention of Bash, zsh, or Linux package managers, nor are there any screenshots or commands shown from a Linux environment.
Recommendations
  • Add explicit examples and instructions for Linux users, such as using Bash or zsh in the terminal.
  • Include CLI-based alternatives (e.g., Azure CLI, az functionapp commands) for creating and deploying Azure Functions, alongside Visual Studio Code instructions.
  • Reference Linux package managers or installation steps for required tools (e.g., how to install Azure Functions Core Tools on Ubuntu).
  • Provide screenshots or terminal output examples from a Linux environment.
  • Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and provide links or notes for Linux/macOS installation and usage.
  • Avoid Windows-centric terminology like 'command prompt' unless also mentioning 'terminal' or 'shell' for Linux/macOS.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2025-09-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code, and by not providing explicit Linux or cross-platform instructions for running or building the sample application. There are no terminal or shell commands shown for Linux environments, nor are there any mentions of Linux-specific tools or considerations. The only command-line example is a generic Bash git clone, but all build/run instructions assume the use of Visual Studio or Visual Studio Code without clarifying Linux compatibility or providing dotnet CLI commands.
Recommendations
  • Explicitly mention that the sample can be built and run on Linux and macOS using the .NET CLI (dotnet build, dotnet run), not just through Visual Studio/VS Code.
  • Provide step-by-step instructions for Linux users, including terminal commands for restoring dependencies, building, and running the application using the dotnet CLI.
  • Include notes about any platform-specific requirements or differences (such as HTTPS certificate setup on Linux/macOS).
  • List prerequisites for Linux (and optionally macOS), such as installing the .NET SDK and any required dependencies.
  • Ensure screenshots and instructions are not exclusively tailored to Windows environments.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-akamai-secure-hybrid-access.md ...e-directory-b2c/partner-akamai-secure-hybrid-access.md
Medium Priority View Details →
Scanned: 2025-09-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing certificate management steps that link only to Windows-specific instructions and omitting equivalent Linux or cross-platform guidance. For example, the steps to obtain and upload certificates for SAML configuration link to documentation with a 'tabs=windows' parameter, and there are no Linux or cross-platform alternatives or notes. Additionally, the only application code sample provided is for ASP.NET MVC (a Windows-centric technology), with no mention of Linux-compatible frameworks or deployment options.
Recommendations
  • Provide explicit Linux (and macOS, if possible) instructions or links for certificate generation and management, such as using OpenSSL or Linux-native tools.
  • Update links to certificate management documentation to include both Windows and Linux tabs, or add a note clarifying Linux alternatives.
  • Include code samples or references for cross-platform or Linux-friendly application frameworks (e.g., Node.js, Python Flask, Java Spring) in addition to ASP.NET MVC.
  • When referencing sample applications, ensure at least one is easily runnable on Linux (e.g., the Docker header-demo-app is a good start, but clarify how to run it on Linux).
  • Review all step-by-step instructions to ensure parity for Linux users, especially in areas involving file manipulation, certificate creation, and application deployment.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md ...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Medium Priority View Details →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a link for securing REST APIs with a query parameter '?tabs=windows', suggesting that Windows-specific instructions are prioritized or presented first. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux tooling or parity in the referenced sections. The documentation assumes a Windows environment for certain setup steps, which may hinder Linux users.
Recommendations
  • Ensure that all referenced links (such as 'secure-rest-api.md?tabs=windows') provide Linux/macOS tabs or examples, and mention this in the documentation.
  • Explicitly state that the instructions are cross-platform where applicable, or provide parallel Linux/macOS instructions if differences exist.
  • Avoid using Windows-specific query parameters or language in documentation unless absolutely necessary; instead, use neutral or multi-platform phrasing.
  • Where command-line or scripting is referenced, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
  • Audit all referenced guides for similar bias and update them to ensure Linux parity.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio and path length limitations (260 characters) that are primarily relevant to Windows. While Visual Studio Code is mentioned as a cross-platform alternative, there are no explicit Linux/macOS-specific instructions or examples (e.g., for running, building, or troubleshooting the .NET app on Linux). The documentation assumes familiarity with Windows tooling and omits Linux-specific considerations, such as file permissions, environment variables, or alternative editors/IDEs.
Recommendations
  • Explicitly mention that Visual Studio Code and .NET SDK are cross-platform, and provide links or notes for Linux/macOS installation.
  • Include Linux/macOS-specific instructions or notes for running and building the sample (e.g., using the dotnet CLI in a terminal).
  • Clarify that the 260-character path length limitation is a Windows-specific constraint, and note that Linux/macOS users are not affected.
  • Provide troubleshooting tips or common issues for Linux/macOS users (e.g., file permissions, HTTPS development certificates).
  • Consider including example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash) where relevant.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-f5.md .../blob/main/articles/active-directory-b2c/partner-f5.md
Medium Priority View Details →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and by linking to IIS-specific setup instructions. There are no equivalent examples or guidance for Linux-based web servers or applications, and no mention of Linux tools or deployment patterns. All other instructions are platform-agnostic, focusing on Azure, F5 BIG-IP, and browser-based configuration.
Recommendations
  • Provide Linux-based application examples (e.g., Apache, Nginx) alongside the IIS example for testing.
  • Include links or references to documentation for setting up a test web application on Linux.
  • Clarify that the solution is compatible with both Windows and Linux back-end applications.
  • Where possible, use neutral language (e.g., 'web application') instead of referencing only IIS.
  • Add troubleshooting notes or configuration tips relevant to common Linux web servers.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by referencing Visual Studio as the primary development tool and omitting explicit instructions or examples for Linux users. While Visual Studio Code is mentioned (which is cross-platform), there are no details about running the sample on Linux, nor are there instructions for using Linux-specific tools or terminal commands beyond 'git clone'. The instructions for building and running the sample assume Visual Studio or Visual Studio Code, but do not clarify how to use the .NET CLI or other Linux-native workflows. There are no PowerShell-specific examples, but the overall guidance is Windows-centric.
Recommendations
  • Add explicit instructions for Linux users, such as using the .NET CLI (e.g., 'dotnet build', 'dotnet run') to build and run the sample projects.
  • Include Linux-specific prerequisites, such as installing the .NET SDK on Ubuntu or other distributions.
  • Clarify that Visual Studio Code is cross-platform and provide steps for running the sample on Linux and macOS.
  • Add troubleshooting notes for common Linux issues (e.g., HTTPS development certificates, file permissions, path length limitations).
  • Ensure all screenshots and UI references are either generic or include Linux/VS Code equivalents.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-akamai-secure-hybrid-access.md ...e-directory-b2c/partner-akamai-secure-hybrid-access.md
Medium Priority View Details →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing certificate management steps that link only to Windows-specific instructions, and by omitting Linux or cross-platform alternatives for key tasks such as obtaining and uploading certificates. Additionally, the application code samples and configuration steps are focused on ASP.NET/OWIN (Windows-centric technologies), with no mention of Linux-compatible frameworks or deployment scenarios.
Recommendations
  • Provide parallel instructions and links for obtaining and uploading certificates on Linux (e.g., using OpenSSL and Azure CLI/PowerShell cross-platform).
  • Include examples or references for configuring and running sample applications (such as the header-demo-app and OIDC app) on Linux environments.
  • When referencing code samples (e.g., ASP.NET/OWIN), mention equivalent approaches for popular Linux-friendly frameworks (such as Node.js, Python Flask/Django, or Java Spring) and link to relevant documentation.
  • Ensure all referenced documentation (such as 'obtain a certificate' and 'upload the certificate') includes tabs or sections for Linux/macOS, not just Windows.
  • Explicitly state that the procedures are cross-platform where applicable, and highlight any platform-specific differences.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-arkose-labs.md ...n/articles/active-directory-b2c/partner-arkose-labs.md
Medium Priority View Details →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected 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 macOS alternatives. There are no explicit Linux-specific instructions or examples, and the workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Explicitly mention that Visual Studio Code and the Azure Functions extension are cross-platform, and provide installation instructions for Linux and macOS.
  • Include alternative instructions or notes for deploying and running Azure Functions using native Linux/macOS terminals and tools (e.g., bash, zsh), not just 'terminal' or 'command prompt'.
  • Provide examples of environment variable management and local.settings.json creation for Linux/macOS users, including common CLI commands.
  • Clarify that the Azure portal is web-based and accessible from any OS, and provide screenshots or notes that are OS-agnostic.
  • If referencing command-line operations, include both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) equivalents where applicable.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-f5.md .../blob/main/articles/active-directory-b2c/partner-f5.md
Medium Priority View Details →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, without mentioning or providing alternatives for Linux-based web servers. There are no Linux-specific instructions, examples, or references to common Linux tools or environments. All application setup and testing guidance is centered on Windows technologies, with no parity for Linux users.
Recommendations
  • Provide parallel examples for Linux-based web servers (e.g., Apache, Nginx) alongside IIS, including setup and configuration steps.
  • Reference Linux-compatible application environments and tools where relevant, not just Windows/IIS.
  • Include troubleshooting tips and configuration guidance for both Windows and Linux back-end applications.
  • When mentioning IIS, add a note or section for Linux users with equivalent instructions.
  • Ensure that any sample code, screenshots, or walkthroughs are not exclusively Windows-centric.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/authorization-code-flow.md ...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority View Details →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is largely platform-neutral, focusing on HTTP requests and protocol details. However, in the section on testing POST HTTP requests, only Microsoft PowerShell is mentioned as an example HTTP client, with no mention of Linux or cross-platform alternatives. There are no explicit examples or instructions for Linux users, nor are Linux-native tools (such as curl or httpie) referenced.
Recommendations
  • When suggesting HTTP clients for testing, mention cross-platform and Linux-native tools such as curl, httpie, or wget alongside PowerShell.
  • Provide example commands using curl or httpie for making POST and GET requests, ensuring Linux users have clear, ready-to-use examples.
  • Avoid referencing only Windows-specific tools or interfaces; always include at least one cross-platform or Linux-native alternative when demonstrating command-line interactions.
  • Consider adding a short section or callout noting that all HTTP requests can be performed using standard tools available on Linux, macOS, and Windows.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md ...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Medium Priority View Details →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation contains a subtle Windows bias. In the few places where platform-specific instructions are referenced (such as securing REST APIs with OAuth2 bearer tokens), the documentation links to instructions with a 'tabs=windows' parameter, and does not mention or provide Linux-specific examples or parity. There are no explicit PowerShell or Windows-only tool examples, but the guidance assumes the reader is using Windows as the default environment for certain steps.
Recommendations
  • Wherever documentation links include platform-specific tabs (e.g., 'tabs=windows'), ensure that Linux (and macOS, if applicable) tabs are also referenced or mentioned, so users on those platforms know equivalent instructions exist.
  • Explicitly mention that the steps for securing REST APIs, obtaining tokens, and other platform-sensitive operations can be performed on Linux and macOS, and provide direct links or notes to those instructions.
  • Review all linked documentation to ensure Linux parity and add clarifying notes in this guide if any steps differ between Windows and Linux.
  • If any scripts, CLI commands, or setup steps are provided in the future, ensure both Windows (PowerShell/CMD) and Linux (Bash/CLI) examples are included side-by-side.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Visual Studio (a primarily Windows tool) before Visual Studio Code in the prerequisites, and by not providing explicit Linux/macOS instructions or examples for running or building the sample application. There are no PowerShell-specific commands or Windows-only tools mentioned, but the lack of Linux/macOS parity in setup and execution steps may disadvantage non-Windows users.
Recommendations
  • Explicitly include instructions for Linux/macOS users, such as using the dotnet CLI to build and run the project (e.g., 'dotnet build', 'dotnet run').
  • Clarify that Visual Studio Code and the .NET SDK are cross-platform, and provide terminal commands for common tasks (restoring dependencies, running the app) on Linux/macOS.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, HTTPS development certificates, path length differences).
  • Where screenshots or UI steps are shown for Visual Studio, consider including equivalent steps for Visual Studio Code or CLI usage.
  • Mention any platform-specific requirements or differences, such as installing the .NET SDK on Linux/macOS, or handling HTTPS development certificates.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-python-web-app.md ...-b2c/configure-authentication-sample-python-web-app.md
Medium Priority View Details →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides cross-platform guidance, but there are subtle signs of Windows bias. The instruction to extract the sample to a folder with a path length of 260 or fewer characters references a Windows-specific limitation. Additionally, in the 'Run the sample web app' section, the Windows example uses 'py' instead of 'python', which is a Windows-specific launcher, and the order of examples places Linux and macOS before Windows, but the path length warning appears before any OS-specific instructions.
Recommendations
  • Clarify that the 260-character path length limitation is specific to Windows, and note that Linux/macOS users are not affected.
  • In the 'Run the sample web app' section, explicitly state that 'py' is the Windows Python launcher, and that 'python' should be used on Linux/macOS.
  • Consider providing a note or table summarizing OS-specific differences (such as path length limits and Python launcher usage) to improve clarity for all users.
  • Ensure that any filesystem or tool limitations are clearly attributed to their respective platforms to avoid confusion.
  • Continue to provide parallel examples for all major platforms, and avoid assuming Windows-specific behaviors apply to all users.
GitHub Create Pull Request
← Previous Page 12 of 16 Next →