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 51-75 of 101 flagged pages
Active Directory B2C Tutorial to enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP .../blob/main/articles/active-directory-b2c/partner-f5.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing IIS as the example application for testing, linking to IIS setup instructions, and omitting Linux or cross-platform alternatives. No Linux web server (e.g., Apache, Nginx) is mentioned, and there are no examples or guidance for deploying or testing with non-Windows applications. Windows tools and patterns (IIS) are referenced exclusively and before any Linux equivalents, which are not provided.
Recommendations
  • Include examples for deploying and testing with popular Linux web servers such as Apache or Nginx.
  • Provide links to documentation for setting up header-based applications on Linux.
  • Offer parity in troubleshooting and configuration guidance for Linux-based backend applications.
  • Explicitly state that the solution works with both Windows and Linux applications, and describe any platform-specific considerations.
  • Add sample configuration snippets for Linux environments where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is largely platform-neutral until the 'Revoke a consumer user's session' section, which exclusively provides instructions for using Microsoft Graph PowerShell in 'Windows PowerShell', with no mention of Linux/macOS alternatives or CLI/API usage. The explicit reference to 'Windows PowerShell' and lack of cross-platform guidance creates friction for non-Windows users.
Recommendations
  • Provide Microsoft Graph PowerShell instructions for Linux/macOS (e.g., using pwsh or PowerShell Core).
  • Include equivalent Microsoft Graph API (REST) examples for session revocation, which are platform-agnostic.
  • Clarify that Microsoft Graph PowerShell can be used on Linux/macOS with PowerShell Core, and provide installation links.
  • Avoid specifying 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or 'pwsh' for cross-platform compatibility.
  • Consider listing API/CLI methods before or alongside PowerShell instructions to ensure parity.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Jumio ...ob/main/articles/active-directory-b2c/partner-jumio.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the sections on certificate creation and key generation. All code samples for creating certificates and random keys use PowerShell, a Windows-centric tool, with no mention of Linux/macOS alternatives. The instructions for exporting and importing certificates reference Windows certificate stores and workflows, and PowerShell is presented as the default and only method for critical steps. No Linux or cross-platform command-line alternatives (such as OpenSSL or bash) are provided.
Recommendations
  • Add equivalent Linux/macOS instructions for creating and exporting self-signed certificates (e.g., using OpenSSL).
  • Provide bash or Python examples for generating random signing/encryption keys.
  • Clarify how to import certificates into Azure App Service from non-Windows environments.
  • Present cross-platform options first, or at least in parallel, rather than only PowerShell.
  • Explicitly state that PowerShell examples are for Windows and link to Linux/macOS alternatives.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Enable Saviynt to delete users' section. It exclusively instructs users to install and use the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux/macOS alternatives or cross-platform CLI options. The only example commands provided are PowerShell-based, and there is no guidance for Linux users on how to perform equivalent tasks.
Recommendations
  • Provide equivalent instructions using Microsoft Graph CLI (mgc) or REST API, which are cross-platform and work on Linux/macOS.
  • Explicitly mention that Microsoft Graph PowerShell is available on Linux/macOS via PowerShell Core, and provide installation steps for those platforms.
  • Include example commands for Linux/macOS environments, such as using Bash with curl or the Microsoft Graph CLI.
  • Avoid language that implies Windows is required (e.g., 'on a Windows workstation or server') unless strictly necessary, and clarify platform support.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias in the certificate creation section, where PowerShell is presented as the only explicit command-line method for preparing a self-signed certificate. No Linux or macOS alternatives (such as OpenSSL) are mentioned, and the PowerShell module is referenced without parity for other platforms. The rest of the documentation is platform-neutral, focusing on Azure portal UI and XML configuration, but the lack of Linux/macOS certificate creation guidance may create friction for non-Windows users.
Recommendations
  • Add explicit instructions and examples for creating self-signed certificates on Linux and macOS using OpenSSL.
  • Reference cross-platform tools (e.g., OpenSSL) alongside PowerShell, and clarify which steps are platform-specific.
  • Where PowerShell is mentioned, provide equivalent bash/terminal commands for Linux/macOS users.
  • Include links to official documentation for certificate creation on all major platforms.
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-12 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 use of PowerShell and references to Azure Cloud Shell (which supports PowerShell) create friction for users on non-Windows platforms. No Linux/macOS command-line examples or tool recommendations are present.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API and downloading audit logs.
  • Provide a Python example using the 'requests' library to demonstrate cross-platform API access.
  • Explicitly mention that the API can be accessed from any platform and link to relevant cross-platform SDKs or CLI tools.
  • Clarify which parts of the workflow are platform-agnostic and which are Windows-specific.
  • Consider listing Linux/macOS examples before or alongside PowerShell to avoid implicit prioritization.
GitHub Create Pull Request
Active Directory B2C Add AD FS as a SAML identity provider by using custom policies ...es/active-directory-b2c/identity-provider-adfs-saml.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with exclusive references to Windows tools (AD FS Management snap-in, Server Manager, Event Viewer) and PowerShell commands. There are no Linux/macOS equivalents or instructions, and troubleshooting steps rely on Windows-specific applications. This creates friction for users administering AD FS from non-Windows platforms.
Recommendations
  • Provide guidance on managing AD FS via remote PowerShell from Linux/macOS using cross-platform tools (e.g., PowerShell Core, WinRM, or REST APIs).
  • Include instructions for accessing AD FS logs and configuration via command line or remote management tools that work on Linux/macOS.
  • Clarify that AD FS is a Windows-only service, but highlight any possible cross-platform management options or alternatives.
  • Where possible, offer parity by describing how to perform certificate creation, XML editing, and other steps on Linux/macOS (e.g., using OpenSSL, text editors).
  • Add notes or links for Linux/macOS users about prerequisites and limitations.
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-11 06:20
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 Azure portal tasks, but the section on revoking a user's session is notably Windows-biased: it only provides instructions for using Microsoft Graph PowerShell in 'Windows PowerShell', with no mention of Linux/macOS alternatives or CLI/API usage. The PowerShell module is cross-platform, but the documentation implies Windows-only usage and omits Linux/macOS guidance.
Recommendations
  • Clarify that Microsoft Graph PowerShell is cross-platform and can be used on Linux/macOS (e.g., via pwsh or PowerShell Core).
  • Provide explicit instructions or examples for running the PowerShell commands on Linux/macOS.
  • Offer alternative examples using Microsoft Graph API via curl or other cross-platform tools.
  • Avoid language like 'In your Windows PowerShell'—instead, use 'In your PowerShell terminal' and note platform compatibility.
  • Add a note or section for Linux/macOS users to ensure parity and reduce friction.
GitHub Create Pull Request
Active Directory B2C Tutorial to enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP .../blob/main/articles/active-directory-b2c/partner-f5.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing IIS as the example application for testing, and linking to IIS setup instructions. There are no equivalent examples or instructions for Linux-based web servers (such as Apache or Nginx), nor are Linux-specific tools or patterns mentioned. This may create friction for Linux users who wish to follow the tutorial with a non-Windows backend.
Recommendations
  • Provide Linux-based web application examples (e.g., Apache, Nginx) alongside IIS.
  • Include links or instructions for setting up a test web application on Linux.
  • Mention Linux-compatible SSL certificate management and troubleshooting steps.
  • Ensure that any references to application setup, testing, or troubleshooting are platform-neutral or offer both Windows and Linux alternatives.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides critical steps for enabling Saviynt to delete users in Azure AD B2C using the Microsoft Graph PowerShell module, explicitly stating installation on a Windows workstation or server. All command-line examples are in PowerShell, with no mention of Linux/macOS alternatives (such as Microsoft Graph CLI, REST API, or cross-platform scripting). This creates friction for non-Windows users and may prevent them from completing the integration without additional research.
Recommendations
  • Add instructions and examples for using Microsoft Graph CLI and/or REST API, which are cross-platform.
  • Clarify that PowerShell Core is available on Linux/macOS and provide installation steps for those platforms.
  • Provide equivalent bash or shell script examples for Linux/macOS users.
  • Avoid language that implies Windows is required unless absolutely necessary; specify cross-platform options where possible.
  • List Linux/macOS instructions alongside Windows, or in a dedicated section, to ensure parity.
GitHub Create Pull Request
Active Directory B2C Tutorial to configure Azure Active Directory B2C with Jumio ...ob/main/articles/active-directory-b2c/partner-jumio.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias, especially in sections related to certificate creation and key generation. All code examples for creating self-signed certificates and random signing/encryption keys use PowerShell, a Windows-centric tool. There are no equivalent Linux/macOS commands (e.g., OpenSSL, bash) provided, and Windows tools are mentioned exclusively and first. This creates friction for Linux/macOS users who cannot directly follow the instructions without seeking alternative methods.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., OpenSSL commands).
  • Include bash or Python examples for random string/key generation.
  • Explicitly mention cross-platform alternatives and link to relevant external documentation.
  • Order examples so that Windows and Linux/macOS instructions are presented side-by-side or in parallel sections.
  • Clarify which steps are platform-specific and offer guidance for non-Windows environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing .NET applications and configuration via web.config (an IIS/Windows-centric pattern), and by providing hosting guidance only for Azure App Service (which is platform-neutral but often used from Windows). There are no examples or instructions for Linux/macOS users, such as how to run the demo app on Linux, how to configure certificates outside of Windows tooling, or how to deploy using Linux-native web servers (e.g., Apache, Nginx, Kestrel).
Recommendations
  • Provide explicit instructions for running the demo app on Linux/macOS, including prerequisites (e.g., .NET Core SDK installation on Linux).
  • Include examples for configuring certificates using Linux tools (e.g., OpenSSL) and updating appsettings.json for .NET Core apps instead of only web.config.
  • Add deployment guidance for Linux-based hosting environments (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
  • Clarify cross-platform compatibility of the demo app and highlight any OS-specific steps.
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-11 06:20
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 example is Windows-centric, and there is no mention of cross-platform alternatives or parity in scripting instructions.
Recommendations
  • Add Bash/curl and Python examples for querying the Microsoft Entra reporting API, including authentication and data retrieval.
  • Explicitly mention that the API can be accessed from any platform and provide guidance for Linux/macOS users.
  • Reference cross-platform tools (e.g., Azure CLI, REST API via curl) alongside PowerShell.
  • Reorder or supplement scripting sections to present cross-platform solutions before or alongside Windows/PowerShell examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily in the certificate creation section, where only PowerShell is mentioned for preparing a self-signed certificate. No Linux or cross-platform alternatives (such as OpenSSL) are provided or referenced. The rest of the documentation is platform-neutral, focusing on Azure portal and XML configuration, but the lack of Linux/macOS guidance for certificate generation creates friction for non-Windows users.
Recommendations
  • Add Linux/macOS instructions for generating self-signed certificates, e.g., using OpenSSL.
  • Explicitly mention cross-platform alternatives alongside PowerShell, and link to relevant guides.
  • Where PowerShell is referenced, clarify that it is Windows-specific and provide parity for other platforms.
  • Consider a table or section comparing certificate generation methods across Windows, Linux, and macOS.
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-11 06:20
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/macOS users (e.g., Bash, curl, or Python). This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and the instructions assume a Windows environment.
Recommendations
  • Add equivalent examples using Bash and curl, or Python, to demonstrate how to obtain a token and call the Microsoft Graph API from Linux/macOS.
  • Explicitly mention cross-platform alternatives and tools.
  • Reorder examples or provide tabs for Windows (PowerShell) and Linux/macOS (Bash/curl/Python) to ensure parity.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, without referencing Linux/macOS alternatives such as curl or HTTPie. This suggests a Windows bias, as PowerShell is a Windows-centric tool and is listed as the only example. Additionally, the mention of PowerShell comes before any mention of cross-platform or Linux-native tools.
Recommendations
  • Include examples using cross-platform tools such as curl and HTTPie for making HTTP requests.
  • Explicitly mention that any HTTP client can be used, and provide sample commands for both Windows (PowerShell) and Linux/macOS (curl).
  • Avoid listing Windows tools exclusively or first; present cross-platform options equally.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates bias toward Windows by recommending PowerShell for GUID generation and providing a PowerShell script as the first example for obtaining an access token. The mention of PowerShell as the default tool for GUID generation, with only a secondary reference to online generators, and the ordering of examples (PowerShell before cURL) both suggest a Windows-centric approach. Linux/macOS users may need to seek alternative commands or tools for some steps.
Recommendations
  • Explicitly provide Linux/macOS equivalents for GUID generation, such as 'uuidgen' or 'openssl rand -hex 16'.
  • Present cURL (cross-platform) examples before or alongside PowerShell scripts to avoid Windows-first ordering.
  • Clarify that all steps can be completed on Linux/macOS and mention platform-agnostic tools where possible.
  • Add notes or links to platform-specific instructions for common tasks (e.g., manifest editing, secret management).
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-11 06:20
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 recommendations. PowerShell is the only HTTP client shown for testing the Node.js REST API, and Microsoft PowerShell is mentioned as the primary tool for making POST requests both locally and after deployment. No Linux/macOS equivalents (such as curl or HTTPie) are provided, nor are they referenced as alternatives. This creates friction for non-Windows users, who must infer or adapt the instructions themselves.
Recommendations
  • Add Linux/macOS-friendly HTTP client examples, such as curl and HTTPie, alongside PowerShell.
  • Explicitly mention that any terminal (e.g., Bash, zsh) can be used for Node.js development and testing.
  • Provide equivalent command-line snippets for curl and HTTPie when demonstrating POST requests.
  • Clarify that Visual Studio Code is cross-platform, and suggest alternatives (e.g., Vim, nano) for code editing.
  • Avoid referencing Microsoft PowerShell as the sole HTTP client; present it as one of several options.
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-11 06:20
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 in Azure Pipelines. All code examples, instructions, and pipeline task guidance are centered on PowerShell, which is natively available on Windows and only optionally available on Linux/macOS. There is no mention of Bash, shell scripts, or cross-platform alternatives, nor any guidance for Linux/macOS users. This creates friction for non-Windows users and may require them to install PowerShell Core or adapt the process themselves.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Explicitly mention that PowerShell Core is required for Linux/macOS and provide installation instructions.
  • Add notes or sections describing how to adapt the deployment process for non-Windows agents in Azure Pipelines.
  • Consider offering a cross-platform script (e.g., using Python or Node.js) for policy deployment.
  • List both Windows and Linux agent options when describing pipeline setup.
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-11 06:20
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. PowerShell is the only CLI tool mentioned for tenant-wide password expiry configuration, with no Linux/macOS alternatives (such as Bash, curl, or Microsoft Graph CLI). The use of PowerShell is presented without cross-platform context, and Windows-centric tools are referenced before any Linux equivalents (which are missing). All portal instructions are platform-neutral, but CLI automation is Windows-focused.
Recommendations
  • Provide Microsoft Graph CLI or REST API (curl) examples alongside PowerShell for password expiry configuration, ensuring Linux/macOS users have parity.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if the cmdlet is Windows-only.
  • Add notes or links to installing and using Microsoft Graph CLI on Linux/macOS.
  • Consider reordering examples so that platform-neutral or cross-platform options appear 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-11 06:20
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, especially in the 'How-to guide' sections for generating symmetric and asymmetric keys. PowerShell is exclusively used for key and certificate generation, with no Linux/macOS alternatives (e.g., OpenSSL) provided. Windows tools and patterns are mentioned first and, in some cases, exclusively, which may create friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide equivalent Linux/macOS commands for key and certificate generation (e.g., OpenSSL for symmetric keys and self-signed certificates).
  • Include cross-platform code samples or explicitly mention alternatives for non-Windows environments.
  • Reorder examples or clarify that instructions apply to all platforms, not just Windows.
  • Reference platform-agnostic tools and libraries where possible.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md ...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by only referencing .NET applications and configuration via web.config, which are primarily Windows-centric technologies. There are no examples or guidance for deploying the sample app on Linux, nor are alternative Linux hosting or configuration instructions provided. The certificate creation and hosting instructions link to Azure App Service guidance, which is platform-neutral, but the lack of explicit Linux instructions or parity in examples is notable.
Recommendations
  • Provide equivalent instructions for deploying the demo app on Linux environments (e.g., using Kestrel, Nginx, or Apache).
  • Include examples for configuring the application using environment variables or appsettings.json, which are more common in cross-platform .NET Core apps.
  • Add guidance for certificate creation and management on Linux (e.g., using OpenSSL).
  • Clarify that the sample app can be hosted on both Windows and Linux platforms, and provide links or steps for both.
  • Where possible, use .NET Core/.NET 6+ terminology and examples, which are cross-platform, rather than .NET Framework/web.config (Windows-centric).
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
Medium Priority View Details →
Scanned: 2026-01-08 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 tools or examples are provided, and the only tool explicitly referenced is Windows-centric. This may lead Linux users to feel unsupported or unclear about equivalent workflows.
Recommendations
  • Mention cross-platform HTTP clients such as curl and HTTPie alongside PowerShell.
  • Provide example commands for Linux/macOS environments (e.g., curl command for the POST request).
  • Clarify that the process can be performed on any OS and list multiple tool options.
  • Avoid referencing only Windows tools unless there is a specific reason; strive for parity in tool recommendations.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md ...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by primarily referencing Visual Studio and Visual Studio Code as development environments, with no explicit mention of Linux or macOS alternatives for building and running the sample. There are no terminal or command-line examples for Linux (e.g., using dotnet CLI), and the instructions assume a GUI-based workflow typical of Windows users. While Visual Studio Code is cross-platform, the lack of explicit Linux/macOS instructions or screenshots, and the absence of Linux-specific troubleshooting or environment setup, means Linux parity is not achieved.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using the dotnet CLI to build and run the sample projects (e.g., 'dotnet build', 'dotnet run').
  • Include a section or tab for Linux/macOS setup, covering prerequisites like installing .NET SDK on Linux, and using editors like VS Code or JetBrains Rider.
  • Provide Linux/macOS-specific screenshots or notes where file paths, environment variables, or UI elements differ.
  • Mention and link to official .NET installation guides for Linux and macOS.
  • Clarify that Visual Studio Code is cross-platform and supported on Linux/macOS, and ensure all steps are validated on those platforms.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app.md ...rectory-b2c/configure-authentication-sample-web-app.md
Medium Priority View Details →
Scanned: 2026-01-06 18:40
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio and Visual Studio Code as development environments, with no mention of Linux-specific tools or workflows. The instructions and prerequisites focus on Windows-centric IDEs and do not provide guidance for Linux users, such as using command-line .NET tools or alternative editors. There are no explicit Linux examples or deployment instructions, and the sample application is ASP.NET-based, which is traditionally Windows-focused, though .NET Core is cross-platform.
Recommendations
  • Add explicit instructions for Linux users, including installation of .NET SDK on Linux distributions and use of command-line tools (dotnet CLI) for building and running the sample.
  • Include examples of opening and running the project using Linux-friendly editors (e.g., Vim, Emacs, JetBrains Rider) or just the terminal.
  • Provide troubleshooting tips for common Linux issues, such as HTTPS certificate setup for localhost development.
  • Clarify that the sample can be run on Linux and macOS, and provide any necessary configuration differences.
  • Mention deployment options for Linux servers (e.g., using Nginx/Apache as reverse proxies for ASP.NET Core apps).
GitHub Create Pull Request
← Previous Page 3 of 5 Next →