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 26-50 of 392 flagged pages
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-11 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 exclusively providing PowerShell examples and referencing Windows-centric tools (such as the Microsoft Graph PowerShell module) for configuring password expiry. There are no equivalent Linux shell (bash, curl, etc.) examples or instructions, and the PowerShell approach is presented as the default method for scripting these operations. The Azure portal steps are platform-agnostic, but all command-line automation is Windows-oriented.
Recommendations
  • Provide equivalent examples using bash and curl for Microsoft Graph API operations, especially for PATCH requests to update user attributes.
  • Include instructions for installing and using cross-platform tools (such as Azure CLI or direct REST API calls) for Linux/macOS users.
  • When presenting PowerShell examples, also offer Linux/macOS alternatives side-by-side, or clearly indicate platform-specific sections.
  • Reference cross-platform scripting options before or alongside Windows/PowerShell tools, rather than defaulting to Windows-first.
  • Explicitly state platform compatibility for each tool or command, and link to relevant installation guides for non-Windows 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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell scripts and instructions for deploying Azure AD B2C custom policies in Azure Pipelines. All automation examples use PowerShell, and there is no mention of Bash, shell scripting, or cross-platform alternatives. The pipeline task instructions only reference the PowerShell task, with no guidance for Linux agents or non-Windows environments.
Recommendations
  • Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux agents.
  • Explicitly mention that Azure Pipelines agents can run on Linux and macOS, and provide instructions for those platforms.
  • Include guidance on using cross-platform tools (e.g., Azure CLI, curl) to interact with Microsoft Graph API.
  • Add notes on how to adapt the deployment process for non-Windows environments, including any required changes to scripts or pipeline tasks.
  • Ensure that examples and instructions are presented in a platform-neutral way, or offer both Windows and Linux options side-by-side.
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-11 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 only PowerShell examples for key generation and certificate creation, referencing Windows-specific tools (PowerShell cmdlets), and omitting equivalent Linux/macOS commands or guidance. Windows tooling is mentioned first and exclusively in critical steps, such as generating symmetric keys and self-signed certificates, with no mention of cross-platform alternatives.
Recommendations
  • Add Linux and macOS equivalents for key generation (e.g., using OpenSSL for symmetric keys and certificates).
  • Provide bash or shell script examples alongside PowerShell for cross-platform parity.
  • Reference cross-platform tools (e.g., OpenSSL, ssh-keygen) before or alongside Windows-specific tools.
  • Explicitly state that the steps can be performed on non-Windows platforms and link to relevant documentation.
  • Include sample commands for generating JWTs and certificates on Linux/macOS environments.
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-11 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 strong Windows bias by exclusively referencing Windows-specific tools (AD FS Management snap-in, Server Manager, Event Viewer), providing PowerShell-only examples for configuration, and omitting any mention of Linux alternatives or cross-platform approaches for AD FS management or troubleshooting. All procedural steps assume a Windows environment and do not address scenarios for administrators using Linux or non-Windows platforms.
Recommendations
  • Add notes or sections clarifying that AD FS is a Windows-only technology, but acknowledge cross-platform SAML providers and how they might integrate with Azure AD B2C.
  • Where possible, provide equivalent steps or references for managing SAML identity providers from Linux (e.g., using open-source SAML IdPs like Shibboleth or SimpleSAMLphp) and how to configure them with Azure AD B2C custom policies.
  • For certificate creation and management, include Linux/openssl command-line examples alongside Windows instructions.
  • When discussing troubleshooting, mention how to access logs or debug SAML transactions from non-Windows environments, such as using syslog or application logs in Linux-based SAML providers.
  • Clearly indicate in prerequisites that the guide is specific to AD FS (Windows), and link to documentation for integrating other SAML providers on different platforms.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing AD FS management via Server Manager and GUI steps that are only available on Windows. There are no examples or instructions for configuring AD FS from Linux or cross-platform tools, nor are PowerShell or command-line alternatives provided. The documentation assumes the reader is using Windows Server and its graphical tools, with no mention of Linux-compatible approaches or open-source equivalents.
Recommendations
  • Provide command-line instructions (e.g., PowerShell, Windows CMD) for AD FS configuration, which could be run remotely or scripted.
  • Clarify whether AD FS management can be performed via REST APIs or other cross-platform tools, and provide examples if available.
  • Explicitly state that AD FS is a Windows-only technology, but suggest alternatives for Linux environments (such as using other OpenID Connect providers).
  • Add a note or section for users on non-Windows platforms, explaining their options and any limitations.
  • Where possible, link to documentation for configuring OpenID Connect providers on Linux, or suggest open-source equivalents.
GitHub Create Pull Request
Active Directory B2C Set up sign-up and sign-in with a Microsoft Account ...e-directory-b2c/identity-provider-microsoft-account.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references the Azure portal web UI and Microsoft-specific tools and patterns, with no mention of Linux command-line alternatives, cross-platform CLI usage, or parity for Linux users. All instructions assume use of the Azure portal, which is platform-agnostic but heavily oriented toward Windows users and workflows. There are no examples using Azure CLI, REST API, or other automation-friendly, cross-platform tools. No Linux-specific considerations or examples are provided.
Recommendations
  • Add equivalent instructions using Azure CLI and/or PowerShell, and ensure Azure CLI examples are presented before or alongside PowerShell to support Linux and macOS users.
  • Include REST API examples for application registration and configuration steps to enable automation and cross-platform usage.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, and provide links to CLI documentation for users who prefer command-line workflows.
  • Where secrets or configuration files are referenced, provide guidance on secure storage and management for Linux environments (e.g., using environment variables, key vaults, or secure files).
  • Review and update documentation to ensure that Linux and macOS users are not required to use Windows-specific tools or patterns, and that all steps can be completed on any platform.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias, particularly in the 'Revoke a consumer user's session' section, where only Windows PowerShell and Microsoft Graph PowerShell are mentioned and example commands are given. There is no mention of Linux or cross-platform alternatives, nor are examples provided for Bash, Azure CLI, or other non-Windows environments. The instructions and tooling references assume a Windows environment, which may exclude or inconvenience Linux and macOS users.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, such as using Bash, Azure CLI, or Microsoft Graph API via curl.
  • Clarify that Microsoft Graph PowerShell is cross-platform and can be used in PowerShell Core on Linux/macOS, or provide explicit instructions for these platforms.
  • Include REST API examples (e.g., using curl or httpie) for session revocation and other tasks, to ensure parity for users who do not use PowerShell.
  • When mentioning tools or commands, avoid specifying 'Windows PowerShell' unless necessary, and instead use 'PowerShell' or specify cross-platform compatibility.
  • Add a note or section highlighting platform-agnostic approaches for all tasks described.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits 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). The only concrete application setup guidance is for IIS, a Windows-specific technology. No Linux-based alternatives or instructions are mentioned, and Windows terminology (IIS, .NET-style URLs) appears before or instead of cross-platform options.
Recommendations
  • Provide Linux-based web application examples, such as Apache or Nginx, alongside IIS.
  • Include setup instructions or links for configuring a header-based web application on Linux.
  • Mention Linux tools and patterns (e.g., systemd, SELinux, Linux certificate stores) where relevant.
  • Ensure troubleshooting and deployment steps reference both Windows and Linux environments.
  • Use neutral terminology when referring to web applications, avoiding Windows-specific language unless alternatives are also presented.
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-11 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 exclusively providing instructions and examples using Microsoft Graph PowerShell, explicitly stating installation on a Windows workstation or server. No Linux or cross-platform alternatives (such as Bash, CLI, or SDK usage) are mentioned. The only automation example is PowerShell, and there is no guidance for Linux users or those using non-Windows environments.
Recommendations
  • Provide equivalent instructions for Linux and macOS environments, such as using Microsoft Graph CLI, Bash scripts, or REST API calls.
  • Explicitly mention cross-platform options for installing and using Microsoft Graph tools.
  • Include non-PowerShell examples for key operations (e.g., deleting users) using REST API or Graph CLI.
  • Clarify that the solution is not limited to Windows and provide links to relevant Linux/macOS documentation.
  • Add a section or note highlighting platform-agnostic approaches for integration and automation.
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-11 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 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 gap.
Recommendations
  • Add Linux/macOS instructions for creating self-signed certificates, such as using OpenSSL, alongside the PowerShell example.
  • Explicitly mention that certificate generation can be performed on any OS and provide equivalent commands for popular platforms.
  • Where PowerShell is referenced, clarify that it is a Windows-specific tool and offer alternatives for other operating systems.
  • Review other sections for subtle platform assumptions (e.g., file paths, certificate formats) and ensure cross-platform guidance is provided.
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-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 provides only a PowerShell script for monitoring directory quota usage, which is specific to Windows environments. There are no equivalent examples for Linux or cross-platform tools (such as Bash, curl, or Python). The use of PowerShell and Windows-centric tooling is presented as the sole method, with no mention of alternatives or parity for Linux/macOS users.
Recommendations
  • Add equivalent examples using Bash and curl for Linux/macOS users to obtain the access token and call the Microsoft Graph API.
  • Provide a cross-platform example using Python (requests library) to demonstrate how to perform the same API calls.
  • Explicitly mention that PowerShell is Windows-specific and offer guidance for Linux users (such as using PowerShell Core, curl, or other scripting languages).
  • Ensure that future documentation presents cross-platform examples side-by-side or in tabs, rather than defaulting to Windows/PowerShell first.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically accessing audit logs, 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) indicate a Windows-centric approach. There is no mention of Linux-native tools or cross-platform scripting alternatives.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs.
  • Provide a Python script example using the requests library to demonstrate cross-platform access.
  • Explicitly mention that the API can be accessed from any OS and provide guidance for Linux/macOS users.
  • Reference Linux tools (e.g., wget, curl) alongside PowerShell, and avoid presenting Windows tools first or exclusively.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide examples for both.
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-10 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 Windows bias by exclusively mentioning Microsoft PowerShell as an example HTTP client for testing POST requests, without referencing Linux or cross-platform alternatives. No Linux-specific tools (such as curl or wget) are suggested, and PowerShell is mentioned before any other tool, reinforcing a Windows-centric approach.
Recommendations
  • Include Linux and cross-platform command-line examples using tools like curl or wget for making HTTP requests.
  • Mention PowerShell as one option among several, rather than the only example, and avoid listing it first unless contextually appropriate.
  • Add explicit instructions or examples for Linux users, ensuring parity in guidance for both Windows and Linux environments.
  • Consider referencing cross-platform tools (e.g., Postman, HTTPie) to make the documentation more inclusive.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation shows evidence of Windows bias. The instructions for generating a GUID mention PowerShell first ('new-guid' command in Microsoft PowerShell) before suggesting an online generator, and the scripting example for obtaining an access token uses PowerShell before cURL. There are no explicit Linux shell or tool examples for GUID generation, and the ordering of examples and tool references favors Windows environments.
Recommendations
  • Provide Linux shell equivalents for GUID generation, such as 'uuidgen' or 'openssl rand -hex 16', alongside PowerShell.
  • Present cURL and other cross-platform examples before or alongside PowerShell scripts to avoid Windows-first ordering.
  • Explicitly mention that all steps can be performed on Linux/macOS and provide relevant command-line examples.
  • Where Windows-specific tools are referenced, offer Linux/macOS alternatives in equal detail.
  • Review screenshots and instructions to ensure they are not exclusively Windows/Azure Portal-centric, or add notes for Linux users where appropriate.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation 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). There are no Linux-specific instructions or parity for application setup, and Windows tooling is mentioned exclusively in the context of the test application.
Recommendations
  • Include Linux-based web server examples (e.g., Apache, Nginx) alongside IIS for testing the integration.
  • Provide setup instructions or links for configuring header-based applications on Linux platforms.
  • Mention Linux equivalents for SSL certificate management and application deployment.
  • Ensure troubleshooting and configuration steps are platform-agnostic or offer guidance for both Windows and 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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell scripts and PowerShell pipeline tasks for deploying Azure AD B2C custom policies, with no mention of Bash, shell, or cross-platform scripting alternatives. All code and pipeline instructions assume the use of PowerShell, which is traditionally Windows-centric, and there are no Linux-specific or platform-neutral examples provided.
Recommendations
  • Provide equivalent Bash or shell script examples for deploying policies using Microsoft Graph API, suitable for Linux agents.
  • Include instructions for adding Bash or cross-platform script tasks in Azure Pipelines, alongside PowerShell.
  • Clarify platform compatibility for the PowerShell script (e.g., does it work on PowerShell Core on Linux/macOS?) and, if so, mention how to run it on non-Windows agents.
  • Add a section comparing Windows and Linux agent setup for this deployment scenario, highlighting any differences or considerations.
  • Explicitly state that users can choose either Windows or Linux agents, and provide guidance for both.
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-10 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 Windows bias in its instructions for running the SPA application. The final step uses PowerShell syntax ('npm ./index.js') and does not provide equivalent Linux/macOS shell commands. There is no mention of Linux or macOS environments, nor are alternative commands or considerations for those platforms included. The examples and instructions implicitly assume a Windows environment, which may confuse or hinder users on other platforms.
Recommendations
  • Provide both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) command examples for running the application, e.g., 'node index.js' instead of 'npm ./index.js'.
  • Explicitly state that the instructions are cross-platform and clarify any platform-specific differences.
  • Avoid using PowerShell-specific syntax unless necessary, and offer alternatives for other shells.
  • Add notes or sections addressing Linux/macOS users, including common commands and troubleshooting tips.
  • Test and validate the instructions on multiple platforms to ensure parity.
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-10 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 only PowerShell examples for key generation and certificate creation, referencing Windows-specific tools (PowerShell cmdlets), and omitting equivalent Linux/macOS commands or tools. The guidance for creating self-signed certificates and symmetric keys is exclusively Windows-centric, with no mention of cross-platform alternatives. This may hinder Linux or macOS developers from following the instructions without additional research.
Recommendations
  • Provide equivalent Linux/macOS command-line examples for key generation (e.g., using openssl for symmetric keys and certificates).
  • Mention cross-platform tools (such as openssl, ssh-keygen) alongside PowerShell, and clarify which steps are OS-agnostic.
  • Reorder examples to present cross-platform or OS-neutral approaches first, or in parallel with Windows-specific instructions.
  • Add notes or links to external resources for Linux/macOS users to generate keys and certificates.
  • Explicitly state that the process can be completed on any OS, and highlight any platform-specific caveats.
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-10 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 clear Windows bias. All examples and procedures for configuring AD FS are based on Windows tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no references to Linux equivalents, nor any guidance for performing similar tasks on non-Windows platforms. Troubleshooting steps and AD FS management are exclusively described using Windows GUI and command-line tools, with no mention of cross-platform or Linux-compatible alternatives.
Recommendations
  • Explicitly state that AD FS is a Windows-only service, but clarify any Azure AD B2C steps that are platform-agnostic.
  • Where possible, provide guidance for SAML identity provider integration using open-source or Linux-based SAML providers (e.g., Shibboleth, SimpleSAMLphp) alongside AD FS.
  • Include troubleshooting steps for SAML integration that are not dependent on Windows tools, such as using SAML-tracer browser extensions, curl, or openssl for certificate inspection.
  • If PowerShell is required, mention alternatives for scripting on Linux (e.g., PowerShell Core, Bash scripts) and clarify which steps are strictly Windows-only.
  • Add notes or links for users who may be running Azure AD B2C integration from non-Windows environments, explaining what parts of the process are platform-dependent.
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-10 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 exclusively providing PowerShell examples for testing the REST API and referencing Microsoft PowerShell as the suggested HTTP client. No equivalent Linux/macOS command-line examples (e.g., curl) are provided, and Windows tools are mentioned before any cross-platform alternatives. This may hinder Linux/macOS users from following the instructions seamlessly.
Recommendations
  • Add Linux/macOS command-line examples using curl or httpie for making HTTP requests to the REST API.
  • Mention cross-platform tools (curl, wget, httpie) alongside PowerShell, and provide usage instructions for each.
  • Rephrase sections to avoid suggesting Windows tools as the default or only option.
  • Explicitly state that the instructions apply to all platforms and clarify any platform-specific steps.
  • Include screenshots or terminal output from Linux/macOS environments where relevant.
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-10 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 environments by providing PowerShell examples exclusively for password expiry configuration, referencing Windows-centric tools (PowerShell, Azure portal), and omitting equivalent Linux or cross-platform CLI instructions. All procedural steps and code samples assume use of Windows-based interfaces or tools, with no mention of Linux shell commands, Azure CLI, or REST API usage from non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, especially for password expiry configuration.
  • Include REST API usage examples with curl or httpie for Linux/macOS users.
  • Add explicit instructions for performing Azure portal steps from non-Windows browsers and clarify platform neutrality.
  • Ensure that all code samples and procedural instructions are presented in a cross-platform manner, or offer both Windows and Linux/macOS alternatives.
  • Review and update documentation to avoid assuming the use of Windows tools as the default or only option.
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-10 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 Windows bias by exclusively referencing Windows-based tools (AD FS Management, Server Manager), providing step-by-step instructions for GUI configuration in Windows environments, and omitting any mention of Linux equivalents or command-line alternatives. All examples and workflows assume the use of Windows Server and AD FS, with no guidance for Linux-based identity providers or cross-platform scenarios.
Recommendations
  • Include instructions or references for configuring OpenID Connect identity providers using cross-platform or Linux-based tools (e.g., Shibboleth, Keycloak, or other SSO solutions).
  • Provide PowerShell and command-line examples alongside GUI steps, and mention if these can be run on non-Windows platforms (e.g., via Azure CLI, REST API, or other automation tools).
  • Add a section comparing AD FS with Linux-compatible alternatives, and clarify which steps are specific to Windows environments.
  • Explicitly state the platform requirements and limitations at the beginning of the documentation.
  • Where possible, link to documentation for configuring OpenID Connect providers on Linux or in cloud-native environments.
GitHub Create Pull Request
Active Directory B2C Set up sign-up and sign-in with a Microsoft Account ...e-directory-b2c/identity-provider-microsoft-account.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Azure portal (web UI) for all configuration steps and does not mention or provide examples for command-line tools, automation, or scripting methods available on Linux (such as Azure CLI or REST API). There are no references to Linux-specific workflows, and the documentation assumes use of graphical tools commonly associated with Windows environments. The order of presentation and terminology is also Windows-centric, with no parity for Linux users.
Recommendations
  • Add equivalent instructions using Azure CLI and/or REST API for all configuration steps, including app registration, secret creation, and identity provider setup.
  • Explicitly mention that these steps can be performed on any OS and provide cross-platform command-line examples.
  • Include links to relevant Azure CLI documentation and sample scripts for Linux/macOS users.
  • Clarify that the Azure portal is web-based and accessible from any OS, but highlight automation options for users who prefer non-GUI workflows.
  • Where possible, provide PowerShell and Bash/CLI examples side-by-side to ensure parity.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Revoke a consumer user's session' section, where only Windows PowerShell is mentioned and all command examples are given in PowerShell syntax. There is no mention of Linux or cross-platform alternatives (such as Bash, Azure CLI, or direct REST API usage) for these tasks. The instructions and tooling are presented from a Windows-first perspective, and Linux users are not provided with equivalent guidance.
Recommendations
  • Include examples using Bash or shell commands for Linux/macOS users, especially for Microsoft Graph API usage via curl or similar tools.
  • Clarify that Microsoft Graph PowerShell is cross-platform and provide installation and usage instructions for Linux/macOS (e.g., using pwsh).
  • Add Azure CLI examples where possible, or reference REST API usage for tasks like session revocation.
  • Avoid phrases like 'In your Windows PowerShell' and instead use 'In your terminal' or specify instructions for multiple platforms.
  • Explicitly mention platform compatibility for all tools and commands, ensuring parity for Linux and macOS users.
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-10 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 using PowerShell for certificate creation and random string generation, without providing Linux or cross-platform alternatives. Visual Studio is mentioned as the publishing tool, which is primarily a Windows application. There are no examples or instructions for Linux/macOS users for these critical steps, and Windows-centric tools and patterns are presented first and exclusively.
Recommendations
  • Provide equivalent Linux/macOS commands for certificate creation (e.g., using OpenSSL).
  • Include bash or cross-platform scripts for random string generation.
  • Mention alternative publishing methods (such as Azure CLI, GitHub Actions, or VS Code) that work on Linux/macOS.
  • Clearly indicate which steps are platform-specific and offer parity instructions for other operating systems.
  • Add a note or table summarizing platform compatibility for each major step.
GitHub Create Pull Request
← Previous Page 2 of 16 Next →