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 51-75 of 392 flagged pages
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-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 PowerShell-based instructions for enabling Saviynt to delete users in Azure AD B2C, explicitly stating the need for a 'Windows workstation or server.' There are no equivalent instructions or examples for Linux or cross-platform environments, and no mention of alternative tools or methods (such as Azure CLI, Bash, or cross-platform PowerShell Core). This creates a clear Windows and PowerShell bias.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • If PowerShell is required, clarify that PowerShell Core (pwsh) can be used on Linux/macOS, and provide installation and usage instructions for those platforms.
  • Include explicit Linux/macOS command examples or note any platform-specific differences.
  • Avoid language that implies only Windows environments are supported unless there is a technical limitation, and state such limitations clearly if they exist.
  • Add a section or note on how to perform the same tasks from non-Windows environments, or link to relevant Microsoft documentation for cross-platform scenarios.
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 Windows bias primarily in the section on creating self-signed certificates, where only PowerShell is mentioned as the method for certificate creation outside Azure Key Vault. There are no references to Linux or cross-platform alternatives (such as OpenSSL) for certificate generation. The absence of Linux/macOS command-line examples or tool recommendations for key/certificate management may hinder non-Windows users. All portal-based instructions are platform-neutral, but command-line guidance is Windows-centric.
Recommendations
  • Add instructions and examples for creating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
  • Explicitly mention that certificate/key management can be performed on any OS, and provide links to cross-platform tools.
  • Where PowerShell is referenced, offer equivalent bash/CLI commands for Linux/macOS users.
  • Review all sections for implicit assumptions of Windows environments and clarify where steps are OS-agnostic.
  • Include troubleshooting or notes for Linux/macOS users regarding file formats (e.g., .pfx, .pem) and conversions.
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: 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 Azure AD B2C directory quota, with no equivalent example for Linux or cross-platform tools. PowerShell is a Windows-centric tool, and its exclusive use suggests a bias towards Windows users. There is no mention of alternatives such as Bash, curl, or Python, which are commonly used on Linux and macOS. The instructions and examples are presented from a Windows-first perspective, potentially excluding or inconveniencing administrators using other platforms.
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 the steps can be performed on any OS, and link to platform-specific instructions where appropriate.
  • Consider including a table or section comparing methods for Windows (PowerShell), Linux (Bash/curl), and cross-platform (Python).
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only a PowerShell script example for programmatically accessing Azure AD B2C audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash, curl, or Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) indicate a Windows-centric approach. There is no mention of Linux-native tools or scripting languages, nor are there instructions or examples for users on non-Windows platforms.
Recommendations
  • Provide equivalent examples using Bash with curl or wget to demonstrate how to access the Microsoft Graph API from Linux or macOS environments.
  • Include a cross-platform example using a widely available scripting language such as Python, which works on Windows, Linux, and macOS.
  • Explicitly mention that the API can be accessed from any platform and provide guidance for users on Linux or macOS.
  • Where PowerShell is used, note that PowerShell Core is available cross-platform, and provide installation instructions or alternatives for non-Windows users.
  • Ensure that any references to tools or environments (such as Azure Cloud Shell) clarify their cross-platform capabilities or provide alternatives.
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:34
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 areas. The only explicit command-line example for generating a GUID uses Microsoft PowerShell, with no mention of Linux alternatives (e.g., uuidgen). The PowerShell script for obtaining an access token is presented before the cURL example, and the guidance for generating GUIDs prioritizes PowerShell over platform-neutral or Linux-native tools. There is a lack of Linux-specific instructions or examples for common tasks, and Windows tools/patterns are referenced without Linux parity.
Recommendations
  • Include Linux-native command examples for generating GUIDs, such as 'uuidgen' or 'cat /proc/sys/kernel/random/uuid'.
  • Present cURL (cross-platform) examples before or alongside PowerShell scripts to avoid Windows-first ordering.
  • Explicitly mention platform-neutral or Linux alternatives wherever Windows tools (like PowerShell) are referenced.
  • Add notes or sections for Linux/macOS users, especially for steps involving command-line operations.
  • Ensure that all code snippets and tool recommendations are cross-platform or provide equivalents for each major OS.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-call-rest-api.md ...-directory-b2c/custom-policies-series-call-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). Windows tools are mentioned first and exclusively, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Include equivalent Linux/macOS command-line examples using curl or wget for making HTTP requests to the REST API.
  • Mention cross-platform tools (e.g., curl, httpie) alongside PowerShell, and provide sample commands for each.
  • Clarify that PowerShell is available on Linux and macOS, but also offer native shell examples for those platforms.
  • Where tools are referenced (e.g., HTTP client), list cross-platform options before or alongside Windows-specific tools.
  • Review other steps (e.g., file creation, running Node.js) to ensure instructions are platform-neutral or provide platform-specific notes as needed.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/deploy-custom-policies-devops.md .../active-directory-b2c/deploy-custom-policies-devops.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 using PowerShell scripts for deployment automation and pipeline tasks, with no mention of Bash, shell, or cross-platform alternatives. All code examples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for Linux or macOS users. The documentation does not provide Linux-native tooling or examples, nor does it acknowledge platform differences in running scripts or configuring pipelines.
Recommendations
  • Provide equivalent Bash or shell script examples for deploying policies, alongside PowerShell.
  • Explicitly state platform compatibility for the provided scripts and tasks, and offer guidance for Linux/macOS users.
  • Mention and demonstrate how to run deployment scripts in cross-platform agents (e.g., Ubuntu, macOS) in Azure Pipelines.
  • Include instructions for installing PowerShell Core on Linux/macOS if PowerShell is required, or offer native alternatives.
  • Reference Linux tools and patterns (e.g., curl, jq) where appropriate for interacting with Microsoft Graph API.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-spa-app.md .../active-directory-b2c/enable-authentication-spa-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing command-line instructions in PowerShell syntax (e.g., 'npm install' and 'npm ./index.js') and referencing 'command shell' without clarifying cross-platform compatibility. No explicit Linux or macOS terminal examples are given, and the only shell command block uses PowerShell formatting. There is no mention of Linux-specific considerations or alternative shell commands, which may confuse or exclude non-Windows users.
Recommendations
  • Provide explicit instructions for Linux/macOS users, such as using 'bash' or 'sh' syntax (e.g., 'node index.js' instead of 'npm ./index.js').
  • Replace PowerShell-specific command blocks with generic shell commands or show both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) equivalents side-by-side.
  • Clarify that the steps are cross-platform and note any OS-specific differences, such as file paths, permissions, or package installation nuances.
  • Avoid using PowerShell formatting for generic Node.js commands, as these are typically run in bash/zsh/cmd as well.
  • Add a section or note on running the SPA application on Linux/macOS, including troubleshooting tips for those platforms.
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:34
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-based examples for password expiry configuration, referencing Windows-centric tools (PowerShell modules), and omitting equivalent Linux/macOS command-line instructions. All procedural steps involving command-line interaction are shown using PowerShell, with no mention of alternatives such as Bash, curl, or cross-platform CLI tools. This may hinder Linux or macOS administrators from easily following the instructions.
Recommendations
  • Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API via curl, or Bash scripts.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide installation instructions for non-Windows platforms.
  • Reorder or supplement command-line sections to present cross-platform approaches before or alongside Windows/PowerShell methods.
  • Include notes or links to documentation for Linux/macOS users, clarifying how to perform the same operations outside of Windows environments.
  • Audit future documentation for command-line instructions to ensure parity between Windows and non-Windows platforms.
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-09 00:34
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 Windows bias by exclusively referencing Windows-specific tools (AD FS Management snap-in, Server Manager, Event Viewer), providing PowerShell commands for configuration, and omitting any mention of Linux equivalents or cross-platform alternatives. All administrative steps and troubleshooting are described using Windows UI and tooling, with no guidance for Linux-based AD FS deployments or command-line alternatives.
Recommendations
  • Provide equivalent instructions for managing AD FS using command-line tools (where possible) that are available on Linux, or clarify AD FS is Windows-only and suggest alternatives for Linux environments.
  • Mention that AD FS is a Windows Server feature, and for Linux users, suggest SAML-compatible alternatives (e.g., Shibboleth, SimpleSAMLphp) and link to relevant integration guides.
  • Include troubleshooting steps that can be performed via command-line (e.g., PowerShell Core, Windows Admin Center, or remote management tools) and clarify remote access options from non-Windows systems.
  • Explicitly state platform requirements and limitations early in the documentation, so Linux administrators are aware of the Windows dependency.
  • Where PowerShell is used, note if PowerShell Core (cross-platform) can be used, or provide REST API alternatives if available.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs.md ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 tools, which are only available on Windows. There are no Linux or cross-platform alternatives provided for AD FS setup, nor are command-line or script-based examples (such as PowerShell or CLI) included. The documentation assumes the reader is operating in a Windows Server context and does not mention Linux-based identity providers or AD FS alternatives, nor does it provide parity for Linux administrators.
Recommendations
  • Add instructions or references for managing AD FS via PowerShell, which can be run remotely and may be scriptable from non-Windows environments.
  • Explicitly state that AD FS is a Windows-only technology and suggest alternatives for Linux environments, such as using other OpenID Connect providers (e.g., Keycloak, IdentityServer, or Authentik).
  • Provide examples or links for configuring OpenID Connect identity providers on Linux, and how to integrate them with Azure AD B2C using custom policies.
  • Include a section comparing AD FS with cross-platform OpenID Connect providers, and guidance for users who may not have access to Windows infrastructure.
  • Where possible, offer REST API or configuration file-based instructions that do not require Windows GUI tools.
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-09 00:34
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 exclusively referencing the Azure portal (a web UI most commonly used on Windows), omitting any command-line or automation examples (such as Azure CLI, PowerShell, Bash, or REST API). There are no Linux-specific instructions, nor is there mention of cross-platform tooling. All configuration steps are described using GUI navigation patterns typical of Windows environments, and there is no parity for users who prefer or require Linux or command-line workflows.
Recommendations
  • Add equivalent instructions using Azure CLI and/or REST API for all major steps (app registration, identity provider configuration, policy key creation, etc.), ensuring these examples work on Linux, macOS, and Windows.
  • Include PowerShell and Bash script examples where appropriate, and clarify which commands are cross-platform.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, but provide alternatives for users who prefer command-line or automation.
  • Add a section comparing GUI and CLI approaches, and link to relevant cross-platform documentation.
  • Ensure screenshots or UI references do not assume a Windows environment (e.g., avoid referencing Windows-specific browser features or UI elements).
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-09 00:34
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 primarily 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 offer equivalent examples for Linux or macOS environments. There is no mention of cross-platform alternatives (e.g., Bash, Azure CLI, or direct REST API usage), and the PowerShell approach is presented as the default method for session revocation.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, such as using PowerShell Core (pwsh), Bash, or REST API calls via curl.
  • Clarify that Microsoft Graph PowerShell can be used cross-platform and provide installation and usage steps for non-Windows environments.
  • Include Azure CLI or direct API examples for session revocation to ensure parity for users on all operating systems.
  • Avoid referring to 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or 'PowerShell Core' for cross-platform applicability.
  • Add notes or sections highlighting platform differences and guiding users to appropriate tools for their OS.
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-09 00:34
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, with no equivalent Linux or cross-platform alternatives (e.g., OpenSSL, Bash). Windows tools and workflows (Visual Studio, PowerShell) are mentioned exclusively or before any Linux equivalents, and there are no instructions for performing these steps on Linux or macOS systems.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., OpenSSL commands) alongside PowerShell examples.
  • Include Bash or Python scripts for random string generation, not just PowerShell.
  • Mention cross-platform deployment options (such as VS Code, CLI tools) in addition to Visual Studio.
  • Explicitly note platform requirements or limitations for each step, and offer guidance for non-Windows users.
  • Add a section or callouts 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/partner-f5.md .../blob/main/articles/active-directory-b2c/partner-f5.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, linking to IIS setup instructions, and omitting any mention of Linux-based web servers (such as Apache or Nginx). All application setup and testing guidance is focused on Windows tooling, with no Linux alternatives or parity. The documentation also references Windows-specific patterns (IIS, .NET-style claims) before any cross-platform or Linux options.
Recommendations
  • Add Linux-based web application examples (e.g., Apache, Nginx, Tomcat) for testing the integration.
  • Provide links or instructions for setting up a test application on Linux, similar to the IIS guidance.
  • Include troubleshooting steps and configuration notes relevant to Linux environments (e.g., SELinux, systemd, certificate management).
  • Mention cross-platform considerations for header-based SSO and attribute mapping, including differences in web server configuration.
  • Ensure parity in screenshots and walkthroughs for both Windows and Linux application scenarios.
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-09 00:34
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. No Linux or cross-platform alternatives (such as deploying via CLI, GitHub Actions, or VS Code) are mentioned. The documentation assumes the use of Visual Studio, a Windows tool, and does not provide parity for Linux users in deployment or configuration steps.
Recommendations
  • Include instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
  • Provide Linux-specific or platform-neutral deployment examples alongside Visual Studio instructions.
  • Reference documentation for configuring and deploying from non-Windows environments.
  • Clarify that Visual Studio is one option and highlight alternatives for users on macOS or Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only PowerShell-based instructions for enabling Saviynt to delete users, explicitly stating the need for a 'Windows workstation or server' and referencing the Microsoft Graph PowerShell module. There are no equivalent instructions or examples for Linux or cross-platform environments, nor are alternative tools (such as Azure CLI or REST API) mentioned. This limits accessibility for users on non-Windows platforms.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include REST API examples for the relevant Microsoft Graph operations, allowing users to perform the steps from any environment.
  • Clarify that the Microsoft Graph PowerShell module is available for PowerShell Core, which runs on Linux and macOS, and provide installation instructions for those platforms.
  • Avoid specifying 'Windows workstation or server' unless truly required; instead, refer to 'a machine with access to the required tools' and list cross-platform options.
  • Where possible, present Windows and Linux/macOS instructions side-by-side or in tabs, so users can follow the guide regardless of their operating system.
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:34
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, with no equivalent example for Linux or cross-platform tools. PowerShell is a Windows-centric tool, and its exclusive use may disadvantage administrators working on Linux or macOS systems. The documentation does not mention or suggest alternatives such as Bash, curl, or Python, nor does it provide guidance for non-Windows environments.
Recommendations
  • Add a Bash/curl example for Linux/macOS users to perform the same Microsoft Graph API call.
  • Include a cross-platform Python script example for broader accessibility.
  • Explicitly mention that the API call can be made from any platform and provide links or references to relevant tools.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented together, ensuring parity.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/secure-rest-api.md .../main/articles/active-directory-b2c/secure-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 by exclusively referencing PowerShell for certificate creation and omitting Linux/macOS alternatives. The only explicit tooling example for preparing a self-signed certificate is via a PowerShell module, with no mention of Linux tools such as OpenSSL or macOS Keychain. This may hinder Linux/macOS users from following the steps without additional research.
Recommendations
  • Add equivalent Linux/macOS instructions for creating and exporting certificates, such as using OpenSSL commands.
  • Where PowerShell is referenced, include alternative commands for Bash or other common shells.
  • Explicitly mention cross-platform options for all steps involving local tooling, especially for certificate management.
  • Review other sections for similar tooling bias and ensure parity in examples and instructions.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/view-audit-logs.md .../main/articles/active-directory-b2c/view-audit-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Azure AD B2C audit logs, with no equivalent example for Linux/Unix environments (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) implicitly favor Windows users. There is no mention of cross-platform or Linux-native tooling, nor are alternative command-line examples provided.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, including authentication steps using tools like curl and jq.
  • Provide a Python script example using the requests library to demonstrate cross-platform access to the API.
  • Explicitly mention that the API can be accessed from any OS and provide guidance for Linux/macOS users.
  • Reference Azure CLI or other cross-platform tools where appropriate.
  • Structure the documentation so that examples for Windows and Linux are presented side by side, or clearly indicate which examples are OS-specific.
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-08 00:53
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. It suggests using Microsoft PowerShell to generate GUIDs before mentioning platform-agnostic alternatives, and the first scripting example for obtaining an access token is in PowerShell, with the cURL (Linux-friendly) example following. The documentation references Windows tools and patterns (PowerShell, Azure portal screenshots) without providing explicit Linux command-line alternatives for all steps, and Windows-centric terminology and ordering are present.
Recommendations
  • When suggesting GUID generation, mention platform-agnostic or Linux-native methods first (e.g., 'uuidgen' on Linux/macOS) or provide both options side-by-side.
  • Present scripting examples in a neutral order (e.g., cURL first, then PowerShell), or provide both simultaneously.
  • Explicitly mention Linux/macOS equivalents for all command-line steps, including manifest editing and API testing.
  • Avoid assuming the use of Windows tools; where possible, use cross-platform terminology and examples.
  • Add screenshots or instructions for Linux/macOS environments where Azure portal usage or other steps may differ.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs.md ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools (AD FS Management, Server Manager) and GUI workflows for configuring AD FS, with no mention of Linux equivalents or command-line alternatives. All examples and instructions assume a Windows Server environment, and there are no PowerShell or CLI examples, nor any guidance for Linux-based AD FS alternatives or integration patterns.
Recommendations
  • Provide command-line alternatives (e.g., PowerShell, Windows CLI) for AD FS configuration to support automation and remote management.
  • Explicitly state that AD FS is a Windows Server feature, and mention that there are no direct Linux equivalents, but suggest alternatives (such as using other OpenID Connect providers on Linux) where appropriate.
  • Include a section comparing AD FS with Linux-based identity providers (e.g., Keycloak, Gluu) and provide guidance for integrating those with Azure AD B2C.
  • If possible, link to documentation or community resources for OpenID Connect provider setup on Linux, and clarify the scope of the article.
  • Add a note about cross-platform considerations and recommend best practices for organizations with mixed OS environments.
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-08 00:53
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 primarily 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 or using cross-platform tools. The documentation assumes the use of Visual Studio and does not mention alternatives such as VS Code, CLI, or Linux-based deployment methods.
Recommendations
  • Add instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code.
  • Provide Linux/macOS examples for API deployment, including command-line steps.
  • Reference platform-agnostic documentation for publishing to Azure App Service, not just Visual Studio.
  • Explicitly mention that the API can be deployed from any OS and provide links to relevant documentation for Linux/macOS users.
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-08 00:53
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 or instructions for Linux or cross-platform tools (such as Bash, curl, or Python). The use of Windows-specific tools and the absence of Linux alternatives demonstrate a clear Windows bias.
Recommendations
  • Add equivalent examples using Bash and curl for Linux/macOS users.
  • Provide a cross-platform example using Python (requests library) to call the Microsoft Graph API.
  • Explicitly mention that the PowerShell script is for Windows and direct Linux/macOS users to alternative instructions.
  • Ensure that examples for Linux/macOS are presented alongside Windows examples, not after them.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page primarily describes user management tasks in the Azure portal, which is platform-agnostic. However, for session revocation, it exclusively provides instructions using Microsoft Graph PowerShell, explicitly referencing 'Windows PowerShell' and omitting equivalent Linux/macOS shell examples. There is no mention of using Bash, Azure CLI, or cross-platform alternatives for these tasks, and the PowerShell method is presented first and solely.
Recommendations
  • Provide examples for revoking user sessions using Microsoft Graph API via curl or other HTTP clients, which are platform-independent.
  • Clarify that Microsoft Graph PowerShell can be used on Linux/macOS (via PowerShell Core), and provide installation and usage instructions for those platforms.
  • Include Azure CLI or Bash script examples where possible, especially for bulk operations or automation.
  • Avoid referencing 'Windows PowerShell' exclusively; use 'PowerShell' and specify cross-platform compatibility.
  • Add notes or links to documentation for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
← Previous Page 3 of 16 Next →