Active Directory B2C
566
Total Pages
521
Linux-Friendly Pages
45
Pages with Bias
8.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
101 issues found
Showing 76-100 of 101 flagged pages
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md
...ctory-b2c/custom-policies-series-sign-up-or-sign-in.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation requires Visual Studio Code (VS Code) as a prerequisite, but does not specify that it is cross-platform or mention any Linux-specific setup or alternatives. There are no command-line examples, but all tool references (e.g., VS Code, Azure Portal) are platform-agnostic except for the implicit assumption that VS Code is installed, which may be interpreted as a Windows-centric tool by some users. No explicit Linux or macOS instructions or screenshots are provided, and no mention is made of Linux-specific considerations.
Recommendations
- Clarify that Visual Studio Code is available on Windows, Linux, and macOS, and provide installation links for all platforms.
- Explicitly mention that all steps can be performed on Linux and macOS, not just Windows.
- If any command-line steps are added in the future, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Include a note or section addressing any platform-specific differences, even if minimal, to assure Linux users of parity.
- Consider providing screenshots or terminal snippets from Linux environments where relevant.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-wpf-desktop-app-options.md
...y-b2c/enable-authentication-wpf-desktop-app-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is exclusively focused on WPF desktop applications, which are Windows-only. All code samples are in C# and tailored for WPF, with no mention of Linux or cross-platform desktop frameworks. There are no examples or guidance for Linux desktop applications or alternative frameworks (e.g., GTK#, Avalonia, Electron). The documentation assumes a Windows development environment and does not address Linux parity.
Recommendations
- Add equivalent examples for cross-platform desktop frameworks (e.g., Avalonia, Electron, GTK#) that run on Linux.
- Include guidance for configuring Azure AD B2C authentication in Linux desktop applications.
- Mention and provide code samples for MSAL usage in .NET Core/MAUI apps that can run on Linux.
- Clarify in the introduction that the guidance is Windows-specific, and link to cross-platform alternatives if available.
- If possible, provide parity in documentation for Linux and macOS desktop environments, including redirect URI configuration and authentication flows.
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 web applications and development workflows typical of Windows environments. All code and tooling examples assume .NET Core usage, but the only IDEs mentioned are Visual Studio and Visual Studio Code, with package installation commands given for both. However, the Visual Studio Code example uses Install-Package, which is a PowerShell/NuGet CLI command not natively available on Linux/macOS terminals. There is no explicit mention of Linux or macOS development environments, nor are there instructions for running the app outside of Windows (e.g., using bash, configuring HTTPS certificates on Linux, or using cross-platform .NET CLI commands for package management). The documentation does not mention Linux-specific considerations, such as file paths, shell commands, or troubleshooting steps for non-Windows platforms.
Recommendations
- Add explicit instructions and examples for Linux/macOS environments, including using bash/zsh shells and .NET CLI commands for package installation and running the app.
- Clarify that Visual Studio Code is cross-platform and provide package installation commands using 'dotnet add package' for all platforms, rather than 'Install-Package' which is PowerShell-specific.
- Include notes on file path differences (e.g., '/' vs '\') and HTTPS certificate setup for Linux/macOS.
- Mention any platform-specific prerequisites or troubleshooting steps for running ASP.NET Core apps on Linux/macOS.
- Ensure parity in documentation by listing Linux/macOS instructions alongside Windows, rather than only referencing Windows tools and patterns.
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 bias by focusing exclusively on ASP.NET web applications, which are traditionally associated with Windows development. The instructions and examples assume the use of Visual Studio and Visual Studio Code, both of which are more commonly used on Windows. There is no mention of Linux-specific development environments, nor are there any examples or guidance for running the application on Linux (e.g., using the dotnet CLI on Linux, configuring for nginx or Apache, or troubleshooting Linux-specific issues). Package installation examples use dotnet CLI and Install-Package, but do not clarify cross-platform usage or provide parity for Linux users.
Recommendations
- Add explicit instructions for setting up and running the ASP.NET Core app on Linux (e.g., Ubuntu), including prerequisites like installing the .NET SDK on Linux.
- Include examples of using the dotnet CLI on Linux terminals (bash/zsh), and clarify that the dotnet commands work cross-platform.
- Mention alternative editors such as JetBrains Rider or simply using VS Code on Linux, and provide guidance for Linux users.
- Provide troubleshooting tips or notes for common Linux-specific issues (e.g., file permissions, HTTPS certificate setup for localhost).
- Clarify that ASP.NET Core is cross-platform and can be developed and hosted on Linux, macOS, and Windows.
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 exclusively provides examples and instructions for ASP.NET Core applications, which are traditionally associated with Windows environments. There are no platform-specific instructions, but the use of .NET, C#, and references to files like Startup.cs and appsettings.json implicitly target Windows developers. There are no Linux-specific examples, nor any mention of cross-platform considerations (such as running on Linux, using bash, or deploying on non-Windows environments).
Recommendations
- Explicitly state that ASP.NET Core is cross-platform and can run on Linux, macOS, and Windows.
- Include instructions or examples for deploying and configuring the application on Linux (e.g., using systemd, configuring environment variables in bash, file paths).
- Mention any platform-specific considerations for file locations, permissions, or dependencies.
- Provide sample commands for both Windows (PowerShell/Command Prompt) and Linux (bash) where relevant, such as for environment setup or running the application.
- Reference Linux-friendly tools and workflows (e.g., using Visual Studio Code, dotnet CLI on Linux, Docker containers) alongside Windows equivalents.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant.md
...rectory-b2c/identity-provider-azure-ad-multi-tenant.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively references the Azure portal (web UI) for all configuration steps and does not provide any command-line examples (e.g., Azure CLI, PowerShell, or Bash). Where browser instructions are given, only Microsoft browsers (Edge, Chrome) are mentioned. There is no mention of Linux-specific tools, nor are there any examples or guidance for users working from Linux environments. The documentation assumes a GUI-first, Windows-centric workflow.
Recommendations
- Add Azure CLI examples for app registration, policy key creation, and claims provider configuration, alongside or in place of portal UI steps.
- Mention cross-platform browsers (e.g., Firefox) when suggesting private browsing for testing.
- Explicitly state that all steps can be performed from any OS (Windows, Linux, macOS) via the Azure portal, and clarify any OS-specific limitations if present.
- Provide sample scripts or commands for Linux users to automate or perform the same tasks described in the portal.
- If PowerShell is referenced in related content, ensure Azure CLI or Bash equivalents are provided.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-grit-iam.md
...main/articles/active-directory-b2c/partner-grit-iam.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation focuses exclusively on Azure AD B2C and Grit IAM integration, referencing Azure-specific tools and portals (which are primarily accessed via web interfaces or Microsoft-centric environments). There are no command-line examples, but all infrastructure and configuration guidance assumes use of Azure (a Microsoft platform), with no mention of Linux-specific workflows, tools, or alternative environments. There is no reference to Powershell, but the absence of Linux CLI, shell, or open-source tool examples constitutes a subtle Windows bias.
Recommendations
- Include examples or guidance for Linux users, such as using Azure CLI on Linux, or accessing Grit IAM via Linux-based environments.
- Mention cross-platform compatibility for portals and APIs, clarifying if they can be accessed from Linux or macOS systems.
- Provide sample scripts or automation steps using bash or other Linux-native tools, where relevant.
- Explicitly state any platform requirements or limitations, and offer alternatives for non-Windows users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/solution-articles.md
...ain/articles/active-directory-b2c/solution-articles.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by primarily referencing ASP.NET Core applications (which are historically Windows-centric, though now cross-platform) and omitting explicit examples or guidance for Linux environments. There are no mentions of Linux tools, shell commands, or Linux-specific development patterns. The training and solution guides do not clarify platform parity or provide Linux-focused instructions, potentially leaving Linux developers underserved.
Recommendations
- Include explicit examples for both Windows and Linux environments when demonstrating Azure AD B2C integration, such as showing configuration steps using Bash or Linux-native tools.
- Add references to Linux-compatible development stacks (e.g., Node.js, Python, Java) alongside ASP.NET Core.
- Clarify that Azure AD B2C can be used from Linux and provide links to cross-platform SDKs and documentation.
- Ensure downloadable guides and training materials mention platform-agnostic approaches or provide separate sections for Windows and Linux users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-emergency-access-account.md
...tory-b2c/tenant-management-emergency-access-account.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Azure Portal (web UI) instructions and does not reference any command-line tools or scripts. However, where command-line or automation might be expected (e.g., PowerShell, CLI), there are no examples for either Windows or Linux. The only implicit bias is that, in Azure documentation, PowerShell or Windows tools are often mentioned first or exclusively, but here, no CLI tools are mentioned at all. There is a slight 'windows_first' bias in the language (e.g., 'Sign in to the Azure portal' is a common pattern in Microsoft docs, and there is no mention of Azure CLI or cross-platform automation). There are no Linux-specific instructions or parity suggestions.
Recommendations
- Add Azure CLI examples for creating emergency access accounts, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- If PowerShell automation is relevant, provide equivalent Bash or Azure CLI scripts.
- Explicitly mention that the Azure Portal is web-based and accessible from any OS, to clarify cross-platform compatibility.
- Include a section or note on how to perform these tasks using automation tools suitable for Linux environments.
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 references to Linux-specific tools, patterns, or deployment instructions, nor are there examples or guidance for developers working on Linux or cross-platform environments. No PowerShell or Windows-only tools are mentioned, but the overall approach and examples implicitly favor Windows by omitting Linux or cross-platform considerations.
Recommendations
- Add explicit notes or sections on how to configure and run ASP.NET Core applications on Linux (e.g., using dotnet CLI, configuring appsettings.json, and Startup.cs on Linux).
- Include examples or links for deploying and managing Azure AD B2C-enabled web apps on Linux environments (such as Ubuntu or CentOS), including common Linux workflows.
- Mention cross-platform development tools (e.g., Visual Studio Code, JetBrains Rider) and provide instructions for both Windows and Linux users.
- If any command-line instructions are needed, provide both Windows (PowerShell/CMD) and Linux (bash) equivalents.
- Clarify that ASP.NET Core is cross-platform and can be developed and deployed on Linux, macOS, and Windows.
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 and Visual Studio tooling, which are primarily used on Windows. The only explicit environment-specific instructions are for Visual Studio and Visual Studio Code, with no mention of Linux or macOS equivalents. There are no examples or guidance for running, building, or troubleshooting the application on Linux (e.g., using bash shell, Linux package managers, or Linux-specific .NET development patterns). The command-line instructions and project structure assume a Windows-centric workflow.
Recommendations
- Add explicit instructions and examples for Linux users, such as using bash/zsh shells and common Linux distributions.
- Include guidance for installing .NET SDK and running the application on Linux (e.g., using apt, yum, or snap).
- Provide parity in tooling instructions, such as using VS Code on Linux, JetBrains Rider, or the dotnet CLI exclusively.
- Clarify that the dotnet CLI commands are cross-platform, and provide any Linux/macOS-specific notes where necessary (e.g., file paths, environment variables).
- Mention how to run and debug the ASP.NET application on Linux (e.g., using 'dotnet run' in a terminal, opening localhost URLs, handling HTTPS certificates on Linux).
- If referencing Visual Studio, always include equivalent instructions for Linux-friendly tools and make it clear that the workflow is cross-platform.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-application-options.md
...y-b2c/enable-authentication-web-application-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric development tools and workflows, such as Visual Studio and C#/.NET, without mentioning or providing examples for Linux or cross-platform development environments. There are no instructions or examples for Linux users, such as using VS Code, command-line tools, or alternative project setup methods. All code snippets and project guidance assume a Windows/Visual Studio context.
Recommendations
- Include instructions for setting up and configuring Azure AD B2C authentication in cross-platform environments, such as using VS Code or JetBrains Rider on Linux.
- Provide equivalent command-line instructions (e.g., dotnet CLI) for creating controllers and modifying project files, rather than relying solely on Visual Studio's GUI.
- Clarify that the .NET Core/ASP.NET Core stack is cross-platform and can be used on Linux and macOS, and provide links or notes for Linux/macOS-specific setup.
- Add examples or notes for editing configuration files and running the application on Linux (e.g., using nano/vim for appsettings.json, running dotnet run, etc.).
- Avoid language that assumes Visual Studio or Windows as the default environment; mention alternatives and ensure parity in guidance.
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 page is largely platform-neutral, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, it lists browser extensions for Chrome and Firefox, but when mentioning built-in developer tools, it only references Microsoft Edge and Internet Explorer (both Windows browsers), with no mention of Linux or macOS equivalents (e.g., Chrome DevTools, Firefox Developer Tools). This subtly prioritizes Windows tools and omits Linux-native options.
Recommendations
- When referencing browser developer tools, mention Chrome DevTools and Firefox Developer Tools explicitly, as these are cross-platform and available on Linux.
- If providing links or instructions for built-in browser tools, include those for Chrome and Firefox, not just Edge/IE.
- Where possible, avoid referencing only Windows-specific browsers or tools. If a tool is Windows-only, clarify that and suggest Linux alternatives.
- Consider adding a note that all XML and SAML configuration steps are platform-agnostic and can be performed on any OS.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Azure portal (a web-based GUI) for all steps and does not provide any command-line examples. There is no mention of cross-platform CLI tools (such as Azure CLI or Microsoft Graph CLI), nor are there any PowerShell or Windows-specific commands. However, by omitting CLI-based instructions, the documentation implicitly favors Windows/GUI workflows, which are more common in Windows environments, and does not address Linux or automation-focused users who may prefer or require CLI/scripted approaches.
Recommendations
- Add Azure CLI examples for application registration, permission assignment, and role assignment, as Azure CLI is cross-platform and widely used on Linux.
- Include Microsoft Graph CLI or REST API examples for relevant operations, enabling automation and parity for Linux and macOS users.
- Explicitly mention that all steps can be performed via CLI and provide links or code snippets for these alternatives.
- Ensure that any references to tools or workflows are balanced between GUI and CLI, and clarify platform compatibility where relevant.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/page-layout.md
...blob/main/articles/active-directory-b2c/page-layout.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through references to Microsoft Edge and Internet Explorer compatibility, and mentions of features (such as saving passwords to iCloud Keychain) that are platform-specific. There are no explicit Linux or cross-platform examples, and browser compatibility fixes are described in terms of Windows browsers first (Edge, IE11), with no mention of Linux browsers or environments. No PowerShell or Windows command-line examples are present, but the focus on Windows browser compatibility and terminology suggests a Windows-centric perspective.
Recommendations
- Include explicit references to Linux and macOS browser compatibility (e.g., Firefox, Chrome on Linux/macOS) when discussing browser-specific features or fixes.
- Add examples or notes for developers working on Linux environments, such as testing with Linux browsers or using Linux-based development tools.
- Where browser compatibility is discussed, list non-Windows browsers/environments alongside Windows ones, or provide a compatibility matrix.
- Avoid assuming Windows as the default platform; use neutral language (e.g., 'major browsers' instead of 'Microsoft Edge and Internet Explorer').
- If platform-specific features are mentioned (e.g., iCloud Keychain), clarify their applicability and suggest alternatives for other platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing .NET and web.config (Windows-centric technologies) and providing configuration and deployment guidance only for Azure App Service, with no mention of Linux hosting, Linux deployment steps, or cross-platform alternatives. There are no examples or instructions for Linux environments, such as using environment variables, Linux-compatible certificate management, or deployment to Linux-based hosts.
Recommendations
- Add instructions for deploying the demo app on Linux-based hosts (e.g., Azure App Service for Linux, Docker, or other Linux web servers).
- Provide configuration examples using environment variables or appsettings.json, which are cross-platform, instead of only web.config.
- Include certificate creation and management steps for Linux (e.g., using OpenSSL) alongside Windows instructions.
- Mention Linux-compatible .NET hosting and provide parity in deployment guidance.
- Clarify that the solution can be hosted on both Windows and Linux platforms, and provide links or steps for both.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-whoiam.md
...b/main/articles/active-directory-b2c/partner-whoiam.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows/Azure-centric bias by exclusively referencing Azure services, portals, and workflows, with no mention of Linux tools, command-line interfaces, or cross-platform deployment options. All configuration and testing steps assume use of the Azure Portal UI, which is most commonly accessed from Windows environments, and there are no CLI or automation examples (e.g., Azure CLI, Bash scripts) that would help Linux users. There are no references to Linux-specific tools or deployment scenarios.
Recommendations
- Add examples using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
- Include instructions for deploying BRIMS API and admin portal using command-line tools (e.g., Bash scripts, ARM templates, or Terraform) in addition to the Azure Portal.
- Mention that the Azure Portal and all Azure services can be accessed from any OS, and clarify that the tutorial is platform-agnostic.
- Provide troubleshooting steps or notes for Linux users, such as managing environment variables, file permissions, or using open-source tools.
- If any local development or testing is required, include instructions for both Windows and Linux environments.
Active Directory B2C
Set up OAuth 2.0 client credentials flow
.../active-directory-b2c/client-credentials-grant-flow.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias. It references PowerShell as the primary method for generating GUIDs and provides a PowerShell script as the first example for obtaining an access token. Windows tools and terminology are mentioned before cross-platform or Linux alternatives, though a cURL example is also provided. There is no explicit Linux/macOS example for GUID generation, and the scripting section leads with PowerShell.
Recommendations
- Include Linux/macOS command-line examples for GUID generation (e.g., `uuidgen` or `openssl rand -hex 16`).
- Present cURL (cross-platform) examples before or alongside PowerShell examples.
- Explicitly state that all steps can be performed on Linux/macOS and provide equivalent commands where relevant.
- Reference platform-agnostic online tools for tasks like GUID generation before mentioning Windows-specific tools.
- Add notes or sections for Linux/macOS users to clarify parity and any differences.
Active Directory B2C
Best practices for Azure AD B2C
...b/main/articles/active-directory-b2c/best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-centric tools (Visual Studio Code, Azure DevOps, VS Web Test) and listing them before or without mentioning Linux/macOS alternatives. Examples for testing mention Selenium and VS Web Test, but do not suggest Linux-friendly equivalents. There are no explicit PowerShell-heavy examples or Windows-only instructions, but the overall tooling focus is on Microsoft/Windows ecosystem products.
Recommendations
- Include examples and recommendations for Linux/macOS users, such as alternative editors (e.g., Vim, Sublime Text) and CI/CD tools (e.g., GitHub Actions, Jenkins) alongside Azure DevOps.
- When mentioning testing tools, suggest cross-platform options (e.g., Selenium, Cypress, Playwright) and clarify which are available on Linux/macOS.
- Explicitly state that Visual Studio Code and its extensions are available on Linux/macOS, and provide installation guidance for those platforms.
- Add notes or links for Linux/macOS users where Windows-centric tools are referenced, ensuring parity in guidance.
Active Directory B2C
Authorization code flow - Azure Active Directory B2C
...ticles/active-directory-b2c/authorization-code-flow.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, presenting HTTP requests and responses in a generic format. However, there is a notable Windows bias in the section '2. Get an access token', where Microsoft PowerShell is mentioned as an example HTTP client, with no mention of Linux/macOS alternatives. Additionally, the only explicit tool recommendation is Windows-centric and appears before any mention of cross-platform or Linux tools.
Recommendations
- When suggesting HTTP clients for testing requests, include cross-platform tools such as curl, httpie, or Postman alongside PowerShell.
- Explicitly mention that the HTTP requests can be executed from any OS using standard tools.
- Provide example commands for Linux/macOS environments (e.g., curl or wget) in addition to PowerShell.
- Avoid listing Windows tools first or exclusively when discussing generic tasks like sending HTTP requests.
Active Directory B2C
Enable authentication in a SPA application by using Azure Active Directory B2C building blocks
.../active-directory-b2c/enable-authentication-spa-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a slight Windows bias, particularly in the final step where the command shell instructions use PowerShell syntax (e.g., 'npm ./index.js') and the code block is explicitly marked as 'powershell'. There are no explicit Linux/macOS instructions or examples, nor is there mention of cross-platform command differences. Earlier steps use generic 'command shell' language and Node.js tooling, which are cross-platform, but the final run instructions may confuse Linux/macOS users.
Recommendations
- Replace or supplement PowerShell-specific commands with cross-platform equivalents (e.g., 'node index.js' instead of 'npm ./index.js').
- Use 'bash' or 'shell' code block syntax for generic commands, or provide both Windows and Linux/macOS command examples.
- Add a note clarifying that the instructions work on Linux/macOS and highlight any differences (such as command syntax or file paths).
- Avoid using Windows-specific terminology like 'PowerShell' unless necessary, and ensure parity in tool recommendations.
Active Directory B2C
Best practices for Azure AD B2C
...b/main/articles/active-directory-b2c/best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-centric tools (Visual Studio Code, Azure DevOps, VS Web Test) and listing Windows-related testing tools before mentioning cross-platform or Linux alternatives. However, there are no explicit PowerShell-only examples, nor are Linux/macOS users blocked from following the guidance. Most recommendations are platform-agnostic, but the examples and tool suggestions lean toward the Microsoft/Windows ecosystem.
Recommendations
- Include explicit examples or tool recommendations for Linux/macOS users, such as alternative editors (e.g., Vim, Sublime Text) for editing custom policies.
- When mentioning testing tools, list cross-platform options (e.g., Selenium, Cypress) before or alongside Windows-specific ones like VS Web Test.
- Provide guidance or links for setting up CI/CD pipelines using popular Linux/macOS tools (e.g., GitHub Actions, Jenkins) in addition to Azure DevOps.
- Clarify that Visual Studio Code and its extensions are available on Linux/macOS, and mention any platform-specific installation notes if relevant.
- Ensure that automation and troubleshooting sections reference command-line tools and scripts that work across platforms, not just Windows.
Active Directory B2C
Authorization code flow - Azure Active Directory B2C
...ticles/active-directory-b2c/authorization-code-flow.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits minor Windows bias by mentioning Microsoft PowerShell as an example HTTP client for testing POST requests, without referencing Linux/macOS alternatives. No explicit Linux/macOS examples or tools (such as curl or httpie) are provided, and PowerShell is mentioned before any cross-platform options.
Recommendations
- Include Linux/macOS-friendly HTTP client examples, such as curl or httpie, alongside or before PowerShell.
- Explicitly state that any HTTP client can be used, and provide example commands for curl and/or httpie.
- Avoid referencing Windows-specific tools exclusively; ensure parity by mentioning cross-platform tools.
- Consider adding a section or note on how to perform the same steps on Linux/macOS.
Active Directory B2C
Enable authentication in a SPA application by using Azure Active Directory B2C building blocks
.../active-directory-b2c/enable-authentication-spa-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. In the 'Run your SPA application' section, the example commands are shown in PowerShell syntax, and no explicit Linux/macOS shell equivalents are provided. While the rest of the document is generally cross-platform (Node.js, Express, JavaScript), the command-line instructions and examples implicitly prioritize Windows users by using PowerShell and not mentioning Linux/macOS alternatives.
Recommendations
- Provide both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) command examples side by side, especially for npm and server startup commands.
- Explicitly state that the instructions work on all platforms and mention any platform-specific considerations (e.g., file paths, permissions).
- Avoid using PowerShell-specific syntax unless necessary, or clarify when it is required.
- Add a note or section for Linux/macOS users, highlighting any differences in setup or execution.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-web-application-firewall.md
...tive-directory-b2c/partner-web-application-firewall.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for configuration steps and does not provide any command-line examples. There are no PowerShell or Windows-specific tools mentioned, but there is also a lack of parity for Linux users: no Azure CLI (cross-platform) or Bash examples are given. This omission can disadvantage users who prefer or require CLI-based automation, especially on Linux or macOS.
Recommendations
- Add Azure CLI examples for all major configuration steps (e.g., creating a WAF policy, associating it with a Front Door profile, enabling logging).
- Where possible, provide both Portal (UI) and CLI instructions side-by-side.
- Explicitly mention that the Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
- If scripting is required, provide Bash script snippets in addition to any PowerShell or Windows batch examples.
- Link to Azure CLI documentation for relevant commands (e.g., `az network front-door waf-policy`).