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 351-375 of 392 flagged pages
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 is heavily focused on ASP.NET Core and C# code, which are most commonly associated with Windows development environments. There are no explicit instructions, examples, or notes for Linux or cross-platform users. The use of Windows-centric project structures (e.g., Startup.cs, appsettings.json) and references to Visual Studio conventions further reinforce a Windows-oriented approach. There are no command-line instructions, but if there were, they would likely be PowerShell or CMD by default given the context.
Recommendations
- Add explicit notes or sections clarifying that ASP.NET Core and related tools are cross-platform, and provide guidance for Linux and macOS users.
- Include examples or references for setting up and running the sample projects on Linux (e.g., using the dotnet CLI, file paths, and environment variable configuration).
- Mention common Linux editors (e.g., VS Code, Vim) and how to edit configuration files or run the application from the terminal.
- If any scripts or commands are referenced, provide both Windows (PowerShell/CMD) and Linux (bash) equivalents.
- Highlight any platform-specific considerations, such as file permissions or case sensitivity, that may affect Linux users.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api.md
...irectory-b2c/enable-authentication-web-app-with-api.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on ASP.NET Core and Visual Studio tooling, which are traditionally Windows-centric. While .NET Core is cross-platform, the instructions and examples assume a Windows development environment (e.g., Visual Studio, Visual Studio Code) and do not mention or provide explicit guidance for Linux or macOS users. There are no Linux-specific instructions, troubleshooting tips, or references to Linux development workflows.
Recommendations
- Explicitly mention that all .NET Core CLI commands work cross-platform (Windows, Linux, macOS) and provide assurance that Linux is supported.
- Add a section or callout for Linux/macOS users, including any prerequisites (e.g., installing .NET SDK on Linux, using editors like VS Code or JetBrains Rider).
- Include Linux/macOS-specific instructions for running the app (e.g., using 'dotnet run' in a terminal), and clarify any differences in file paths or environment variables.
- If referencing Visual Studio, also reference cross-platform editors (e.g., VS Code, Rider) and provide equivalent steps.
- Add troubleshooting tips for common Linux/macOS issues (e.g., HTTPS certificate trust, file permissions).
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 (a Microsoft-centric technology), referencing Visual Studio and Visual Studio Code as development environments, and omitting any Linux-specific instructions or examples. There are no mentions of Linux tools, shell environments, or cross-platform considerations for running or deploying the application. All command-line instructions are generic or Windows-centric, and there is no guidance for users developing on Linux or macOS.
Recommendations
- Explicitly mention that .NET Core and ASP.NET Core are cross-platform and can be developed and run on Linux, macOS, and Windows.
- Provide Linux/macOS equivalents for any command-line instructions, including package installation and project creation.
- Include instructions for using popular Linux editors (e.g., VS Code on Linux, JetBrains Rider) and terminal environments.
- Add troubleshooting notes or links for common Linux/macOS issues (e.g., HTTPS certificate trust, file permissions).
- Clarify that the dotnet CLI commands work on all platforms, and avoid implying that Visual Studio (Windows) is required.
- If referencing Visual Studio, also mention Visual Studio for Mac or cross-platform alternatives.
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 is heavily focused on using the Azure portal web UI for configuration, which is cross-platform, but where command-line or automation is implied, there are no examples for Linux (e.g., Azure CLI, Bash) or PowerShell. There is a subtle 'Windows-first' bias in that all UI instructions and terminology are oriented toward the Azure portal experience, which is identical on all platforms but is often associated with Windows-centric workflows. There are no explicit references to Windows-only tools, but there is also a lack of parity for Linux users who may prefer CLI or scripting approaches.
Recommendations
- Provide Azure CLI examples for key steps (e.g., app registration, secret creation, identity provider configuration) alongside portal instructions.
- Explicitly mention that all portal steps can be performed from any OS/browser to reinforce cross-platform compatibility.
- Where relevant, include Bash and PowerShell script snippets for automation, and clarify that both are supported.
- Add a section or links to documentation for automating these tasks using CLI tools, which are popular in Linux environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/integrate-with-app-code-samples.md
...ctive-directory-b2c/integrate-with-app-code-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists a broad set of code samples for Azure AD B2C integration across platforms and languages. However, for desktop and console/daemon app scenarios, only .NET/Windows-specific samples are provided (e.g., WPF desktop app, .NET Core console app), with no equivalent Linux or cross-platform desktop/CLI examples. The only desktop sample is explicitly for Windows, and there are no Linux-native or cross-platform GUI/CLI samples. Additionally, the .NET samples are consistently listed before Node.js, Python, or other language samples, indicating a subtle 'windows_first' ordering bias.
Recommendations
- Add Linux-native or cross-platform desktop application samples (e.g., using Electron, Qt, or Java) to demonstrate Azure AD B2C integration outside of Windows.
- Provide CLI/daemon application samples in languages commonly used on Linux (e.g., Python, Node.js, Go) and clarify their cross-platform compatibility.
- Where possible, clarify if .NET Core samples are cross-platform and provide explicit instructions or notes for running them on Linux/macOS.
- Balance the ordering of sample listings so that Windows/.NET samples are not always listed first; consider grouping by platform or language family.
- For each sample, specify supported platforms (Windows, Linux, macOS) to help developers identify relevant examples.
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
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively describes using the Azure Portal (a web-based GUI) for all steps and does not provide any command-line examples. There are no references to PowerShell, Windows-specific tools, or CLI commands, but there is also a complete absence of Linux-friendly alternatives such as Azure CLI or REST API examples. This omission can disadvantage Linux users or those who prefer automation and scripting over GUI-based workflows.
Recommendations
- Add Azure CLI examples for all major steps (e.g., app registration, permission assignment, role assignment, client secret creation), ensuring commands are cross-platform.
- Include REST API examples (using curl or similar tools) for users who wish to automate the process or work on non-Windows platforms.
- Explicitly mention that all steps can be performed using CLI or API, and provide links to relevant documentation.
- If PowerShell or Windows-specific tools are ever referenced, ensure Linux equivalents are presented side-by-side or before the Windows examples.
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-first 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 instructions for Linux or macOS users. The documentation does not provide parity in examples or guidance for non-Windows environments, and focuses on Windows-specific tools and terminology.
Recommendations
- Include explicit examples and instructions for enabling biometric authentication on Linux (e.g., using fprintd, libfprint, or other Linux-compatible biometric solutions) and macOS (e.g., Touch ID).
- When describing scenarios, mention Linux and macOS biometric capabilities alongside Windows Hello, rather than focusing on Windows first.
- Provide troubleshooting or compatibility notes for users on Linux and macOS, including any limitations or required setup steps.
- Use platform-neutral language where possible (e.g., 'your device's biometric authentication' instead of 'Windows Hello'), and only reference Windows Hello as one of several options.
- Add a table or section comparing biometric authentication support across Windows, Linux, and macOS, with links to relevant setup guides.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure Portal GUI instructions and the absence of any Linux-specific or cross-platform command-line examples. All step-by-step instructions assume use of the Azure Portal, which is platform-agnostic but often more familiar to Windows users. There are no references to Linux tools, shell commands, or PowerShell/CMD scripts, but also no mention of Bash or Linux CLI alternatives. The only code snippets are XML/PowerShell-like configuration blocks, which are not OS-specific, but the overall workflow and tooling references implicitly favor Windows users by not acknowledging or providing parity for Linux environments.
Recommendations
- Add CLI-based instructions using Azure CLI or Azure PowerShell, and specify cross-platform compatibility.
- Include examples or notes for performing key steps (such as uploading policy files or managing secrets) using Bash or Linux shell environments.
- Explicitly mention that the Azure Portal is accessible from any OS, and provide links to documentation for Linux users where relevant.
- Where configuration files are edited or uploaded, provide command-line alternatives (e.g., using az ad b2c policy commands if available) and note any OS-specific considerations.
- Review and update the documentation to ensure that Linux administrators can follow all steps without needing to switch to a Windows environment.
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 demonstrates subtle Windows bias by referencing a SAML application guide with a URL parameter '?tabs=windows', suggesting that Windows-specific instructions or tabs are prioritized or default. There are no explicit Linux or cross-platform examples or tabs mentioned, and no indication that Linux users are equally supported in the SAML app registration flow. No PowerShell or Windows-only tools are directly mentioned, but the lack of Linux parity in tabbing and examples is notable.
Recommendations
- Ensure that all platform-specific instructions (such as for SAML apps) provide both Windows and Linux (and possibly macOS) tabs or examples.
- Default to a neutral or cross-platform tab (e.g., '?tabs=linux' or '?tabs=cli') in documentation URLs, or provide a platform selector.
- Explicitly mention Linux and other non-Windows platforms in relevant sections to assure users of parity.
- Review all linked tutorials to confirm that Linux instructions are present and equally prominent.
- Where applicable, provide CLI-based (e.g., Azure CLI, Bash) examples alongside any Windows/Powershell instructions.
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, primarily through the mention of Windows-centric tools and patterns. For example, Visual Studio Code is recommended for editing custom policies, and testing examples mention Selenium and 'VS Web Test' (Visual Studio Web Test), a Windows-specific tool, before any cross-platform alternatives. There are no explicit Linux/macOS examples or tool recommendations, and no PowerShell-specific instructions, but the ordering and tool selection subtly favor Windows environments.
Recommendations
- Include Linux/macOS equivalents or alternatives for all recommended tools (e.g., mention cross-platform editors like Vim, Emacs, or JetBrains IDEs alongside Visual Studio Code).
- When listing testing tools, provide cross-platform options first or alongside Windows tools (e.g., mention Cypress, Playwright, or Puppeteer in addition to Selenium and Visual Studio Web Test).
- Add explicit notes or examples for Linux/macOS users where workflows or tools differ.
- Ensure that any automation or CI/CD recommendations (such as Azure DevOps) also mention alternatives popular in Linux environments (e.g., GitHub Actions, GitLab CI).
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 demonstrates mild Windows bias by referencing PowerShell for GUID generation and providing a PowerShell script as the first example for obtaining an access token. Windows tools and terminology (PowerShell, 'new-guid') are mentioned before alternatives, and Linux/macOS equivalents for GUID generation are not provided. However, a cURL example is included, which is cross-platform.
Recommendations
- Include Linux/macOS command-line examples for GUID generation (e.g., 'uuidgen' or 'openssl rand -hex 16').
- Present cURL and PowerShell examples side-by-side, or list cURL first to emphasize cross-platform compatibility.
- Explicitly mention that cURL works on Windows, Linux, and macOS.
- Add notes or links for Linux/macOS users on how to accomplish steps that reference Windows tools.
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
Summary
The documentation is largely platform-neutral, focusing on HTTP requests and protocol details. However, there is a minor Windows bias in the section '2. Get an access token', where Microsoft PowerShell is mentioned as an example HTTP client for testing POST requests. No Linux/macOS tools (such as curl, httpie, or wget) are mentioned, nor are cross-platform examples provided.
Recommendations
- Mention cross-platform HTTP clients such as curl, httpie, or wget alongside PowerShell.
- Provide example commands for Linux/macOS users (e.g., curl POST requests) in addition to or instead of PowerShell.
- Clarify that any HTTP client can be used, and link to documentation for popular Linux/macOS tools.
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 its final 'Run your SPA application' step, where the example commands are shown in PowerShell syntax and no Linux/macOS shell equivalents are provided. Earlier steps use generic 'command shell' language and standard npm commands, which are cross-platform, but the explicit PowerShell block and lack of Linux/macOS instructions may cause confusion or friction for non-Windows users.
Recommendations
- Provide Linux/macOS shell equivalents (e.g., bash/zsh) alongside PowerShell commands in the 'Run your SPA application' section.
- Use generic command syntax (e.g., 'npm install && node index.js') that works across platforms, or clarify platform-specific differences.
- Explicitly mention that all steps can be performed on Linux/macOS and Windows, and note any platform-specific caveats.
- Avoid using PowerShell-specific syntax unless necessary, and if used, always provide alternatives.
Active Directory B2C
Tutorial to enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP
.../blob/main/articles/active-directory-b2c/partner-f5.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and providing a link to IIS setup documentation. No equivalent Linux or cross-platform web application example (such as Apache, Nginx, or a generic header-based app) is mentioned. All other configuration steps are platform-agnostic, focusing on Azure AD B2C and F5 BIG-IP, which are not inherently Windows-specific.
Recommendations
- Include Linux-based web application examples (e.g., Apache, Nginx) for testing header-based authentication.
- Provide links to setup guides for Linux web servers alongside the IIS example.
- Clarify that any header-based web application can be used, and offer sample configuration snippets for both Windows (IIS) and Linux (Apache/Nginx) environments.
- Explicitly mention cross-platform compatibility in the prerequisites and testing sections.
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
Summary
The documentation is generally 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 reference to Linux/macOS alternatives such as curl or HTTPie. This is a mild Windows bias in tooling recommendations.
Recommendations
- When suggesting HTTP clients for testing, include cross-platform tools such as curl, HTTPie, or Postman alongside PowerShell.
- Add example commands for Linux/macOS users (e.g., curl POST examples) to demonstrate parity and inclusivity.
- Explicitly state that any HTTP client can be used, and provide links or references to popular clients on all platforms.
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 mentioning Visual Studio Code (a cross-platform tool but historically associated with Windows) and VS Web Test (a Windows-centric testing tool) before or alongside more platform-neutral alternatives. Windows tools are referenced in testing and implementation sections, and examples like Selenium are listed after VS Web Test. However, the page does not provide command-line examples, PowerShell scripts, or instructions that are Windows-only, and most recommendations are platform-agnostic.
Recommendations
- When listing tools for testing, mention platform-neutral or Linux/macOS-friendly tools first (e.g., Selenium, Cypress) before Windows-specific ones like VS Web Test.
- Explicitly state that Visual Studio Code and its extensions are available on Linux and macOS, not just Windows.
- Include examples or references for Linux/macOS equivalents where Windows tools are mentioned (e.g., alternatives to VS Web Test).
- Add notes or links for users on Linux/macOS about any differences in setup or usage for recommended tools.
Active Directory B2C
Tutorial to enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP
.../blob/main/articles/active-directory-b2c/partner-f5.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing IIS as the example application for testing and linking to IIS setup instructions, without mentioning or providing equivalent Linux-based web application examples (e.g., Apache, Nginx). The only explicit application setup guidance is for IIS, which is Windows-specific. No PowerShell or Windows-only tools are referenced, and most configuration steps are platform-agnostic (focused on F5 BIG-IP and Azure AD B2C GUIs).
Recommendations
- Include examples and setup instructions for common Linux web servers (such as Apache or Nginx) alongside IIS.
- Provide links to Linux-based application setup guides for testing the integration.
- Clarify that the solution is not limited to IIS and can be used with any header-based web application, including those running on Linux.
- Add troubleshooting notes or tips relevant to Linux environments where appropriate.
Active Directory B2C
Manage user data in Azure Active Directory B2C
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not include any command-line examples (Windows or Linux). However, there is a lack of parity in that no Linux (bash/curl) or Windows (PowerShell) examples are given for interacting with the Microsoft Graph API, which could be seen as a missed opportunity to ensure cross-platform inclusivity.
Recommendations
- Add explicit examples for both Windows (using PowerShell) and Linux/macOS (using bash and curl) to demonstrate how to call the Microsoft Graph API for deleting and exporting user data.
- When providing sample scripts or command-line instructions, ensure both PowerShell and bash/curl examples are included side by side.
- Mention cross-platform tools (such as Azure CLI, Microsoft Graph CLI, or REST API via curl) and clarify their availability on different operating systems.
- Explicitly state that the operations can be performed from any OS, and provide links or references to platform-agnostic tools.
Active Directory B2C
Manage user data in Azure Active Directory B2C
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples (such as command-line instructions or scripts), but it also does not mention or show any Windows-specific tools, PowerShell commands, or Windows-first patterns. However, there is a lack of parity in that no Linux (or cross-platform) command-line examples, scripts, or tooling are provided at all, which could leave Linux users without clear guidance for practical implementation.
Recommendations
- Add example commands for both Windows (e.g., PowerShell) and Linux (e.g., curl or bash scripts) to demonstrate how to call the Microsoft Graph API for deleting or exporting user data.
- Include references to cross-platform tools (such as Azure CLI, Microsoft Graph CLI, or REST API calls using curl) to ensure users on any OS can follow along.
- Explicitly state that the described processes can be implemented on any platform, and provide sample code or scripts for both Windows and Linux environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-collect-user-input.md
...ctory-b2c/custom-policies-series-collect-user-input.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by requiring Visual Studio Code (VS Code) to be installed on 'your computer' without specifying cross-platform compatibility or alternatives. While VS Code is available on Windows, Linux, and macOS, the documentation does not explicitly acknowledge Linux or macOS users, nor does it mention any Linux-specific setup or tools. No command-line or scripting examples are given, so there is no overt PowerShell or Windows command bias. However, the implicit assumption of a Windows environment is present.
Recommendations
- Explicitly state that Visual Studio Code is available on Windows, Linux, and macOS, and provide links or instructions for installing it on each platform.
- If any steps require OS-specific actions (such as file paths, uploading files, or running scripts), provide equivalent instructions for Linux and macOS users.
- Mention that the Azure portal and policy upload process are platform-agnostic, and clarify that all steps can be performed from any supported OS.
- If referencing tools or editors, consider mentioning popular Linux alternatives or command-line options where applicable.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a mild Windows bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) equivalent. No Linux-specific example is given, but the iOS command is compatible with Linux/macOS. There are no other Windows-specific tools, PowerShell scripts, or patterns elsewhere in the document.
Recommendations
- Present command-line examples for Windows and Linux/macOS side by side, or use neutral headings such as 'On Windows' and 'On Linux/macOS' instead of 'For Windows' and 'For iOS'.
- Explicitly mention that the 'iOS' command works for Linux/macOS, or provide a separate 'For Linux/macOS' section.
- Consider providing a table or tabbed interface for platform-specific commands to ensure parity and clarity.
- Review other documentation pages linked from this one to ensure Linux users are not left out in related setup or troubleshooting steps.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-user-data.md
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, scripts, or tooling, but it also does not include any command-line or automation examples at all. As such, there is a lack of parity in that neither Windows (e.g., PowerShell) nor Linux (e.g., Bash/cURL) approaches are shown. However, the absence of Linux-specific examples or mentions could be considered a subtle bias, as many Azure AD B2C and Microsoft Graph API guides tend to default to Windows/PowerShell unless otherwise specified.
Recommendations
- Add explicit examples for both Windows (PowerShell) and Linux/macOS (Bash/cURL) for interacting with the Microsoft Graph API to delete or export user data.
- Include sample scripts or command-line invocations for both platforms, demonstrating how to authenticate and call the relevant Graph API endpoints.
- Ensure that any references to tools or workflows are cross-platform, or provide alternatives where necessary.
- Clarify in the documentation that the API operations can be performed from any OS, and provide links to SDKs or tools for multiple platforms.
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
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not exhibit overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it exclusively relies on the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, which is cross-platform and commonly used on Linux/macOS). There are no Linux-specific or cross-platform automation examples, which may disadvantage users who prefer or require non-GUI, scriptable workflows, especially on Linux.
Recommendations
- Add Azure CLI examples for all major steps (application registration, permission assignment, role assignment, client secret creation), as Azure CLI is cross-platform and widely used on Linux.
- Where possible, provide REST API or Microsoft Graph API examples (e.g., using curl or HTTP requests) for automation scenarios.
- Explicitly mention that all steps can be performed using command-line tools on Linux/macOS, not just via the Azure Portal.
- Consider including a section or callout for 'Command-line (CLI) instructions' alongside the portal-based instructions to ensure parity for Linux and automation-focused 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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias by linking to API protection instructions that default to a Windows-specific tab (e.g., '?tabs=windows') when referencing further documentation. However, the main content itself is largely platform-neutral, focusing on Azure AD B2C policy XML and REST API patterns without explicit use of Windows-only tools or commands. There are no PowerShell-heavy sections, exclusive Windows tools, or missing Linux examples in the main body.
Recommendations
- When linking to further documentation (such as 'secure-rest-api.md?tabs=windows'), ensure that links are either platform-neutral or explicitly mention both Windows and Linux options.
- If the linked documentation contains platform-specific instructions, provide a brief note or alternative link for Linux/macOS users.
- Review all referenced guides and ensure parity in examples and instructions for both Windows and Linux environments.
- Consider adding a short section or note clarifying that the described steps and API interactions are OS-agnostic, and can be performed from any platform.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation contains a subtle Windows bias in the form of a key link to API protection instructions that explicitly uses a Windows-specific tab in its URL (secure-rest-api.md?tabs=windows&pivots=b2c-custom-policy#using-oauth2-bearer). This suggests that Windows instructions are the default or primary guidance, with no mention of Linux or cross-platform alternatives. No PowerShell, Windows-only tools, or CLI examples are present, but the linked documentation may reinforce a Windows-first perspective.
Recommendations
- Ensure that all referenced links (such as to API protection guides) either default to a cross-platform or neutral tab, or explicitly mention both Windows and Linux options.
- If the linked documentation provides platform-specific instructions, clarify in this document that equivalent steps are available for Linux/macOS users and provide direct links or notes.
- Review all external documentation references for similar platform-specific defaults and adjust to promote parity.
- Consider adding a brief note in the prerequisites or relevant sections stating that all steps can be performed on Windows, Linux, or macOS, and link to platform-appropriate instructions where necessary.