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 1-25 of 392 flagged pages
Active Directory B2C Add AD FS as a SAML identity provider by using custom policies ...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with all AD FS management steps described using Windows GUI tools (Server Manager, AD FS Management snap-in) and PowerShell cmdlets. There are no Linux or macOS equivalents, nor any mention of cross-platform alternatives for AD FS setup, troubleshooting, or certificate management. Troubleshooting references only Windows Event Viewer. This creates friction for non-Windows users, who cannot follow key steps without access to a Windows system.
Recommendations
  • Clarify that AD FS is a Windows-only service, but explicitly state requirements for a Windows environment at the start.
  • Provide guidance for Linux/macOS users on how to interact with AD FS remotely (e.g., via web interfaces, REST APIs, or remote PowerShell sessions).
  • Offer alternative methods for certificate creation and management using cross-platform tools (e.g., OpenSSL) and explain how to transfer certificates to Windows.
  • Include troubleshooting steps that can be performed remotely or via command line, and mention any relevant logs accessible outside Windows Event Viewer.
  • If possible, suggest SAML identity providers that are cross-platform as alternatives to AD FS for non-Windows environments.
GitHub Create Pull Request
Active Directory B2C Add AD FS as an OpenID Connect identity provider by using custom policies ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically AD FS (Active Directory Federation Services), which is a Windows Server feature. All configuration steps reference Windows-only tools (Server Manager, AD FS Management), and there are no Linux/macOS equivalents or alternative approaches mentioned. The instructions and screenshots assume a Windows GUI, and there is no mention of command-line or cross-platform methods. Linux users cannot complete the AD FS setup as described.
Recommendations
  • Explicitly state that AD FS is a Windows Server feature and clarify platform requirements early in the documentation.
  • Provide guidance or links for Linux/macOS users on alternative identity providers or cross-platform OpenID Connect implementations.
  • If possible, include PowerShell and command-line examples for AD FS setup to support automation and remote management, and clarify their platform limitations.
  • Mention open-source or non-Windows options for similar scenarios, such as using Keycloak, IdentityServer, or other OpenID Connect providers.
  • Add a comparison table or section outlining platform support and alternatives for non-Windows environments.
GitHub Create Pull Request
Active Directory B2C Add AD FS as an OpenID Connect identity provider by using custom policies ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing AD FS management via Windows GUI tools (Server Manager, AD FS Management) and omitting any Linux/macOS equivalents or command-line alternatives. All configuration steps assume access to Windows Server and its graphical interface, with no mention of how to perform these tasks on non-Windows platforms or via cross-platform tools. Windows terminology and endpoints are used exclusively, and Windows-specific documentation is referenced first and exclusively.
Recommendations
  • Provide PowerShell and command-line alternatives for AD FS management tasks, and clarify which steps can be performed remotely or via scripts.
  • Explicitly state that AD FS is a Windows Server feature and note any cross-platform limitations.
  • If possible, mention alternatives for Linux/macOS users, such as using Azure AD or other OpenID Connect providers that are cross-platform.
  • Add guidance or links for configuring OpenID Connect providers on Linux (e.g., using Keycloak, IdentityServer, etc.) for similar scenarios.
  • Clarify prerequisites regarding platform requirements early in the documentation.
GitHub Create Pull Request
Active Directory B2C Add AD FS as a SAML identity provider by using custom policies ...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a significant Windows bias. All configuration steps for AD FS rely exclusively on Windows-specific tools such as Server Manager, AD FS Management snap-in, and PowerShell cmdlets. Troubleshooting instructions reference Windows Event Viewer only. There are no Linux/macOS equivalents, nor any mention of cross-platform alternatives for managing AD FS or viewing logs. Windows tools and patterns are presented as the only option, with no parity for Linux or macOS users.
Recommendations
  • Explicitly state that AD FS is a Windows-only technology and clarify platform requirements at the top of the document.
  • Where possible, mention that all AD FS management and troubleshooting steps require Windows Server and are not available on Linux/macOS.
  • If any cross-platform SAML identity providers are supported, provide equivalent instructions or links for those platforms.
  • For certificate creation and management, include Linux/macOS command-line examples (e.g., using OpenSSL) alongside Windows instructions.
  • For troubleshooting, suggest alternative log inspection methods if supported by Azure AD B2C or SAML providers on non-Windows platforms.
GitHub Create Pull Request
Active Directory B2C Request an access token in Azure Active Directory B2C ...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Microsoft PowerShell as an example HTTP client for testing the POST request, without referencing any Linux or cross-platform alternatives. No Linux command-line tools (such as curl or wget) are suggested, and PowerShell is mentioned before any other tool, implying Windows as the default environment.
Recommendations
  • Include examples using cross-platform tools such as curl or wget for making HTTP requests.
  • Explicitly mention that any HTTP client can be used, and provide sample commands for both Windows (PowerShell) and Linux/macOS (curl).
  • Avoid listing Windows-specific tools first; present cross-platform or OS-neutral options before platform-specific ones.
  • Add a note clarifying that the instructions apply equally to Linux, macOS, and Windows environments.
GitHub Create Pull Request
Active Directory B2C Set up OAuth 2.0 client credentials flow .../active-directory-b2c/client-credentials-grant-flow.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias in several areas. The only explicit tool mentioned for generating GUIDs is Microsoft PowerShell, with no Linux or cross-platform alternatives provided or prioritized. The scripting example for obtaining an access token is given first in PowerShell, before the cURL (Linux-friendly) example. Windows tools and patterns are referenced without equal mention of Linux equivalents, and the order of examples favors Windows-first presentation.
Recommendations
  • When mentioning GUID generation, include Linux/macOS alternatives such as 'uuidgen' or 'openssl rand -hex 16', and provide example commands.
  • Present cross-platform examples (e.g., cURL) before or alongside Windows-specific ones like PowerShell.
  • Explicitly mention that all steps (including manifest editing and API calls) can be performed on Linux/macOS, and provide relevant command-line or tool references.
  • Avoid referencing Windows tools exclusively; always provide parity for Linux/macOS users.
  • Consider adding a table or section listing equivalent commands/tools for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Saviynt with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-saviynt.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias in the section on enabling Saviynt to delete users. It exclusively instructs users to install and use the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. Only PowerShell commands are provided, and there is no guidance for performing the same tasks on Linux or macOS, nor are platform-agnostic tools (such as Microsoft Graph CLI or REST API) mentioned.
Recommendations
  • Provide equivalent instructions for Linux and macOS environments, including installation and usage of Microsoft Graph CLI or REST API.
  • Include examples using platform-agnostic tools (e.g., Microsoft Graph CLI, curl commands for REST API) alongside PowerShell examples.
  • Explicitly state cross-platform options for all steps involving command-line tools.
  • Rephrase steps to avoid assuming a Windows environment by default (e.g., 'On your workstation' instead of 'On a Windows workstation or server').
  • Add a note clarifying that PowerShell Core is available on Linux/macOS and provide installation instructions if PowerShell is still preferred.
GitHub Create Pull Request
Active Directory B2C IDology integration with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-idology.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API. There are no examples or guidance for deploying the API from Linux environments, nor are alternative tools or workflows (such as VS Code, CLI, or GitHub Actions) mentioned. The documentation assumes the use of Windows tooling and does not provide parity for Linux users.
Recommendations
  • Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code.
  • Add Linux-specific deployment examples (e.g., using dotnet CLI or zip deploy from Linux/macOS).
  • Mention alternative editors and IDEs (such as VS Code) alongside Visual Studio.
  • Ensure that all referenced documentation and samples are accessible and applicable from Linux environments.
  • Review and update any screenshots or UI references to avoid Windows-only terminology.
GitHub Create Pull Request
Active Directory B2C Call a REST API by using Azure AD B2C custom policy ...-directory-b2c/custom-policies-series-call-rest-api.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for testing the REST API, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The instructions and tooling references (e.g., Visual Studio Code) are cross-platform, but the testing and client interaction sections are Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS command-line examples for testing the REST API, such as using curl or HTTPie.
  • When referencing PowerShell, clarify that it is available cross-platform, but also offer alternative commands for users on Linux/macOS.
  • List cross-platform or Linux-native tools (e.g., curl, wget, HTTPie) before or alongside Windows tools when suggesting HTTP clients.
  • Explicitly mention that Visual Studio Code and Node.js are cross-platform, and that all steps can be performed on Linux/macOS as well as Windows.
  • Consider including a table or section summarizing how to perform key steps on Windows, Linux, and macOS.
GitHub Create Pull Request
Active Directory B2C Configure a force password reset flow in Azure AD B2C .../articles/active-directory-b2c/force-password-reset.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively providing PowerShell examples for configuring password expiry duration, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux or cross-platform CLI instructions. All procedural steps assume use of the Azure portal or PowerShell, with no mention of Bash, Azure CLI, or other Linux-friendly approaches. Windows tools and patterns are presented first and exclusively, with no parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands for all operations currently demonstrated with PowerShell.
  • Include Bash or shell script snippets where applicable, especially for REST API calls (e.g., using curl for PATCH requests).
  • Explicitly mention cross-platform compatibility for all steps, clarifying which tools can be used on Linux, macOS, and Windows.
  • Add a section or note highlighting how Linux/macOS users can perform the same tasks without PowerShell, including installation and usage of Microsoft Graph CLI or REST API.
  • Ensure that tool recommendations and examples are presented in a platform-neutral order, or grouped by platform, rather than defaulting to Windows/PowerShell first.
GitHub Create Pull Request
Active Directory B2C Add AD FS as an OpenID Connect identity provider by using custom policies ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias. All instructions for configuring AD FS are given using Windows-specific tools (Server Manager, AD FS Management), with no mention of Linux alternatives or cross-platform approaches. The examples and screenshots exclusively reference Windows environments, and there are no PowerShell scripts or command-line alternatives provided, but the reliance on GUI tools is itself Windows-centric. No Linux-based AD FS equivalents or instructions are offered, nor is there guidance for users who might be running AD FS or similar identity providers on non-Windows platforms.
Recommendations
  • Provide command-line (PowerShell and/or Windows CMD) instructions for AD FS configuration to support automation and remote management.
  • Explicitly state that AD FS is a Windows Server feature and clarify platform requirements early in the documentation.
  • Mention and link to cross-platform alternatives (such as using Azure AD, Keycloak, or other OpenID Connect providers that run on Linux) for users who do not have access to Windows Server.
  • If possible, include steps or references for configuring OpenID Connect providers on Linux, or provide parity documentation for equivalent scenarios.
  • Add a note about the lack of Linux support for AD FS, and suggest alternative identity providers for Linux environments.
GitHub Create Pull Request
Active Directory B2C Deploy custom policies with Azure Pipelines .../active-directory-b2c/deploy-custom-policies-devops.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies in Azure Pipelines, with no mention of Linux-compatible alternatives (such as Bash or cross-platform scripting). All example scripts and pipeline tasks are PowerShell-based, and there is no guidance for users on Linux agents or those preferring non-Windows tooling. The documentation implicitly assumes a Windows-centric workflow and does not provide parity for Linux users.
Recommendations
  • Provide equivalent Bash script examples for deploying policies using curl or similar tools, suitable for Linux agents.
  • Explicitly mention that Azure Pipelines supports both Windows and Linux agents, and guide users on how to adapt the deployment process for Linux environments.
  • Include instructions for running deployment tasks using Bash or cross-platform scripting languages (e.g., Python), and show how to configure these in the pipeline.
  • Add a section comparing PowerShell and Bash approaches, highlighting any differences and considerations for cross-platform compatibility.
  • Avoid assuming PowerShell as the default; present both Windows and Linux options side-by-side where possible.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. The only explicit command-line example for running the application uses PowerShell syntax (npm ./index.js), which is not valid on Linux/macOS shells. There is no mention of Linux or macOS environments, nor are equivalent Bash commands provided. The instructions and examples implicitly assume a Windows environment, especially in the final 'Run your SPA application' step.
Recommendations
  • Provide equivalent Bash commands for Linux/macOS users, such as 'node index.js' or 'npm start', and clarify cross-platform compatibility.
  • Avoid using PowerShell-specific syntax unless explicitly targeting Windows users; use generic commands where possible.
  • Add a note or section indicating that the instructions apply to Windows, Linux, and macOS, and specify any platform-specific differences.
  • Include troubleshooting tips for common issues on Linux/macOS (e.g., port binding, permissions).
GitHub Create Pull Request
Active Directory B2C Define an ID token hint technical profile in a custom policy ...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-only examples for key generation and certificate creation, referencing Windows-specific tools (PowerShell cmdlets), and omitting equivalent Linux/macOS commands or tools. The instructions for generating a self-signed certificate explicitly mention PowerShell and do not offer alternatives for non-Windows platforms. The sample code and walkthroughs are Windows-centric, with no mention of cross-platform approaches.
Recommendations
  • Provide equivalent command-line examples for Linux and macOS, such as using openssl for key and certificate generation.
  • Mention cross-platform tools and approaches (e.g., dotnet CLI, openssl) alongside Windows/PowerShell instructions.
  • Add notes or sections clarifying how developers on non-Windows platforms can perform the same steps.
  • Ensure that sample code and walkthroughs reference platform-neutral or cross-platform solutions where possible.
  • Order examples so that Windows and Linux/macOS approaches are presented together or Linux/macOS is not always secondary.
GitHub Create Pull Request
Active Directory B2C Add AD FS as a SAML identity provider by using custom policies ...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically AD FS on Windows Server. All configuration and troubleshooting steps reference Windows-only tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux equivalents or cross-platform alternatives mentioned, and all examples and procedures assume a Windows administrative context.
Recommendations
  • Add notes clarifying that AD FS is a Windows-only technology, and suggest alternatives for Linux environments (e.g., Shibboleth, SimpleSAMLphp) where possible.
  • Provide guidance or links for integrating non-Windows SAML providers with Azure AD B2C custom policies.
  • Where troubleshooting steps reference Windows tools (Event Viewer, AD FS Management), mention that these are not available on Linux and suggest alternative logging or debugging strategies for non-Windows SAML providers.
  • If PowerShell is used for configuration, offer equivalent commands or scripts for other platforms where feasible, or clarify that these steps are Windows-specific.
  • Consider including a section on cross-platform SAML integration to improve parity and help Linux administrators understand their options.
GitHub Create Pull Request
Active Directory B2C Create & delete Azure AD B2C consumer user accounts in the Azure portal ...n/articles/active-directory-b2c/manage-users-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias in the section on revoking a consumer user's session, where only Microsoft Graph PowerShell (specifically in 'Windows PowerShell') is provided as an example. There is no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or direct REST API usage), nor is there guidance for running PowerShell cross-platform. The instructions and terminology assume a Windows environment, potentially excluding Linux and macOS users.
Recommendations
  • Provide equivalent examples using Bash, Azure CLI, or direct REST API calls for session revocation.
  • Clarify that Microsoft Graph PowerShell is cross-platform and provide instructions for installation and usage on Linux and macOS.
  • Avoid specifying 'Windows PowerShell' unless the example is truly Windows-specific; use 'PowerShell' or 'terminal' for cross-platform inclusivity.
  • Wherever PowerShell is used, offer alternative command-line or scripting examples suitable for Linux users.
  • Review other sections for similar platform assumptions and ensure parity in instructions and tooling for Linux environments.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting equivalent Linux web server examples (such as Apache or Nginx). Windows tooling (IIS) is mentioned exclusively, and no Linux alternatives or parity guidance are provided for users who may want to test or deploy with Linux-based applications.
Recommendations
  • Add Linux-based web application examples (e.g., Apache, Nginx) alongside IIS for testing the integration.
  • Provide setup instructions or reference links for configuring header-based authentication with popular Linux web servers.
  • Ensure troubleshooting and configuration steps include notes or guidance relevant to Linux environments where applicable.
  • Explicitly state that the solution is platform-agnostic and provide parity in examples and references for both Windows and Linux.
  • Review all references to Windows-specific tools and add Linux equivalents where possible.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Jumio ...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for certificate creation and random string generation, with no equivalent Linux or cross-platform examples (e.g., OpenSSL, Bash). The instructions reference Visual Studio for deployment, a Windows-centric tool, and do not mention alternatives like VS Code or CLI-based deployment methods. The use of Windows certificate store paths and lack of mention of Linux certificate management further reinforce the bias.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., OpenSSL commands) and random string generation (e.g., Bash or Python scripts).
  • Include deployment instructions using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions, not just Visual Studio.
  • Reference certificate storage and management for Linux (e.g., PEM files, local file system) alongside Windows certificate store.
  • Present examples and instructions for both Windows and Linux platforms, or use platform-agnostic language and tooling where possible.
GitHub Create Pull Request
Active Directory B2C Secure APIs used for API connectors in Azure AD B2C .../main/articles/active-directory-b2c/secure-rest-api.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as the method for preparing a self-signed certificate. There is no mention of Linux or cross-platform alternatives (such as OpenSSL) for certificate generation. The rest of the documentation is largely platform-neutral, focusing on Azure portal UI and XML configuration, but the lack of Linux/macOS command-line examples for certificate management is a notable omission.
Recommendations
  • Add instructions and examples for generating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
  • Explicitly mention that certificate creation can be performed on any OS and provide links or steps for both PowerShell and OpenSSL.
  • Where PowerShell is referenced, clarify that it is one option and suggest alternatives for non-Windows users.
  • Review any referenced includes (such as active-directory-b2c-create-self-signed-certificate.md) to ensure Linux/macOS parity.
  • Consider adding a table or section comparing certificate creation methods across platforms.
GitHub Create Pull Request
Active Directory B2C Manage directory size quota in Azure Active Directory B2C ...ive-directory-b2c/tenant-management-directory-quota.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell script for monitoring directory quota usage, with no equivalent example for Linux or cross-platform tools. The use of PowerShell and Windows-specific scripting patterns is presented as the sole method, implicitly prioritizing Windows environments and omitting guidance for Linux or macOS administrators.
Recommendations
  • Add equivalent examples using cross-platform tools such as curl and jq, or provide a Bash script for Linux/macOS users.
  • Explicitly mention that the API call can be made from any platform and provide generic HTTP request instructions.
  • Include notes or links to platform-agnostic Microsoft Graph SDKs (e.g., Python, Node.js) for broader accessibility.
  • Present Windows and Linux/macOS instructions side-by-side or in separate tabs to ensure parity and avoid platform bias.
GitHub Create Pull Request
Active Directory B2C Access and review audit logs .../main/articles/active-directory-b2c/view-audit-logs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides only a PowerShell script example for accessing Azure AD B2C audit logs programmatically, with no equivalent example for Linux users (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) indicate a Windows-centric approach. No Linux-native tools or cross-platform alternatives are mentioned, and the scripting section is introduced without consideration for non-Windows environments.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, demonstrating authentication and pagination.
  • Include a Python script example using the 'requests' library to show cross-platform programmatic access.
  • Explicitly mention that the API can be accessed from any platform and provide guidance for Linux and macOS users.
  • Reference Linux-native tools (e.g., curl, wget) and provide sample commands for downloading and processing logs.
  • Reorder or parallelize scripting examples so that Windows and Linux approaches are presented together, ensuring parity.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Jumio ...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts for certificate creation and random string generation, referencing Visual Studio for deployment, and omitting equivalent Linux/macOS commands or tooling. There are no bash, OpenSSL, or cross-platform CLI examples, and Windows-centric tools and workflows are mentioned first and exclusively.
Recommendations
  • Provide equivalent bash/OpenSSL commands for certificate creation and export for Linux/macOS users.
  • Include examples using Azure CLI or cross-platform tools for deployment, not just Visual Studio.
  • Offer random string generation examples using bash, Python, or other cross-platform scripting languages.
  • Clearly indicate that the steps can be performed on Linux/macOS and provide links to relevant documentation.
  • Add notes or sections for platform-specific instructions to ensure parity and inclusivity.
GitHub Create Pull Request
Active Directory B2C Set up OAuth 2.0 client credentials flow .../active-directory-b2c/client-credentials-grant-flow.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It suggests using Microsoft PowerShell to generate GUIDs before mentioning platform-neutral alternatives, and provides a PowerShell script as the first code sample for obtaining an access token. While a cURL example is also included, Windows-centric tools and patterns are introduced before Linux equivalents, and the use of PowerShell is emphasized.
Recommendations
  • When suggesting GUID generation, list platform-neutral or Linux-friendly options first (e.g., 'uuidgen' on Linux/macOS, or online generators), then mention PowerShell as an alternative.
  • Provide Linux/macOS command-line examples (e.g., 'uuidgen') alongside PowerShell for tasks like GUID generation.
  • Present cURL or platform-neutral examples before PowerShell scripts when demonstrating API calls.
  • Explicitly state that all examples work cross-platform, and clarify any OS-specific requirements.
  • Consider adding bash or Python script examples for token acquisition to further improve parity.
GitHub Create Pull Request
Active Directory B2C Call a REST API by using Azure AD B2C custom policy ...-directory-b2c/custom-policies-series-call-rest-api.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts for testing the REST API, mentioning Microsoft PowerShell as the primary HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The tools and instructions assume a Windows environment, and there is no guidance for users on other platforms.
Recommendations
  • Add equivalent Linux/macOS command-line examples using curl or HTTPie for making HTTP requests to the REST API.
  • When mentioning PowerShell, also mention cross-platform alternatives and provide side-by-side examples.
  • Avoid referring to Microsoft PowerShell as the only HTTP client; instead, use neutral language such as 'an HTTP client such as curl, HTTPie, or PowerShell'.
  • Include notes or sections for Linux/macOS users, especially in testing and deployment steps.
  • Ensure that all code snippets and instructions are platform-agnostic or provide alternatives for each major OS.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. In the 'Run your SPA application' section, the example command is given in PowerShell syntax, which is specific to Windows. There is no mention of Linux/macOS equivalents, nor are cross-platform shell commands (like Bash) provided. The instructions and tooling otherwise remain platform-neutral, but the command-line examples implicitly prioritize Windows users.
Recommendations
  • Provide both PowerShell (Windows) and Bash (Linux/macOS) command examples when instructing users to run commands.
  • Explicitly mention that the steps are cross-platform and can be performed on Linux/macOS as well as Windows.
  • Replace or supplement 'npm ./index.js' (which is not a standard npm command) with 'node index.js', which works across platforms.
  • Add a note clarifying that the instructions apply to all major operating systems and that no step is Windows-specific.
  • Avoid using Windows-specific command shells unless necessary, and always provide alternatives for other platforms.
GitHub Create Pull Request
← Previous Page 1 of 16 Next →