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 301-325 of 392 flagged pages
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, particularly in the certificate creation and upload steps, where only Windows-specific instructions or links are provided. There are no explicit Linux or cross-platform examples for tasks such as certificate management, and the application example for OIDC is based on ASP.NET MVC (a Windows-centric technology), with no mention of Linux or open-source alternatives.
Recommendations
- Provide Linux and macOS instructions for certificate creation and management (e.g., using OpenSSL) alongside or before Windows-specific instructions.
- Include examples of registering and configuring applications using cross-platform frameworks (e.g., Node.js, Python Flask/Django, Java Spring) in addition to ASP.NET MVC.
- Ensure that all referenced documentation (such as certificate upload and management) includes tabs or sections for Linux, macOS, and Windows.
- When referencing command-line tools or scripts, offer both PowerShell/Windows and Bash/Linux equivalents.
- Explicitly state that the process is platform-agnostic where possible, and highlight any steps that are unique to a particular OS.
Create Pull Request
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 →
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 'terminal or command prompt' without explicitly referencing Linux or macOS shells. There are no explicit Linux-specific instructions or examples, and all tooling references (e.g., Visual Studio Code, Azure portal) are platform-neutral but implicitly assume familiarity with Windows-centric workflows. There are no PowerShell-specific commands, but the lack of Linux/macOS terminal examples or explicit parity is notable.
Recommendations
- Explicitly mention that all steps can be performed on Linux and macOS, not just Windows.
- Provide example commands for common Linux/macOS shells (e.g., bash, zsh) where relevant, especially for environment variable management and local development.
- Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and provide installation links/instructions for Linux/macOS.
- Where 'terminal or command prompt' is mentioned, add 'or shell' and clarify with examples for bash/zsh.
- If screenshots or UI flows differ on Linux/macOS, provide alternative visuals or notes.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences).
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and linking to IIS setup instructions. There are no equivalent examples or guidance for deploying or testing with Linux-based web servers (such as Apache or Nginx). No PowerShell or Windows-specific tools are mentioned, but the lack of Linux parity in examples and references suggests an implicit preference for Windows environments.
Recommendations
- Provide parallel examples for setting up a Linux-based test application (e.g., Apache or Nginx) alongside the IIS example.
- Include links to official documentation for configuring SSL and web applications on popular Linux distributions.
- Clarify that the solution is platform-agnostic and can be used with both Windows and Linux back-end applications.
- Wherever IIS is referenced, add a corresponding Linux alternative or a note explaining how to adapt the steps for Linux environments.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references IIS (a Windows-only web server) as the example application for testing, and provides a link to IIS setup instructions, but does not mention or provide examples for Linux-based web servers (such as Apache or Nginx). There are no explicit PowerShell or Windows command-line examples, but the only application setup guidance is Windows-centric. No Linux equivalents or cross-platform alternatives are discussed.
Recommendations
- Include Linux-based web application examples (e.g., Apache, Nginx, or a simple Python/Node.js app) alongside IIS for testing the integration.
- Provide links or brief instructions for setting up a test web application on Linux, similar to the IIS setup link.
- Explicitly mention that the solution is platform-agnostic and can be used with both Windows and Linux back-end applications.
- Where possible, use neutral language (e.g., 'web application' instead of 'IIS app') and provide parity in examples and references.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET (a Microsoft-centric, Windows-originated framework) and by providing package installation instructions that reference Visual Studio and Visual Studio Code, both of which are more commonly associated with Windows development. There are no explicit Linux or cross-platform shell instructions, and no mention of Linux-specific development environments or considerations. All command-line examples use the dotnet CLI, which is cross-platform, but the context and tooling references are Windows-centric. No Linux-specific guidance or troubleshooting is provided.
Recommendations
- Explicitly mention that the dotnet CLI commands work on Linux, macOS, and Windows, and provide example terminal commands for Bash/zsh where appropriate.
- Include instructions for installing the .NET SDK on Linux (e.g., using apt, yum, or snap), or link to official cross-platform installation guides.
- When referencing IDEs, mention cross-platform options (e.g., JetBrains Rider, VS Code on Linux/macOS) and provide parity in instructions.
- Add a note or section on running and testing the ASP.NET Core app on Linux (e.g., using 'dotnet run' in a Bash shell), including any OS-specific caveats.
- Avoid using only Visual Studio/Visual Studio Code tabs; add a 'Command Line (Bash)' or 'Linux/macOS' tab for relevant steps.
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 →
Detected 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.
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 →
Detected 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.
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 →
Detected 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.
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 →
Detected 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.
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 →
Detected 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).
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api-options.md
...-b2c/enable-authentication-web-app-with-api-options.md
Medium Priority
View Details →
Detected 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.
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 →
Detected 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.
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 →
Detected 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.
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 →
Detected 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.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-bindid.md
...b/main/articles/active-directory-b2c/partner-bindid.md
Medium Priority
View Details →
Detected 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.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references the Azure portal web UI for configuration and does not provide any command-line examples. There are no explicit references to Windows-only tools like PowerShell, but the workflow assumes a graphical interface that is most familiar to Windows users. There is no mention of Linux command-line tools (such as Azure CLI), nor are there any CLI-based instructions or examples for Linux or cross-platform users.
Recommendations
- Add Azure CLI examples for all major steps, such as registering applications, creating secrets, and configuring identity providers. Ensure these examples are cross-platform.
- Explicitly mention that all portal steps can be performed from any OS with a web browser, to clarify that the instructions are not Windows-specific.
- Where possible, provide REST API or scripting alternatives for automation and parity with non-Windows environments.
- Include a section or callout for Linux/macOS users, highlighting any differences or additional steps if applicable.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api-options.md
...-b2c/enable-authentication-web-app-with-api-options.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on ASP.NET Core and C# code, referencing project structures and files (e.g., Startup.cs, appsettings.json) that are typical of Windows/.NET development environments. There are no examples or guidance for Linux or cross-platform development environments, nor are there any mentions of command-line tools or workflows outside the Windows/.NET ecosystem.
Recommendations
- Include explicit notes or examples for developers working on Linux or macOS, such as how to locate and edit configuration files, or how to run and debug ASP.NET Core applications using the dotnet CLI.
- Mention that ASP.NET Core is cross-platform and provide links or references to official guidance for developing and deploying on Linux and macOS.
- If relevant, provide bash or shell command equivalents for any setup or configuration steps that might otherwise be performed in Windows-specific tools.
- Clarify that the instructions and code samples apply to any platform where .NET Core is supported, not just Windows.
- Consider including a section or callout box highlighting any platform-specific considerations (e.g., file paths, environment variables) for Linux users.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-specific guidance first in at least one key area, and by omitting explicit Linux or cross-platform examples or instructions. Specifically, the link to securing REST APIs for technical profiles points to a documentation page with a 'tabs=windows' parameter, indicating Windows-first or Windows-only instructions. There are no PowerShell scripts or Windows tools directly shown, but the lack of Linux or cross-platform parity in referenced links and examples may hinder non-Windows users.
Recommendations
- Ensure that all referenced documentation links (such as those for securing REST APIs) either default to a cross-platform view or provide clear tabs for both Windows and Linux, with neither prioritized by default.
- Explicitly mention that the steps and examples are platform-agnostic where possible, or provide parallel instructions for Linux/macOS environments if any step is platform-dependent.
- Audit all external documentation links to confirm that Linux and macOS users are equally supported and not directed to Windows-specific instructions by default.
- If any scripts or command-line examples are added in the future, provide both PowerShell (Windows) and Bash (Linux/macOS) versions.
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 →
Detected 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 biometric options on other platforms, and there are no explicit examples or tool references for Linux or macOS biometric authentication. The documentation does not provide parity in naming or describing Linux (or other OS) equivalents, nor does it offer platform-agnostic guidance.
Recommendations
- Include explicit references to biometric authentication methods available on Linux (such as fprintd, or biometric support in GNOME/KDE environments) and macOS (Touch ID, Face ID).
- When describing scenarios, alternate or parallelize examples so that Windows, Linux, and macOS users see their platforms represented equally (e.g., 'After logging in with a Windows computer using Windows Hello, a Linux computer using fprintd, or a Mac using Touch ID...').
- Avoid listing Windows tools or features (like Windows Hello) before mentioning cross-platform or other OS equivalents.
- Add a section or table summarizing supported biometric authentication methods across different operating systems, with links to relevant setup guides for each.
- Ensure screenshots or UI walkthroughs are not exclusively Windows-centric, or provide equivalents for other platforms.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, most notably in the SAML application registration link, which includes a '?tabs=windows' query parameter, suggesting that Windows-specific instructions or tabs are prioritized or shown by default. There are no explicit Linux or cross-platform examples or tabs mentioned, and no Linux-specific tools or instructions are referenced.
Recommendations
- Ensure that all platform-specific instructions (Windows, Linux, macOS) are equally represented in relevant sections and tabs.
- Where tabs or pivots are used (e.g., '?tabs=windows'), provide equivalent Linux and macOS tabs, and consider making the default tab platform-neutral or based on user agent detection.
- Explicitly mention cross-platform tools and workflows (such as using the Azure CLI or REST API) alongside any platform-specific instructions.
- Review all linked tutorials to ensure Linux users are not disadvantaged or required to adapt Windows-specific steps.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page 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 command-line examples are provided, and the only tool explicitly referenced is Windows-centric. This may make Linux or macOS users feel unsupported or unclear about how to proceed.
Recommendations
- Mention cross-platform HTTP clients such as curl or HTTPie alongside PowerShell.
- Provide example commands for both PowerShell and curl to demonstrate how to make the POST request on different platforms.
- Explicitly state that any HTTP client can be used, and provide at least one example for a non-Windows environment.
- Consider including a table or section listing common tools for Windows, Linux, and macOS to ensure parity.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio as the first development environment and not providing explicit Linux-specific instructions or examples. While Visual Studio Code is mentioned (which is cross-platform), there are no explicit Linux or macOS setup or run instructions, nor are there any terminal commands or troubleshooting tips specific to non-Windows environments. All examples and guidance assume a Windows-like environment, especially in terms of file paths and tool usage.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and throughout the guide.
- Provide Linux/macOS-specific instructions for installing .NET SDK, running the sample, and handling file paths.
- Include terminal commands for building and running the application using the dotnet CLI, not just via Visual Studio or Visual Studio Code GUIs.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, HTTPS certificates, path length differences).
- Ensure screenshots and file path examples are not Windows-specific, or provide alternatives for other platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-protection-investigate-risk.md
...-directory-b2c/identity-protection-investigate-risk.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Microsoft-specific tools and APIs (Azure portal, Microsoft Graph PowerShell SDK) without mentioning or providing parity for Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the only programmatic example references PowerShell, which is traditionally associated with Windows, though it is now cross-platform. There is no mention of Linux command-line tools or workflows.
Recommendations
- Explicitly mention that Microsoft Graph PowerShell SDK is cross-platform and provide installation/use instructions for Linux/macOS.
- Include examples using Microsoft Graph API with curl or other command-line tools available on Linux.
- Clarify that the Azure portal is web-based and accessible from any OS.
- Provide parity in programmatic examples by including both PowerShell and bash/curl (or Python) snippets.
- Avoid implying that PowerShell is the only or primary automation method; highlight REST API usage as a first-class option.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page 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). There are no command-line examples provided, and the only tool referenced is Windows-centric. This may make Linux or macOS users feel unsupported or require them to infer how to perform the same actions on their platforms.
Recommendations
- When suggesting HTTP clients for testing, include cross-platform tools such as curl or HTTPie alongside PowerShell.
- Provide explicit command-line examples using curl for making the POST request to obtain an access token.
- If referencing PowerShell, clarify that it is available cross-platform, or provide both Windows and Linux/macOS instructions/examples.
- Ensure that any tool recommendations or examples are inclusive of all major operating systems, not just Windows.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio as the primary IDE and not providing explicit Linux instructions or examples for running the sample application. While Visual Studio Code is mentioned (which is cross-platform), there are no Linux-specific setup or troubleshooting notes, and the workflow assumes a Windows-like environment (e.g., path length limitations, default use of localhost ports, and Visual Studio usage). There are no PowerShell or Windows command-line examples, but the absence of Linux-specific guidance or parity in tooling is notable.
Recommendations
- Explicitly mention Linux as a supported development environment in the prerequisites.
- Provide Linux-specific instructions for installing .NET SDK, running the sample app, and handling common issues (such as port binding or file permissions).
- Include example commands for running the application from the terminal (e.g., using `dotnet run`) in addition to or instead of relying on Visual Studio/VS Code UI.
- Clarify any platform-specific considerations (such as path length limits, which may differ on Linux).
- If screenshots are included, provide examples from both Windows and Linux environments where relevant.