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 226-250 of 392 flagged pages
Active Directory B2C Secure APIs used for API connectors in Azure AD B2C .../main/articles/active-directory-b2c/secure-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows moderate Windows bias, particularly in the certificate creation section where PowerShell is referenced as the main method for preparing a self-signed certificate. There is no mention of Linux/macOS alternatives (such as OpenSSL) for certificate generation. The ordering of instructions and examples tends to reference Windows-centric tools and workflows first, with no explicit parity for Linux/macOS users in key steps.
Recommendations
  • Add explicit instructions for generating self-signed certificates using OpenSSL on Linux/macOS, alongside the PowerShell method.
  • Where PowerShell is referenced, provide equivalent bash or shell commands for Linux/macOS users.
  • Clarify that .pfx files can be generated on any platform and provide guidance for cross-platform certificate management.
  • Review all example workflows to ensure Linux/macOS users are not left to infer steps or use unsupported tools.
GitHub Create Pull Request
Active Directory B2C Manage directory size quota in Azure Active Directory B2C ...ive-directory-b2c/tenant-management-directory-quota.md
Medium Priority View Details →
Scanned: 2026-01-14 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 example for monitoring directory quota, with no equivalent instructions or code samples for Linux/macOS users (e.g., Bash, curl, or Python). The use of PowerShell-specific cmdlets and object handling assumes a Windows environment and excludes users on other platforms from easily following the tutorial.
Recommendations
  • Add equivalent examples using Bash with curl or Python scripts for Linux/macOS users.
  • Explicitly mention cross-platform alternatives and clarify that the API can be accessed from any OS.
  • Reorder or parallelize examples so that Windows and Linux/macOS instructions are given equal prominence.
  • Reference platform-agnostic tools (e.g., curl, HTTPie, Python requests) alongside PowerShell.
GitHub Create Pull Request
Active Directory B2C Access and review audit logs .../main/articles/active-directory-b2c/view-audit-logs.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell script for accessing audit logs via the Microsoft Entra reporting API, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, curl, Python). The only automation script shown is PowerShell-centric, which is native to Windows and Azure Cloud Shell, creating friction for users on other platforms. No Linux-first or cross-platform CLI examples are provided.
Recommendations
  • Add equivalent examples using Bash/curl and/or Python to demonstrate how Linux/macOS users can access the API and download audit logs.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide installation instructions or links.
  • Clarify that Azure Cloud Shell supports Bash as well as PowerShell, and provide Bash script examples.
  • Include notes or links to cross-platform tools (e.g., Azure CLI, Microsoft Graph SDKs for Python/Node.js) for audit log retrieval.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Microsoft PowerShell as a tool to test HTTP requests, but does not mention or provide examples for equivalent Linux/macOS tools (such as curl or HTTPie). No command-line examples are shown, and the only tool named is Windows-specific, which may create friction for Linux/macOS users.
Recommendations
  • Mention cross-platform HTTP clients such as curl, HTTPie, or Postman alongside PowerShell.
  • Provide example commands for requesting tokens using curl or HTTPie.
  • Clarify that any HTTP client can be used and provide links to documentation for popular non-Windows tools.
GitHub Create Pull Request
Active Directory B2C Deploy custom policies with Azure Pipelines .../active-directory-b2c/deploy-custom-policies-devops.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies, with no mention of Bash, shell, or cross-platform alternatives. All code examples and pipeline instructions assume PowerShell usage, which is native to Windows and only optionally available on Linux/macOS. There are no Linux/macOS-specific instructions or examples, and Windows-centric tools and patterns are referenced throughout.
Recommendations
  • Provide equivalent Bash or shell script examples for deploying policies using Microsoft Graph API, suitable for Linux/macOS agents.
  • Explicitly mention that PowerShell Core is available cross-platform, and clarify any compatibility requirements.
  • Add instructions for running the deployment script on Linux/macOS pipeline agents, including prerequisites and environment setup.
  • Reorder or parallelize examples so Linux/macOS options are presented alongside Windows/PowerShell options.
  • Highlight any platform-specific considerations (e.g., file paths, authentication) for non-Windows environments.
GitHub Create Pull Request
Active Directory B2C Set up OAuth 2.0 client credentials flow .../active-directory-b2c/client-credentials-grant-flow.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a mild Windows bias. It references PowerShell for GUID generation and provides a PowerShell script for token acquisition before the cURL example. The suggestion to use PowerShell for GUID generation is Windows-centric, and PowerShell is presented first in scripting examples, which may create friction for Linux/macOS users.
Recommendations
  • Explicitly mention platform-agnostic alternatives for GUID generation, such as 'uuidgen' (Linux/macOS) or 'openssl rand -hex 16'.
  • Present cURL (cross-platform) examples before or alongside PowerShell examples.
  • Clarify that all scripting examples are platform-agnostic and provide equivalent commands for Linux/macOS users.
  • Avoid referencing Windows tools exclusively; always provide Linux/macOS alternatives in the same context.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias in its examples and tooling. PowerShell is the only HTTP client shown for testing the Node.js REST API, and Microsoft PowerShell is referenced multiple times as the suggested tool. No Linux/macOS alternatives (such as curl, httpie, or bash) are provided, and the PowerShell example appears before any mention of other platforms. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Linux/macOS examples using curl or httpie for making HTTP requests.
  • Explicitly mention cross-platform alternatives to PowerShell for testing the REST API.
  • Present examples for both Windows and Linux/macOS side-by-side, or alternate which platform is shown first.
  • Clarify that PowerShell is available cross-platform, but also provide native command-line examples for each OS.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only command-line example for configuring password expiry duration uses PowerShell (specifically, the Microsoft Graph PowerShell module), with no mention of Linux/macOS alternatives (such as Microsoft Graph CLI, REST API via curl, or cross-platform scripting). Additionally, PowerShell is referenced before any other tooling, and there are no explicit Linux/macOS instructions or examples provided for command-line operations.
Recommendations
  • Provide equivalent examples using Microsoft Graph CLI, which is cross-platform.
  • Include REST API examples using curl for Linux/macOS users.
  • Clearly state that PowerShell examples are for Windows, and offer alternative instructions for other platforms.
  • Add notes or sections highlighting cross-platform compatibility and tool choices.
  • Reorder examples so that cross-platform or platform-neutral methods (e.g., REST API) are presented before Windows-specific tools.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a notable Windows bias, especially in the how-to sections for generating symmetric and asymmetric keys. PowerShell is exclusively used for key and certificate generation, with no mention of Linux/macOS alternatives (e.g., OpenSSL). Windows tools and patterns are referenced first and exclusively, and Linux/macOS users are left without guidance for these critical steps.
Recommendations
  • Provide equivalent Linux/macOS instructions for key and certificate generation, such as using OpenSSL commands.
  • Include cross-platform code samples or explicitly mention alternatives for non-Windows environments.
  • Reference platform-agnostic tools (e.g., OpenSSL, certtool) alongside PowerShell.
  • Reorder examples or clarify that instructions apply to all platforms, not just Windows.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral for portal-based tasks, but introduces Windows bias in the 'Revoke a consumer user's session' section. It exclusively provides instructions for using Microsoft Graph PowerShell, explicitly referencing 'Windows PowerShell' and omitting Linux/macOS alternatives. No CLI, Bash, or cross-platform examples are given for session revocation, and PowerShell is presented as the primary method.
Recommendations
  • Add instructions for using Microsoft Graph PowerShell on Linux/macOS (e.g., via pwsh or dotnet global tools).
  • Provide equivalent examples using Microsoft Graph API via curl or other cross-platform tools.
  • Clarify that PowerShell Core (pwsh) is available on Linux/macOS and show how to use it.
  • Present API-based examples (e.g., using curl or HTTPie) before or alongside PowerShell to ensure parity.
  • Avoid referencing 'Windows PowerShell' specifically unless required; use 'PowerShell' generically or clarify platform support.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Experian ...main/articles/active-directory-b2c/partner-experian.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 referencing Visual Studio as the publishing tool for the API, without mentioning cross-platform alternatives or providing Linux/macOS instructions. There are no examples or guidance for deploying the API from non-Windows environments, nor are Linux/macOS tools or workflows discussed. The order and focus of instructions implicitly assume a Windows user, creating friction for those on other platforms.
Recommendations
  • Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code (which runs on Linux/macOS).
  • Provide explicit steps for uploading certificates and configuring application settings using Azure CLI or the Azure portal, with screenshots or commands for Linux/macOS.
  • Mention alternatives to Visual Studio for publishing code, such as dotnet CLI or other CI/CD pipelines.
  • Add a note clarifying that the process is platform-agnostic and provide parity in examples for Linux/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
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias, primarily through exclusive use of PowerShell for critical steps such as certificate creation and random string generation. No Linux/macOS equivalents (e.g., OpenSSL, Bash) are provided, and Windows tooling is referenced without alternatives. This creates friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., using OpenSSL commands).
  • Include Bash or Python examples for random string generation.
  • Clearly indicate cross-platform alternatives wherever PowerShell or Windows-specific tools are referenced.
  • Reorder examples so that cross-platform or OS-neutral solutions are presented first, or at least in parallel.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Saviynt with Azure Active Directory B2C .../main/articles/active-directory-b2c/partner-saviynt.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias, particularly in the 'Enable Saviynt to delete users' section, where only PowerShell commands are provided and users are instructed to install the Microsoft Graph PowerShell module on a Windows workstation or server. No equivalent instructions or examples are given for Linux or macOS users, nor are cross-platform alternatives (such as Microsoft Graph CLI, REST API, or Azure Cloud Shell) mentioned. Windows tools and patterns are referenced exclusively and before any Linux alternatives, which are absent.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using Microsoft Graph CLI, REST API (with curl or httpie), or Azure Cloud Shell.
  • Explicitly mention that the Microsoft Graph PowerShell module can be installed on non-Windows platforms (if supported), or clarify platform limitations.
  • Add Linux/macOS command-line examples alongside PowerShell, or restructure examples to use platform-agnostic tools.
  • Include a note about cross-platform compatibility and recommend Azure Cloud Shell for users on any OS.
GitHub Create Pull Request
Active Directory B2C Twilio Verify App with Azure Active Directory B2C ...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by referencing .NET and web.config configuration, which are most commonly associated with Windows/IIS deployments. Hosting guidance is provided only for Azure App Service (which is cross-platform but often Windows-centric in documentation), and there are no examples or instructions for Linux-based hosting, configuration, or deployment. Certificate creation and management are referenced via Windows-centric samples, and there is no mention of Linux equivalents (e.g., using OpenSSL or Linux-based configuration files).
Recommendations
  • Provide explicit instructions or examples for deploying the demo app on Linux-based environments (e.g., Apache, Nginx, Docker).
  • Include Linux/macOS equivalents for certificate creation (e.g., OpenSSL commands) and configuration.
  • Show how to set environment variables or configuration outside of web.config (e.g., appsettings.json, environment variables for .NET Core on Linux).
  • Add hosting guidance for popular Linux platforms or containers, not just Azure App Service.
  • Ensure that code samples and configuration steps are OS-agnostic or provide alternatives for each major platform.
GitHub Create Pull Request
Active Directory B2C Manage directory size quota in Azure Active Directory B2C ...ive-directory-b2c/tenant-management-directory-quota.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell script for monitoring directory quota usage, with no equivalent example for Linux/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 following the steps directly. No mention is made of cross-platform alternatives or how Linux/macOS users can achieve the same result.
Recommendations
  • Add a Bash/curl example for obtaining the access token and calling the Microsoft Graph API.
  • Include a Python example using requests for cross-platform compatibility.
  • Explicitly mention that the PowerShell script is for Windows and provide alternative instructions for Linux/macOS users.
  • Reorder examples so that cross-platform solutions appear first or alongside Windows-specific ones.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias, particularly in the certificate creation section, where only PowerShell is mentioned for preparing self-signed certificates. There are no Linux/macOS equivalents (e.g., OpenSSL) provided, and Windows/PowerShell tooling is referenced exclusively for this task. Other sections are platform-neutral, focusing on Azure portal and XML configuration.
Recommendations
  • Add Linux/macOS instructions for creating self-signed certificates using OpenSSL, including command-line examples.
  • Explicitly mention cross-platform alternatives to PowerShell for certificate management.
  • Where PowerShell is referenced, clarify that equivalent steps can be performed on Linux/macOS and provide links or examples.
  • Ensure all code samples and tool references are available for both Windows and Linux/macOS users.
GitHub Create Pull Request
Active Directory B2C Access and review audit logs .../main/articles/active-directory-b2c/view-audit-logs.md
Medium Priority View Details →
Scanned: 2026-01-13 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 programmatic access to audit logs, with no equivalent example for Linux/macOS users (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) create friction for users on non-Windows platforms. No Linux-native tools or cross-platform scripting alternatives are mentioned.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Entra reporting API and downloading 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.
  • Clarify whether Azure Cloud Shell supports Bash and show how to use it for this task.
GitHub Create Pull Request
Active Directory B2C Authorization code flow - Azure Active Directory B2C ...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. The only tool explicitly recommended for testing HTTP POST requests is Microsoft PowerShell, with no mention of Linux or cross-platform alternatives (e.g., curl, httpie). This reference appears before any mention of Linux tools, and no Linux-specific or cross-platform examples are provided. All other content is platform-neutral, focusing on HTTP requests and protocol details.
Recommendations
  • Include Linux and cross-platform command-line examples, such as curl or httpie, alongside or before PowerShell references.
  • Explicitly mention that any HTTP client can be used, and provide sample commands for both Windows (PowerShell) and Linux/macOS (curl, wget, httpie).
  • Avoid recommending Microsoft-specific tools exclusively; instead, provide a balanced set of options for different operating systems.
  • Add a section or note clarifying cross-platform compatibility and tool choices for developers on Linux, macOS, and Windows.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references the Azure portal web UI and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). There is no mention of Linux-specific tools, nor is there any parity in examples for Linux environments. All instructions are GUI-based and implicitly assume a Windows-centric workflow, as the Azure portal is most commonly used in Windows environments and the documentation does not acknowledge alternative platforms or automation approaches.
Recommendations
  • Add Azure CLI examples for all major steps (e.g., app registration, secret creation, identity provider configuration) to support Linux and cross-platform users.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide links or instructions for command-line alternatives.
  • Include sample scripts for Bash and PowerShell where relevant, and present them side-by-side to ensure parity.
  • Reference Linux-friendly tools and workflows (e.g., VS Code, Azure CLI, REST API) where possible.
  • Add a note clarifying platform independence for all steps, and avoid implying a Windows-only workflow.
GitHub Create Pull Request
Active Directory B2C Register a Microsoft Graph application ...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes management tasks using the Azure portal (web UI) and does not provide any command-line examples. There is no mention of platform-specific tools, but all instructions assume use of the Azure portal, which is equally accessible from Windows and Linux. However, there is a subtle Windows bias in the absence of Linux-oriented automation examples (e.g., Bash, CLI, or scripting), and no mention of PowerShell or Windows tools, but also no parity for Linux shell or CLI workflows.
Recommendations
  • Add examples for registering applications and granting permissions using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include sample scripts for automating these tasks using Bash or other Linux-friendly tools.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
  • Explicitly mention that all steps can be performed from any OS with a web browser, and highlight automation options for both Windows and Linux users.
GitHub Create Pull Request
Active Directory B2C Twilio Verify App with Azure Active Directory B2C ...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing .NET and web.config configuration, which are primarily associated with Windows environments. There are no explicit Linux or cross-platform deployment instructions, nor are there examples for Linux-based hosting or configuration (e.g., appsettings.json, environment variables, or Linux deployment steps). Certificate creation and hosting guidance are linked to Azure App Service, but do not mention Linux alternatives or provide parity for Linux users.
Recommendations
  • Provide equivalent instructions for Linux-based deployments, including configuration using appsettings.json or environment variables.
  • Include examples for hosting the demo application on Linux platforms (e.g., Azure App Service for Linux, Docker, or other Linux-based web servers).
  • Offer guidance for certificate creation and management on Linux (e.g., using OpenSSL).
  • Ensure that all configuration steps (such as updating keys and certificates) have cross-platform examples.
  • Clarify that the .NET app can be run on Linux using .NET Core/6+, and provide relevant commands for Linux environments.
GitHub Create Pull Request
Active Directory B2C Troubleshoot custom policies and user flows in Azure Active Directory B2C ...lob/main/articles/active-directory-b2c/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. Troubleshooting tools and examples mention Windows-centric tools (Fiddler, Edge/Internet Explorer developer tools) and browser extensions for Chrome/Edge/Firefox, but do not mention Linux-native alternatives. When listing SAML debugging tools, Edge/IE developer tools are included alongside browser extensions, and Fiddler is recommended for tracing, both of which are primarily Windows tools. Visual Studio Code is recommended as an editor, which is cross-platform, but all configuration and screenshots are shown in a way that assumes a Windows-like environment (e.g., 'File>Preferences>Settings'). No Linux-specific troubleshooting tools or command-line examples are provided.
Recommendations
  • Include Linux-native alternatives for protocol tracing, such as Wireshark, mitmproxy, or curl for SAML/JWT debugging.
  • When mentioning Fiddler, clarify its availability on Linux (via Fiddler Everywhere) or suggest alternatives.
  • Add explicit instructions or screenshots for Visual Studio Code usage on Linux/macOS, including file navigation and settings.
  • List browser extensions and tools that work across all major platforms, and avoid listing Windows-only developer tools before cross-platform options.
  • Provide command-line examples for troubleshooting (e.g., using curl, jq, or OpenSSL for JWT/SAML inspection) to improve parity for Linux users.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention 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 Windows-centric.
Recommendations
  • Include examples using cross-platform tools such as curl or HTTPie for making HTTP requests.
  • Mention PowerShell as one option, but also list Linux/macOS alternatives to ensure parity.
  • Provide sample commands for both Windows (PowerShell) and Linux/macOS (bash/curl) environments.
  • Clarify that the process can be performed on any platform, not just Windows.
GitHub Create Pull Request
Active Directory B2C Authorization code flow - Azure Active Directory B2C ...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. The only explicit mention of a tool for testing HTTP requests is 'Microsoft PowerShell', which is Windows-centric and referenced before any cross-platform or Linux-native alternatives. No Linux-specific tools (such as curl, wget, httpie) or examples are provided, and PowerShell is suggested as the default option for HTTP client testing. There are no code samples or instructions that are exclusive to Windows, but the tool recommendation implicitly prioritizes Windows users.
Recommendations
  • Mention cross-platform and Linux-native tools for HTTP requests, such as curl, wget, or httpie, alongside PowerShell.
  • Provide example commands for both Windows (PowerShell) and Linux/macOS (curl, wget) when demonstrating how to make HTTP requests.
  • Explicitly state that any HTTP client can be used, and offer parity in instructions for both Windows and Linux users.
  • Avoid suggesting Windows tools as the default or only option; present alternatives in a neutral or platform-agnostic order.
GitHub Create Pull Request
Active Directory B2C Best practices for Azure AD B2C ...b/main/articles/active-directory-b2c/best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-centric tools and patterns before their cross-platform or Linux equivalents. For example, testing recommendations mention 'VS Web Test' and Visual Studio Code (which, while cross-platform, is strongly associated with Windows development). There are no explicit Linux-specific examples, nor are Linux-native tools (such as Bash scripts or Linux-based CI/CD pipelines) mentioned. No PowerShell-specific instructions or Windows-only tools are referenced, but the absence of Linux examples and the order of tool presentation suggest a subtle preference for Windows environments.
Recommendations
  • Include Linux-specific examples and tools (e.g., Bash scripts, Linux-native CI/CD pipelines like Jenkins or GitLab CI) alongside or before Windows ones.
  • When mentioning Visual Studio Code, clarify its cross-platform nature and provide installation instructions for Linux.
  • Expand testing tool recommendations to include Linux-friendly options (e.g., pytest, Robot Framework) and avoid listing only Windows-associated tools.
  • Add explicit examples of automating Azure AD B2C tasks using Linux shell scripts or command-line utilities.
  • Ensure that all instructions and best practices are platform-neutral or provide parallel guidance for both Windows and Linux users.
GitHub Create Pull Request
← Previous Page 10 of 16 Next →