Active Directory B2C

566
Total Pages
521
Linux-Friendly Pages
45
Pages with Bias
8.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

101 issues found
Showing 1-25 of 101 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-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 page exhibits a strong Windows bias, with all AD FS configuration and troubleshooting steps relying exclusively on Windows tools (AD FS Management snap-in, Server Manager, Event Viewer) and PowerShell cmdlets. No Linux or cross-platform alternatives are provided, and Windows-specific instructions are presented as the only way to complete critical tasks. This creates significant friction for users on Linux or macOS, who cannot natively run these tools.
Recommendations
  • Explicitly state that AD FS is a Windows-only service and clarify platform requirements at the start of the documentation.
  • Provide guidance for Linux/macOS users, such as using remote desktop or virtualization to access a Windows environment for AD FS management.
  • Where possible, offer cross-platform alternatives for certificate creation, metadata inspection, and SAML troubleshooting (e.g., OpenSSL, curl, SAML toolkits).
  • Include references to Azure AD B2C SAML integration with non-Windows identity providers for broader parity.
  • Add notes or links to documentation for managing SAML providers on Linux-based systems, if relevant.
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 Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing AD FS (Active Directory Federation Services), which is a Windows Server feature. All configuration steps and UI references (Server Manager, AD FS Management) are Windows-specific, with no mention of Linux/macOS equivalents or alternatives. There are no command-line examples (e.g., PowerShell or bash), but all instructions assume access to Windows GUI tools. No Linux-compatible identity provider setup or cross-platform alternatives are discussed.
Recommendations
  • Acknowledge that AD FS is a Windows-only technology and suggest cross-platform alternatives for Linux/macOS environments, such as using other OpenID Connect providers (e.g., Keycloak, IdentityServer).
  • Provide guidance or links for setting up OpenID Connect providers on Linux, and how to integrate them with Azure AD B2C using custom policies.
  • If possible, include command-line instructions or automation options (e.g., PowerShell, CLI, REST API) for AD FS setup, and clarify their platform requirements.
  • Add a note early in the documentation clarifying that the instructions are specific to Windows Server/AD FS and recommend alternatives for non-Windows users.
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, with no equivalent example for Linux/macOS users (e.g., Bash, curl, or Python). The use of PowerShell-specific cmdlets and .NET objects assumes a Windows environment and excludes users on other platforms from easily following the instructions.
Recommendations
  • Add a Bash/curl example for Linux/macOS users to obtain the access token and call the Microsoft Graph API.
  • Provide a cross-platform Python example using the requests library.
  • Explicitly mention that the PowerShell script is for Windows and offer alternatives for other platforms.
  • Consider reordering examples so that cross-platform solutions appear first or alongside Windows-specific instructions.
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 06:20
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 Server Manager and GUI steps, with no mention of Linux-compatible alternatives or command-line options. All examples and instructions assume use of Windows tools and interfaces, and there are no Linux or cross-platform examples provided.
Recommendations
  • Include PowerShell and command-line instructions for AD FS management, which can be run on Windows Server Core or remotely.
  • Explicitly state that AD FS is a Windows-only service, and suggest alternatives for Linux environments (such as using other OpenID Connect providers).
  • Provide guidance or links for integrating non-Windows OpenID Connect providers with Azure AD B2C.
  • If possible, mention open-source or cross-platform equivalents for AD FS functionality.
  • Clarify prerequisites regarding required OS and tools, so Linux/macOS users understand the limitations up front.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only a PowerShell script for monitoring directory quota usage, which is specific to Windows environments. There are no examples or instructions for Linux or cross-platform alternatives (such as Bash, curl, or Python). This may hinder users on Linux or macOS from easily following the tutorial.
Recommendations
  • Add equivalent Linux/macOS examples using Bash and curl or Python (e.g., using curl for token acquisition and API calls).
  • Explicitly mention that the PowerShell script is for Windows and provide cross-platform alternatives.
  • Consider using platform-neutral tools (like Azure CLI or REST API examples) where possible.
  • Add a section on troubleshooting or adapting the instructions for non-Windows environments.
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: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias, especially in the 'How-to guide' sections for generating symmetric and asymmetric keys. PowerShell is exclusively used for key and certificate generation, with no mention of Linux or cross-platform alternatives. Windows tools and patterns are referenced first and exclusively, and there are no examples or instructions for performing these tasks on Linux or macOS.
Recommendations
  • Add equivalent Linux/macOS instructions for key and certificate generation, such as using OpenSSL for both symmetric key and self-signed certificate creation.
  • Provide cross-platform code samples (e.g., bash scripts, OpenSSL commands) alongside PowerShell examples.
  • Explicitly mention that the steps can be performed on non-Windows platforms and link to relevant external documentation for Linux/macOS users.
  • Ensure that references to platform-specific tools (like PowerShell) are balanced with alternatives for other operating systems.
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 Windows bias primarily in the 'Revoke a consumer user's session' section, where only Windows PowerShell and Microsoft Graph PowerShell are mentioned and example commands are provided. There is no mention of Linux or cross-platform alternatives, nor are CLI or REST API examples given. The instructions and tooling assume a Windows environment, and Linux users are not provided with equivalent guidance.
Recommendations
  • Include examples using Microsoft Graph API via curl or other cross-platform tools for session revocation.
  • Mention that Microsoft Graph PowerShell can be installed and used on Linux/macOS, and provide instructions for those platforms.
  • Provide Azure CLI or REST API examples where possible, especially for tasks like session revocation.
  • Avoid language that assumes Windows as the default environment (e.g., 'In your Windows PowerShell...').
  • Add notes or sections specifically for Linux/macOS users to ensure parity in guidance and tooling.
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-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 Visual Studio and linking to Windows-centric deployment instructions for publishing the API, without mentioning Linux alternatives or cross-platform deployment methods. There are no examples or guidance for deploying the API from Linux environments, nor are Linux-native tools or workflows discussed. 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, which are available on Linux.
  • Provide Linux-specific deployment examples, such as using the dotnet CLI or zip deployment via Azure CLI.
  • Reference documentation for deploying from Linux or macOS environments alongside Visual Studio instructions.
  • Avoid assuming Visual Studio as the default tool; mention alternatives like VS Code or JetBrains Rider.
  • Ensure that all steps (such as configuring app settings and uploading policy files) are described in a way that is platform-agnostic or include Linux/macOS equivalents.
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-10 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 bias towards Windows environments by exclusively referencing PowerShell for self-signed certificate creation and omitting equivalent Linux/macOS commands or tooling. The only explicit method for local certificate generation is via PowerShell, with no mention of OpenSSL or other cross-platform alternatives. This may hinder Linux and macOS users who do not have access to PowerShell or prefer native tools.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation, such as OpenSSL commands, alongside PowerShell instructions.
  • Explicitly mention cross-platform tools and workflows where possible, ensuring parity for non-Windows environments.
  • Add examples and screenshots for Linux/macOS certificate management and upload processes.
  • Review other sections for any implicit Windows-first assumptions and clarify that all steps can be performed on any OS with appropriate tooling.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md ...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority View Details →
Scanned: 2026-01-09 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 a Windows bias by recommending Microsoft PowerShell as the example HTTP client for testing the token request, without mentioning any Linux or cross-platform alternatives (such as curl or httpie). No Linux-specific or cross-platform command-line examples are provided, and the only tool explicitly referenced is PowerShell, which is traditionally associated with Windows environments. This may lead Linux users to feel unsupported or unsure about how to perform the same actions on their platform.
Recommendations
  • Include examples using cross-platform tools such as curl or httpie for making HTTP requests.
  • Explicitly mention that PowerShell is available on Linux and macOS, or provide alternative Linux-native commands.
  • Add a section or note listing common tools for both Windows and Linux users to test HTTP requests (e.g., curl, wget, httpie, PowerShell).
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/force-password-reset.md .../articles/active-directory-b2c/force-password-reset.md
High Priority View Details →
Scanned: 2026-01-09 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 configuring password expiry duration, referencing Windows-centric tools (Azure portal, PowerShell), and omitting equivalent Linux/macOS CLI or scripting examples. No mention is made of using cross-platform tools like Azure CLI or Bash scripts, and PowerShell is presented as the sole automation method.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform, for tasks such as updating password expiry settings.
  • Explicitly mention that PowerShell examples can be run on macOS and Linux using PowerShell Core, or provide Bash/cURL examples for Microsoft Graph API calls.
  • Include instructions for using the Azure portal from non-Windows operating systems, or clarify that the portal is web-based and OS-agnostic.
  • Wherever PowerShell is used, provide alternative command-line examples (e.g., using cURL or HTTPie) for REST API operations.
  • Review the order of tool presentation to avoid always listing Windows/PowerShell first; consider starting with cross-platform or REST-based solutions.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/id-token-hint.md ...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority View Details →
Scanned: 2026-01-09 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 demonstrates a clear Windows bias. All command-line examples for generating cryptographic keys and certificates use PowerShell, a Windows-specific tool. The guide for creating a self-signed certificate only provides a PowerShell example and explicitly references the Windows environment. There are no equivalent Linux or cross-platform command-line examples (e.g., using OpenSSL or Bash). The documentation does not mention or link to Linux tools or workflows, and Windows tools are presented as the default and only option.
Recommendations
  • Provide equivalent Linux/macOS examples for generating symmetric keys (e.g., using OpenSSL or /dev/urandom in Bash).
  • Add instructions for creating self-signed certificates on Linux/macOS using OpenSSL.
  • When referencing platform-specific tools (like PowerShell), clarify that the instructions are for Windows and provide alternatives for other platforms.
  • Consider using cross-platform tools or scripts where possible, or at least link to relevant Linux documentation.
  • Reorder or parallelize sections so that Linux and Windows instructions are given equal prominence, rather than Windows-first.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/client-credentials-grant-flow.md .../active-directory-b2c/client-credentials-grant-flow.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias in several ways. The only explicit command-line example for generating a GUID uses PowerShell ('new-guid'), a Windows-specific tool, and mentions it before suggesting an online generator. The scripting example for obtaining an access token is given first in PowerShell, with a cURL (Linux/macOS-friendly) example following. There are no Linux shell or cross-platform alternatives for the GUID generation or other administrative tasks. Windows terminology and tools are referenced without Linux equivalents.
Recommendations
  • Provide Linux and macOS equivalents for all command-line examples, such as using 'uuidgen' for GUID generation.
  • When listing multiple platform options, alternate or randomize the order, or present them side-by-side rather than always listing Windows/PowerShell first.
  • Explicitly mention cross-platform tools (e.g., cURL, HTTPie, uuidgen) and provide examples for each.
  • Avoid referencing Windows-specific tools (like PowerShell) without also including Linux/macOS alternatives.
  • Add a section or callout for Linux/macOS users, ensuring parity in instructions and tooling.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-directory-quota.md ...ive-directory-b2c/tenant-management-directory-quota.md
High Priority View Details →
Scanned: 2026-01-09 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 interacting with the Microsoft Graph API to monitor directory quota, with no equivalent examples for Linux or cross-platform tools (e.g., Bash, curl, Python). The exclusive use of PowerShell and Windows-centric command patterns demonstrates a Windows bias, making it less accessible for Linux or macOS administrators.
Recommendations
  • Provide equivalent examples using Bash with curl or HTTPie, which are commonly available on Linux and macOS.
  • Include a cross-platform example using Python and the requests library, which works on all major operating systems.
  • Clearly indicate that PowerShell Core (pwsh) is available on Linux/macOS if PowerShell is to be used, and provide installation guidance.
  • Reorder or parallelize examples so that Linux/macOS options are presented alongside or before Windows/PowerShell examples.
  • Explicitly state that the API can be accessed from any platform, not just Windows.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md ...ob/main/articles/active-directory-b2c/access-tokens.md
High Priority View Details →
Scanned: 2026-01-06 22:28
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 the POST request, without referencing cross-platform or Linux-native tools such as curl or wget. No Linux-specific or cross-platform command-line examples are provided, and the only tool recommendation is Windows-centric. This may hinder Linux developers or those using non-Windows environments from easily following the instructions.
Recommendations
  • Include examples using curl and/or wget for making HTTP requests, alongside or before PowerShell.
  • Explicitly mention that any HTTP client can be used, and provide links to documentation for popular Linux and cross-platform tools.
  • Add sample command-line requests for Linux/macOS environments.
  • Ensure tool recommendations are platform-neutral or presented in parallel (e.g., 'You can use PowerShell (Windows), curl (Linux/macOS), or any HTTP client...').
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/force-password-reset.md .../articles/active-directory-b2c/force-password-reset.md
High Priority View Details →
Scanned: 2026-01-06 22:28
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 command-line operations (such as updating password expiry duration), referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent instructions for Linux/macOS environments (such as using Azure CLI, Bash, or REST API via curl). The order of presentation also favors Windows tools, with no mention of cross-platform alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
  • Include REST API usage examples with curl or HTTPie for platform-neutral instructions.
  • Clearly indicate that PowerShell examples are for Windows and offer alternatives for other operating systems.
  • Reorder sections or add notes to ensure cross-platform tools are presented alongside or before Windows-specific tools.
  • Reference installation and usage of Microsoft Graph PowerShell module on non-Windows platforms, if supported.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/https-cipher-tls-requirements.md .../active-directory-b2c/https-cipher-tls-requirements.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific resources (such as Schannel cipher suites), linking to Windows-focused articles, and omitting Linux-specific guidance or examples. No Linux/OpenSSL equivalents or commands are provided for checking or configuring TLS/cipher suites.
Recommendations
  • Include Linux/OpenSSL equivalents for checking and configuring TLS and cipher suites (e.g., using openssl ciphers, nmap, or testssl.sh).
  • Add links to Linux-focused documentation or guides for enabling/disabling TLS versions and cipher suites.
  • Provide example commands for both Windows (e.g., PowerShell) and Linux (e.g., bash/openssl) to check endpoint compatibility.
  • Ensure that references to Windows tools (like Schannel) are balanced with references to common Linux libraries (like OpenSSL or GnuTLS).
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/id-token-hint.md ...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias, particularly in the 'How-to guide' sections. All command-line examples for generating keys and certificates use PowerShell and reference Windows-specific tools (e.g., New-SelfSignedCertificate). There are no equivalent examples for Linux or macOS environments, and Windows tooling is mentioned first and exclusively. This may hinder cross-platform adoption and usability for developers on non-Windows systems.
Recommendations
  • Provide equivalent Linux/macOS command-line examples for generating symmetric keys (e.g., using OpenSSL or /dev/urandom).
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell example.
  • When referencing tools or commands, mention cross-platform or OS-agnostic options first, or present them in parallel.
  • Clarify in the documentation that the examples are platform-specific and provide links or guidance for other platforms.
  • Consider including sample scripts or commands for common developer environments (Bash, zsh, etc.) to improve accessibility.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs-saml.md ...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All administrative steps for configuring AD FS are described using Windows-specific tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux equivalents or cross-platform alternatives provided, and all examples and troubleshooting steps assume a Windows environment. Linux-based AD FS alternatives or SAML identity providers are not mentioned.
Recommendations
  • Provide guidance or references for configuring SAML identity providers on Linux (e.g., Shibboleth, SimpleSAMLphp) as alternatives to AD FS.
  • Include example commands or steps for managing certificates and SAML metadata using cross-platform tools (e.g., OpenSSL for certificate creation, curl/wget for metadata retrieval).
  • When referencing PowerShell or Windows-specific tools, add equivalent commands or instructions for Linux environments where possible.
  • Clarify at the beginning that the guide is Windows/AD FS-specific, and link to documentation for Linux-based SAML providers if full parity is not feasible.
  • Add troubleshooting steps that are relevant for Linux-based SAML providers, such as checking logs or configuration files.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references the Azure portal (a web UI) for all configuration steps, with no mention of command-line alternatives (such as Azure CLI, Bash, or PowerShell). There are no Linux-specific instructions, nor are any cross-platform tools or automation options (like az CLI or REST API) demonstrated. The UI navigation patterns and terminology are strongly aligned with Windows/Entra portal conventions, and there is no guidance for users working from Linux or macOS environments.
Recommendations
  • Add equivalent instructions using Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
  • Provide REST API examples for key configuration steps, enabling automation and parity for non-Windows environments.
  • Include notes or sections clarifying that all steps can be performed from any OS via the web portal, but highlight CLI/script options for Linux users.
  • If PowerShell is referenced in related docs, ensure Bash or shell script equivalents are also provided.
  • Explicitly mention cross-platform compatibility and provide links to CLI tool installation guides for Linux and macOS.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-users-portal.md ...n/articles/active-directory-b2c/manage-users-portal.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Revoke a consumer user's session' section, where only Windows PowerShell and Microsoft Graph PowerShell examples are provided. The instructions explicitly mention 'Windows PowerShell' and do not reference Linux or cross-platform alternatives. There are no CLI, Bash, or platform-neutral examples for session revocation or other tasks, and Windows-centric tools are mentioned before any Linux equivalents (which are absent).
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or platform-neutral commands for session revocation and other tasks.
  • Clarify that Microsoft Graph PowerShell is cross-platform and provide installation and usage instructions for Linux and macOS.
  • Include examples using REST API calls (e.g., with curl) for tasks like session revocation to ensure platform neutrality.
  • Avoid specifying 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or clarify cross-platform compatibility.
  • Add a note or section highlighting how Linux and macOS users can perform these operations, including any prerequisites or differences.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-idology.md .../main/articles/active-directory-b2c/partner-idology.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API. There are no examples or instructions for deploying the API from Linux or using cross-platform tools (e.g., VS Code, CLI). The documentation assumes use of Windows tooling and does not mention Linux alternatives or provide parity in deployment guidance.
Recommendations
  • Add instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
  • Include Linux-specific deployment examples (e.g., using dotnet CLI on Ubuntu, or deploying from a Linux machine).
  • Reference platform-agnostic documentation for publishing web apps to Azure, rather than only Visual Studio.
  • Explicitly state that the API can be deployed from any OS and provide links to relevant Linux/macOS guides.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-jumio.md ...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a strong Windows bias by providing only PowerShell scripts for certificate and key generation, referencing Visual Studio for deployment, and omitting any Linux or cross-platform alternatives. No bash, OpenSSL, or cross-platform CLI examples are given, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
  • Provide equivalent Linux/macOS examples for certificate creation using OpenSSL.
  • Include bash or cross-platform shell commands for generating random strings.
  • Mention and provide instructions for deploying the API using cross-platform tools (e.g., Azure CLI, GitHub Actions, or VS Code).
  • Clearly indicate that PowerShell is Windows-specific and offer alternatives for non-Windows users.
  • Add a section or callouts for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-saviynt.md .../main/articles/active-directory-b2c/partner-saviynt.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based instructions for critical steps (such as enabling user deletion), explicitly stating the need for a 'Windows workstation or server,' and referencing the Microsoft Graph PowerShell module without mentioning or providing alternatives for Linux or macOS users. No CLI, Bash, or cross-platform examples are given, and Windows tools and patterns are presented as the default/only option.
Recommendations
  • Provide equivalent instructions using the Microsoft Graph CLI (az or mgc) or REST API with curl, which are cross-platform and work on Linux/macOS.
  • Explicitly mention that the PowerShell module can be installed on Linux/macOS (if supported), and provide installation instructions for those platforms.
  • Add Bash or shell script examples for key operations, or reference official Microsoft documentation for non-Windows environments.
  • Avoid language that implies Windows is required (e.g., 'on a Windows workstation or server'); instead, use 'on your workstation or server' and clarify platform options.
  • Ensure all critical steps have at least one cross-platform alternative to PowerShell.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-lexisnexis.md ...in/articles/active-directory-b2c/partner-lexisnexis.md
High Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio as the primary deployment tool for the API, without mentioning Linux-compatible alternatives or providing cross-platform instructions. There are no examples or guidance for Linux users (e.g., deploying via CLI, VS Code, or GitHub Actions), and the only tool explicitly mentioned for publishing code is Visual Studio, which is primarily a Windows application.
Recommendations
  • Provide alternative deployment instructions using cross-platform tools such as the Azure CLI, Azure Cloud Shell, or Visual Studio Code.
  • Include Linux/macOS-specific examples for deploying the API (e.g., using 'dotnet publish' and 'az webapp deploy').
  • Mention Visual Studio Code as an alternative to Visual Studio for editing and deploying code, as it is available on all major platforms.
  • Ensure that any screenshots or UI instructions are not Windows-specific, or provide equivalents for other operating systems.
  • Explicitly state that the API and UI deployment steps can be performed from Linux, macOS, or Windows, and provide links to relevant documentation.
GitHub Create Pull Request
← Previous Page 1 of 5 Next →