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 326-350 of 392 flagged pages
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
Windows First
Summary
The documentation is generally platform-neutral, focusing on HTTP requests and OAuth 2.0 protocol details. However, there is a subtle Windows bias where Microsoft PowerShell is mentioned as an example HTTP client for testing POST requests, with no mention of Linux or cross-platform alternatives. Additionally, the only specific tool mentioned for making HTTP requests is PowerShell, which is primarily associated with Windows, and it is mentioned before any Linux or cross-platform equivalents.
Recommendations
- When suggesting HTTP clients for testing, mention cross-platform and Linux tools such as curl, HTTPie, or Postman alongside or before PowerShell.
- Provide example commands using curl or HTTPie to demonstrate how to perform the HTTP requests on Linux and macOS systems.
- Explicitly state that any HTTP client can be used, and provide at least one example for both Windows (PowerShell) and Linux/macOS (curl).
- Avoid implying that PowerShell is the default or only tool for these tasks, and ensure parity in tool recommendations across platforms.
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 →
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, and by using a sample configuration (e.g., redirect URI to https://localhost:44316) that aligns with default Windows/IIS Express ports. There are no explicit Linux or cross-platform instructions, nor are there terminal or deployment examples for Linux environments. The documentation does not mention Linux-specific tools, commands, or troubleshooting steps, and does not address potential differences in file paths or environment setup for Linux users.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites, and provide guidance for installing .NET SDK and running ASP.NET Core apps on those systems.
- Include Linux/macOS-specific instructions for extracting the sample, running the app (e.g., using the dotnet CLI), and troubleshooting common issues (such as port conflicts or permissions).
- Provide examples of configuring the redirect URI for common Linux development environments (e.g., using ports commonly available on Linux, or referencing Kestrel rather than IIS Express).
- Add notes about differences in file paths, environment variables, and permissions between Windows and Linux/macOS.
- Where Visual Studio is mentioned, clarify that Visual Studio Code and the dotnet CLI are fully supported on Linux/macOS, and provide parity in example steps.
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 provides cross-platform instructions, with separate command examples for Linux, macOS, and Windows. However, there is evidence of subtle Windows bias: (1) The instruction to extract the sample to a folder with a path length of 260 or fewer characters references a Windows-specific limitation without clarifying that this is not relevant on Linux/macOS; (2) The Windows command examples use 'py' instead of 'python', which is a Windows launcher, and this is presented after Linux/macOS, but the path length warning is not platform-scoped.
Recommendations
- Clarify that the 260-character path length limitation applies only to Windows, and is not relevant for Linux/macOS users.
- Consider providing a brief note about the 'py' launcher being specific to Windows, and that 'python' is the standard command on Linux/macOS.
- Where platform-specific limitations or tools are mentioned, explicitly scope them to the relevant OS to avoid confusion.
- Continue to provide parity in command examples for all major platforms, and ensure that any warnings or notes are clearly attributed to the appropriate OS.
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 is heavily focused on ASP.NET Core and C# code, which are most commonly associated with Windows development environments. There are no examples or instructions for Linux or cross-platform development environments, nor are there mentions of Linux-specific tools or deployment patterns. The documentation assumes the use of Visual Studio project structures and .NET conventions, which may not be as familiar or accessible to Linux-first developers.
Recommendations
- Add explicit notes or sections on how to perform the same configuration and development steps on Linux, including using .NET Core/ASP.NET Core on Linux.
- Provide command-line examples (e.g., using dotnet CLI) for project setup, configuration, and running the application, which are platform-agnostic.
- Mention and link to cross-platform development tools (such as VS Code, JetBrains Rider, or the dotnet CLI) alongside or instead of Windows-centric tools.
- Clarify that the instructions and code samples are applicable on both Windows and Linux, and highlight any platform-specific considerations.
- Include troubleshooting tips or environment setup instructions for Linux users, such as installing the .NET SDK on Ubuntu or other distributions.
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 using terminology like 'command prompt' and 'Visual Studio Marketplace'. There are no explicit Linux or cross-platform CLI examples, nor are alternative Linux development tools or workflows mentioned. The instructions for running and deploying the API assume a Windows-centric workflow, with no mention of Linux-specific steps or considerations.
Recommendations
- Include explicit instructions for Linux users, such as using the terminal and cross-platform CLI tools (e.g., Azure CLI, Bash).
- Mention and provide examples for deploying Azure Functions using the Azure CLI or from a Linux environment.
- Reference cross-platform editors (such as VS Code) in a way that highlights their availability on Linux, and avoid assuming Visual Studio Code is used in a Windows context.
- Replace or supplement references to 'command prompt' with 'terminal' or 'shell', and clarify that all steps work on both Windows and Linux.
- Add notes or sections for Linux/macOS users, especially for environment variable management and local development.
- Ensure screenshots and terminology are not Windows-specific where possible, or provide Linux equivalents.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-generic-saml-options.md
...irectory-b2c/identity-provider-generic-saml-options.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, the recommended tools for debugging SAML flows include browser extensions for Chrome and Firefox, but the only OS-specific developer tools mentioned are 'Microsoft Edge or Internet Explorer developer tools', with a link to a Microsoft blog. There is no mention of Linux-native tools or command-line utilities for SAML debugging, and the order of mention puts Microsoft/Windows tools last but still includes them exclusively as the only OS-specific developer tool. No PowerShell or Windows command-line examples are present, but the lack of Linux-specific tool recommendations is a subtle form of Windows bias.
Recommendations
- Add recommendations for Linux-native SAML debugging tools, such as 'SAMLtool' (https://www.samltool.com/) or command-line utilities like 'curl' and 'xmlsec1' for inspecting and signing SAML messages.
- Mention that browser-based tools (Chrome/Firefox extensions) are cross-platform and highlight this fact for Linux and macOS users.
- If referencing developer tools, include instructions or links for using browser developer tools on Linux and macOS, not just Microsoft Edge/IE.
- Consider including a note that all XML configuration steps are OS-agnostic and can be performed on any platform.
- If any scripts or automation are added in the future, provide both Windows (PowerShell) and Linux (bash/shell) examples.
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, focusing on HTTP requests and OAuth 2.0 protocol details. However, there is a subtle Windows bias in the section suggesting 'Microsoft PowerShell' as an example HTTP client for testing POST requests, without mentioning Linux or cross-platform alternatives. No Linux-specific tools (such as curl or httpie) are referenced, and no Linux command-line examples are provided.
Recommendations
- When suggesting tools for testing HTTP requests, mention cross-platform and Linux-native tools such as 'curl' or 'httpie' alongside PowerShell.
- Provide example commands using 'curl' or 'httpie' for Linux/macOS users in addition to any PowerShell examples.
- Explicitly state that any HTTP client can be used, and offer at least one example for both Windows and Linux environments.
- Review other documentation pages for similar subtle tool recommendations and ensure Linux parity throughout.
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-first bias by focusing exclusively on ASP.NET (a Microsoft technology) and development environments like Visual Studio and Visual Studio Code, but does not provide explicit instructions or examples for Linux users. There are no references to Linux-specific tools, shell commands, or deployment considerations, and the prerequisites and steps assume a Windows-centric workflow.
Recommendations
- Include explicit instructions for running the sample on Linux, such as using the .NET CLI (dotnet run) in a terminal.
- Provide Linux-specific prerequisites, such as installation steps for .NET SDK on Ubuntu or other distributions.
- Mention and show examples of using editors and tools common on Linux (e.g., JetBrains Rider, Vim, or Emacs) in addition to Visual Studio and VS Code.
- Clarify that Visual Studio Code and the .NET SDK are cross-platform, and provide any necessary Linux-specific configuration notes (e.g., HTTPS development certificates).
- Add troubleshooting tips for common Linux issues, such as file permissions or path length differences.
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 demonstrates mild Windows bias. While it provides separate command examples for Linux, macOS, and Windows when running the sample app, there are subtle indications of Windows-first thinking. Notably, the instruction to 'Extract the sample file to a folder where the total length of the path is 260 or fewer characters' references the Windows MAX_PATH limitation, which is not relevant to Linux/macOS. Additionally, the Windows example uses 'py' instead of 'python', which is a Windows-specific launcher. However, the documentation does provide parity in command examples for all platforms and does not omit Linux/macOS instructions.
Recommendations
- Clarify that the 260-character path length limitation applies only to Windows, and that Linux/macOS users are not affected.
- Consider listing Linux/macOS examples before Windows, or in parallel, to avoid a Windows-first impression.
- Where possible, use cross-platform commands (e.g., 'python' instead of 'py') in generic instructions, and explain platform-specific differences in a note.
- Review the documentation for any other implicit Windows assumptions (such as file path separators, environment variable syntax, etc.) and clarify or provide Linux/macOS equivalents as needed.
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 is heavily focused on ASP.NET Core and C# development patterns, which are traditionally associated with Windows environments. There are no explicit instructions, examples, or notes for Linux or cross-platform development, and all file references and code samples (e.g., Startup.cs, appsettings.json) assume a .NET/Windows-centric workflow. There is no mention of Linux-specific tools, deployment, or configuration steps.
Recommendations
- Add explicit notes or sections clarifying that ASP.NET Core is cross-platform and can be developed and deployed on Linux and macOS, not just Windows.
- Include Linux/macOS equivalents for file paths, command-line instructions, and environment setup (e.g., using bash instead of PowerShell, using environment variables in Linux).
- Provide examples or links for deploying and running ASP.NET Core applications on Linux (e.g., using systemd, Nginx/Apache reverse proxy).
- Mention cross-platform development tools (e.g., Visual Studio Code, JetBrains Rider) in addition to Visual Studio.
- If referencing Windows-specific tools or patterns, ensure Linux alternatives are mentioned with equal prominence.
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 focuses exclusively on ASP.NET Core development, which is cross-platform, but the examples and instructions implicitly assume a Windows development environment. There are no explicit Linux or macOS instructions, and the tooling references (such as Visual Studio and Visual Studio Code) are presented in a way that prioritizes Windows workflows. Package installation commands for Visual Studio Code use Install-Package, which is a PowerShell/NuGet Package Manager Console command, not a cross-platform dotnet CLI command. There are no mentions of Linux-specific considerations, file paths, or development environments.
Recommendations
- Provide explicit instructions and examples for Linux and macOS environments, including terminal commands and any OS-specific prerequisites.
- Use cross-platform commands (such as 'dotnet add package') consistently in all tooling sections, especially for Visual Studio Code, which is widely used on Linux/macOS.
- Mention and show file paths in both Windows (\) and Unix (/) formats where relevant.
- Include a note or section on running and debugging the application on Linux/macOS, including any differences in launching the development server or accessing localhost.
- Clarify that ASP.NET Core and the Microsoft Identity Web libraries are fully supported on Linux and macOS, and provide links to relevant cross-platform documentation.
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 focused exclusively on ASP.NET Core web apps, which are cross-platform, but the only development environments mentioned are Visual Studio and Visual Studio Code. The package installation instructions are split between 'Visual Studio' (using dotnet CLI) and 'Visual Studio Code' (using Install-Package), but both are available cross-platform. However, there are no explicit instructions or examples for Linux or macOS users, such as using terminal/bash, nor is there any mention of Linux-specific tooling or considerations. The documentation implicitly assumes a Windows-centric development environment by referencing Visual Studio and Windows-style file paths (e.g., Views\Shared\_Layout.cshtml).
Recommendations
- Add explicit instructions or notes for Linux and macOS users, including any differences in file paths, commands, or environment setup.
- Include examples using bash or terminal commands for package installation and project creation, not just Visual Studio/Visual Studio Code.
- Mention cross-platform compatibility of ASP.NET Core and clarify that all steps can be performed on Linux/macOS as well as Windows.
- Use platform-neutral file path notation (e.g., Views/Shared/_Layout.cshtml) throughout the documentation.
- If referencing IDEs, include cross-platform options such as JetBrains Rider or command-line editors (vim, nano) alongside Visual Studio and Visual Studio Code.
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
Missing Linux Example
Windows First
Summary
The documentation exclusively describes steps using the Azure portal web interface and does not provide any command-line examples. There is no mention of platform-specific tools, but where command-line or automation might be relevant (e.g., scripting registration or configuration), no examples are given for either Windows (PowerShell) or Linux (CLI). However, the overall workflow and terminology (e.g., 'click', 'select', 'portal') are more familiar to users of Windows environments and Azure's web UI, which is often associated with Windows-centric workflows. There is no mention of Azure CLI or cross-platform automation, and no Linux-specific guidance or parity.
Recommendations
- Provide Azure CLI examples for all steps that can be automated, including application registration, client secret creation, and identity provider configuration.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
- Where possible, include both GUI and CLI instructions side-by-side, so Linux and automation-focused users are equally supported.
- Reference documentation for scripting or automating these tasks on Linux/macOS as well as Windows.
- If PowerShell or Windows tools are ever referenced, ensure equivalent Bash/Azure CLI examples are provided.
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 Android or other platforms, and no Linux or cross-platform biometric solutions are discussed. There are no Linux-specific examples or references to Linux-compatible biometric tools.
Recommendations
- Include explicit references to biometric authentication options available on Linux (e.g., fprintd, libfprint, or desktop environment integrations) alongside Windows Hello and Android.
- Provide example scenarios or walkthroughs for enrolling and using biometrics on Linux devices, not just Windows and Android.
- Use neutral, platform-agnostic language when describing biometric authentication, mentioning Windows Hello, Android biometrics, and Linux solutions together.
- If possible, add troubleshooting or support notes for Linux users to ensure parity with Windows and Android guidance.
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 the use of the Azure portal, terminal, or command prompt without explicitly referencing Linux or cross-platform alternatives. There are no explicit Linux-specific instructions, examples, or screenshots, and no mention of Linux-native tools or shell environments. All environment variable and deployment steps are described generically or with a Windows-centric perspective, omitting Linux-specific guidance.
Recommendations
- Explicitly mention that Visual Studio Code and Azure Functions Core Tools are cross-platform and provide installation links for Linux and macOS.
- Include Linux-specific instructions or examples for running and deploying Azure Functions, such as using bash/zsh shells and common Linux package managers.
- Show how to set environment variables in Linux (e.g., export commands or .env files) in addition to the local.settings.json approach.
- Add screenshots or terminal snippets from Linux environments to demonstrate parity.
- Clarify that the Azure portal and related tools are accessible from any OS, and provide links to CLI-based alternatives (e.g., Azure CLI) with Linux usage examples.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-onfido.md
...b/main/articles/active-directory-b2c/partner-onfido.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Visual Studio as the publishing tool for the API and suggesting Azure Storage Explorer for managing Azure storage, both of which are traditionally Windows-centric tools. No Linux-specific tools or cross-platform alternatives are mentioned, and there are no command-line examples (e.g., Azure CLI, PowerShell, Bash) for Linux users. The documentation does not provide explicit instructions or examples for Linux environments.
Recommendations
- Include instructions for deploying the API using cross-platform tools such as the Azure CLI, .NET CLI, or GitHub Actions, in addition to Visual Studio.
- Mention and provide examples for using Azure Storage Explorer on Linux, or suggest alternative methods such as the Azure CLI or azcopy for uploading files to blob storage.
- Add command-line examples for common tasks (e.g., uploading files, configuring CORS) using tools available on Linux.
- Explicitly state that the steps can be performed on Linux, macOS, or Windows, and highlight any platform-specific considerations.
- Where GUI tools are referenced, provide equivalent command-line or cross-platform alternatives.
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 shows mild Windows bias by referencing 'windows' explicitly in the SAML application registration link (saml-service-provider.md?tabs=windows), suggesting that Windows is the default or primary environment. There are no explicit Linux or cross-platform examples or tabs mentioned, and no Linux-specific tools or instructions are provided.
Recommendations
- Wherever platform-specific instructions or tabs are provided (such as for SAML apps), ensure that Linux (and macOS, if relevant) tabs/examples are available and mentioned equally.
- Avoid using Windows as the default or only tab in links; instead, provide a neutral or cross-platform default, or mention all supported platforms.
- Explicitly state when instructions are cross-platform, or provide clear guidance for both Windows and Linux users.
- Review linked tutorials to ensure parity in examples, screenshots, and command-line instructions for both Windows and Linux environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-manage-administrator.md
...irectory-b2c/tenant-management-manage-administrator.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes management tasks using the Azure Portal web interface, with no mention of command-line tools or automation. However, where command-line or scripting might be relevant (e.g., bulk user creation, role assignment, or auditing), there are no examples for PowerShell, CLI, or any platform-specific tools. The only interface described is the Azure Portal, which is cross-platform via browser, but the documentation implicitly assumes a GUI-first, Windows-centric workflow by not mentioning or providing parity for Linux or cross-platform automation tools (such as Azure CLI or REST API). There are no explicit Windows-only tools, but the lack of CLI or automation examples can disadvantage Linux users who may prefer or require non-GUI workflows.
Recommendations
- Add examples using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
- Where appropriate, provide PowerShell examples alongside Azure CLI, but do not make PowerShell the only automation example.
- Include REST API references or examples for tasks that can be automated, to support users on any platform.
- Explicitly mention that all tasks can be performed via browser on any OS, but also provide links or examples for automation and scripting.
- For bulk operations (e.g., user creation), provide sample scripts or commands for both Azure CLI and PowerShell.
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 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 for Linux or macOS users, and the only tool explicitly referenced is Windows-centric.
Recommendations
- Provide equivalent command-line examples using curl or HTTPie, which are available on Linux, macOS, and Windows.
- Mention cross-platform tools (e.g., curl, Postman) alongside PowerShell when suggesting ways to test HTTP requests.
- If including PowerShell examples, also include Bash/curl examples to ensure parity for Linux/macOS users.
- Consider rephrasing to say 'any HTTP client such as curl, HTTPie, Postman, or PowerShell' to avoid implying a Windows-only approach.
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 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 such as curl or HTTPie. No Linux-specific tools or shell examples are provided.
Recommendations
- When suggesting tools for testing HTTP requests, mention cross-platform and Linux-native tools such as curl and HTTPie alongside PowerShell.
- Provide example command lines for both Windows (PowerShell) and Linux/macOS (bash/curl) when demonstrating how to make HTTP requests.
- Explicitly state that the HTTP requests can be tested using any HTTP client, and provide at least one example for each major platform.
- Avoid implying that PowerShell is the default or only option for testing HTTP requests.
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 contains a subtle Windows bias by linking to instructions for securing REST APIs that default to a 'windows' tab (e.g., 'secure-rest-api.md?tabs=windows'), without mentioning or providing equivalent Linux/macOS guidance. There are no explicit PowerShell or Windows command-line examples, but the referenced documentation may prioritize Windows tooling or workflows. No Linux-specific tools, commands, or parity notes are present.
Recommendations
- Wherever documentation links reference platform-specific instructions (such as 'secure-rest-api.md?tabs=windows'), ensure that Linux/macOS tabs are equally visible and referenced. Consider linking to a neutral or multi-platform version of the page.
- Explicitly mention that the guidance applies to all platforms, and provide Linux/macOS equivalents or note when steps are platform-agnostic.
- If any referenced workflows (such as API protection or token acquisition) have platform-specific steps, include both Windows and Linux/macOS examples inline or as expandable sections.
- Review all linked documentation to ensure Linux users are not disadvantaged or forced to adapt Windows-centric instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but it references the Azure portal and Azure CLI for configuration. However, there is a subtle Windows-first bias: the documentation does not explicitly mention Linux or provide Linux-specific guidance or examples, and the Azure CLI (which is cross-platform) is only mentioned in passing, with no concrete CLI commands or shell examples. The instructions and screenshots are oriented toward the Azure portal, which is platform-agnostic, but there is no effort to ensure Linux parity or to highlight cross-platform workflows.
Recommendations
- Add explicit Azure CLI command examples for all configuration steps, including app registration and setting application secrets, and show these commands in both Windows (cmd/PowerShell) and Linux (bash) syntax where relevant.
- Include a note or section confirming that all steps can be performed from Linux, macOS, or Windows, and provide links to cross-platform CLI documentation.
- If screenshots are provided, clarify that the Azure portal is accessible from any OS.
- Where file paths or environment variables are referenced, show both Windows and Linux conventions.
- Consider adding a troubleshooting section for common Linux-specific issues (e.g., file permissions, line endings, CLI installation).
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 demonstrates a mild Windows bias. While it provides Linux, macOS, and Windows command examples for running the sample app, there are subtle indications of Windows-centric assumptions: the warning about path length ("Extract the sample file to a folder where the total length of the path is 260 or fewer characters") is a Windows-specific limitation, and the Windows example is listed last but uses the Windows-specific 'py' launcher. However, all platforms are represented in the run instructions, and there are no PowerShell-only commands or exclusive references to Windows tools.
Recommendations
- Clarify that the 260-character path length limitation applies only to Windows, and that Linux/macOS users are not affected.
- Consider listing Linux or macOS instructions first, or randomizing the order, to avoid implicit prioritization of Windows.
- Provide a note explaining the difference between 'python' and 'py' launchers, and suggest using 'python' on all platforms if possible for consistency.
- Ensure any screenshots or UI references are cross-platform or clarify when they are Windows-specific.
- Continue to provide explicit, parallel instructions for all major platforms (Linux, macOS, Windows) in future updates.
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 page demonstrates a bias toward Windows development environments by focusing exclusively on Visual Studio and Visual Studio Code as prerequisites and editors, with no mention of Linux-specific tools, distributions, or command-line instructions. All examples and instructions are editor-agnostic but implicitly assume a Windows or cross-platform environment without addressing Linux-specific setup, such as package installation, path length limitations, or running .NET applications on Linux. There are no PowerShell-specific commands, but the lack of explicit Linux parity (e.g., mentioning Linux package managers, terminal commands, or troubleshooting) constitutes a subtle bias.
Recommendations
- Explicitly mention that Visual Studio Code and .NET SDK are cross-platform and provide links or instructions for Linux installation (e.g., using apt, yum, or snap).
- Include a Linux-specific section in the prerequisites, listing supported distributions and any additional dependencies (such as libssl-dev for .NET on Linux).
- Address path length limitations as they relate to both Windows and Linux, clarifying if the 260-character limit is a Windows-specific constraint.
- Provide example terminal commands for building and running the .NET projects on Linux (e.g., using dotnet CLI in Bash).
- Mention any known issues or differences when running the sample on Linux (such as file permissions, HTTPS development certificates, or case sensitivity in file paths).
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 demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code, and by using a sample path and port (https://localhost:44316) that are typical defaults for Visual Studio on Windows. There are no explicit instructions or examples for running the sample on Linux (e.g., using the dotnet CLI, configuring HTTPS certificates, or handling path length limitations on Linux filesystems). No Linux-specific tools, commands, or troubleshooting tips are provided.
Recommendations
- Provide explicit instructions for running the sample on Linux, including using the dotnet CLI (e.g., 'dotnet run') and handling HTTPS development certificates.
- Mention any Linux-specific prerequisites, such as installing .NET SDK on Ubuntu or other distributions.
- Clarify that Visual Studio Code is cross-platform and provide example commands for both Windows and Linux environments.
- Address path length limitations as they relate to both Windows and Linux, or clarify if this is only a Windows concern.
- Include troubleshooting tips for common Linux issues, such as permissions or certificate trust.
- When listing prerequisites, present cross-platform tools (like Visual Studio Code and dotnet CLI) before or alongside Windows-specific tools.