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 26-50 of 101 flagged pages
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on .NET and web.config configuration (Windows-centric technologies), referencing Azure App Service (commonly used with Windows), and omitting any Linux-specific instructions or examples. There are no Linux hosting or configuration examples, and no mention of Linux tools or deployment patterns.
Recommendations
- Add instructions for configuring and running the sample app on Linux (e.g., using .NET Core on Ubuntu, configuring appsettings.json instead of web.config).
- Provide examples for deploying the application to Linux-based hosting environments (such as Azure App Service for Linux, Docker containers, or on-premises Linux servers).
- Include guidance for certificate creation and management using Linux tools (e.g., OpenSSL commands) alongside or instead of Windows-centric instructions.
- Mention cross-platform .NET capabilities and clarify that the sample app can be run on both Windows and Linux.
- If using Azure App Service, specify both Windows and Linux hosting options and provide relevant steps for each.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-native-app-desktop.md
.../active-directory-b2c/quickstart-native-app-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows development, specifically using a WPF desktop application and Visual Studio. All examples, screenshots, and instructions are tailored for Windows, with no mention of Linux or cross-platform alternatives. There are no instructions for running the sample on Linux, nor are there references to Linux-compatible development tools or frameworks.
Recommendations
- Provide equivalent instructions and examples for Linux desktop development, such as using .NET MAUI or Avalonia for cross-platform apps.
- Include steps for running the sample application on Linux, including required dependencies and alternative IDEs (e.g., VS Code, JetBrains Rider).
- Add screenshots and walkthroughs for Linux environments.
- Mention cross-platform .NET development patterns and clarify which parts are Windows-specific.
- Offer guidance for building and debugging the sample app on Linux, including command-line instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-web-app-dotnet.md
...cles/active-directory-b2c/quickstart-web-app-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio (a Windows-centric IDE), uses Windows-specific solution files (.sln), and provides instructions tailored to Visual Studio's GUI and workflow. There are no examples or instructions for running or debugging the sample application on Linux or macOS, nor are there mentions of cross-platform tools like Visual Studio Code, JetBrains Rider, or command-line approaches (e.g., dotnet CLI).
Recommendations
- Add instructions for running and debugging the sample application using the dotnet CLI, which is cross-platform and works on Linux and macOS.
- Include guidance for using Visual Studio Code or JetBrains Rider, both of which are available on Linux and macOS, for opening and running the solution.
- Mention prerequisites for Linux/macOS users, such as installing the .NET SDK and any required dependencies.
- Provide alternative steps for tasks currently described with Visual Studio GUI actions (e.g., configuring multiple startup projects) using launch.json or command-line equivalents.
- Explicitly state that the sample can be run on Linux/macOS and provide troubleshooting tips for those platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-web-app-dotnet.md
...cles/active-directory-b2c/quickstart-web-app-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of Visual Studio (a Windows-centric IDE) and provides instructions exclusively for running the sample application in Visual Studio, with no mention of Linux-compatible tools (such as VS Code, JetBrains Rider, or command-line .NET CLI usage). There are no Linux-specific instructions or alternatives for running or debugging the application, and Windows tools and patterns are mentioned exclusively.
Recommendations
- Add instructions for running the sample application using cross-platform tools such as Visual Studio Code or JetBrains Rider.
- Provide examples for building and running the application using the .NET CLI (e.g., 'dotnet build', 'dotnet run'), which work on Linux, macOS, and Windows.
- Explicitly mention that Visual Studio is only available on Windows, and suggest alternatives for Linux users.
- Include screenshots or terminal commands relevant to Linux environments.
- Ensure that all steps (such as configuring multiple startup projects) have Linux-compatible equivalents or workarounds documented.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a PowerShell script for monitoring directory quota, which is specific to Windows environments. There are no equivalent examples for Linux or cross-platform tools (e.g., Bash, curl, Python). The instructions and tooling are Windows-centric, potentially excluding users on Linux or macOS from easily following the steps.
Recommendations
- Provide equivalent examples using Bash and curl, which are available on Linux and macOS.
- Include a cross-platform example using Python, which works on both Windows and Linux.
- Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation guidance if PowerShell is the preferred tool.
- Reorder or parallelize instructions so that Windows and Linux/macOS users are equally supported, rather than presenting only Windows-first solutions.
- Add a note clarifying that the steps can be performed on any OS, and link to relevant cross-platform tools.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script for programmatically accessing audit logs, with no equivalent examples for Linux users (e.g., Bash/cURL or Python). The script assumes use of PowerShell, which is primarily a Windows tool, and there is no mention of cross-platform alternatives or guidance for Linux/macOS users. This creates a Windows-centric bias in the programmatic access section.
Recommendations
- Add a Bash/cURL example for calling the Microsoft Graph API to retrieve audit logs, suitable for Linux/macOS users.
- Provide a Python script example, as Python is widely available cross-platform and commonly used for automation.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide instructions for installing it if retaining PowerShell examples.
- Ensure that all code examples are presented in both Windows (PowerShell) and Linux (Bash/cURL or Python) variants where possible.
- Review the documentation for other implicit Windows tool assumptions and clarify cross-platform compatibility.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/multiple-token-endpoints.md
...icles/active-directory-b2c/multiple-token-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows development environments. All examples and instructions reference Visual Studio, .sln solution files, and editing .cs and .config files typical of Windows/.NET development. There are no mentions of Linux-compatible tools, editors, or workflows, nor are there any CLI or cross-platform instructions. The only development environment referenced is Visual Studio, and all file paths and configuration steps assume a Windows context.
Recommendations
- Add instructions for opening and editing the project using cross-platform editors like VS Code or JetBrains Rider, and mention how to build/run the project using the .NET CLI (dotnet build/run) on Linux.
- Include Linux/macOS-specific instructions for file paths and configuration changes, or clarify that the steps are cross-platform if applicable.
- Mention that the sample code can be used on Linux and macOS with the .NET SDK, and provide any prerequisites or caveats for non-Windows environments.
- Provide examples of using command-line tools (e.g., dotnet CLI) instead of only referencing Visual Studio.
- Explicitly state the cross-platform compatibility of the OWIN/Katana middleware and the sample application.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page primarily describes user management tasks in the Azure portal, which is cross-platform. However, for advanced tasks such as revoking a user's session, only Microsoft Graph PowerShell (and specifically 'Windows PowerShell') is mentioned, with no equivalent examples for Linux or macOS users. The instructions and terminology (e.g., 'In your Windows PowerShell') suggest a Windows-centric approach, and there are no CLI or bash examples provided.
Recommendations
- Provide equivalent examples using cross-platform tools, such as Azure CLI or Microsoft Graph CLI, especially for tasks like session revocation.
- Clarify that Microsoft Graph PowerShell is available on all platforms (Windows, macOS, Linux) and avoid language that implies it is Windows-only.
- Include bash or shell command examples where appropriate, or explicitly state that the PowerShell module can be used on Linux/macOS.
- When referencing PowerShell, use neutral language such as 'in your terminal' or 'in PowerShell', rather than 'in your Windows PowerShell', to avoid implying Windows exclusivity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-experian.md
...main/articles/active-directory-b2c/partner-experian.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by instructing users to publish the integration code using Visual Studio (a Windows-centric tool) without mentioning cross-platform alternatives. There are no examples or instructions for deploying the API from Linux or macOS environments, nor are there references to CLI-based or platform-agnostic deployment methods. The documentation assumes the use of Azure App Service and Visual Studio, which are most commonly used on Windows, and does not provide parity for Linux users.
Recommendations
- Add instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions.
- Provide examples for publishing the code from Linux and macOS environments, for example using 'dotnet publish' and 'az webapp deploy'.
- Mention Visual Studio Code as an alternative editor, which is cross-platform, and provide relevant steps.
- Ensure that all deployment and configuration steps are documented in a platform-agnostic way, or provide parallel instructions for Windows and Linux/macOS users.
- Explicitly state that Visual Studio is optional and link to documentation for alternative deployment methods.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API, without mentioning or providing alternatives for Linux or cross-platform development environments. There are no examples or instructions for deploying the API from Linux or using cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
- Include explicit examples for Linux and macOS users, such as command-line deployment steps or Docker-based deployment.
- Avoid referencing only Visual Studio or Windows-specific tools; if Visual Studio is mentioned, also mention VS Code or other cross-platform IDEs.
- Where possible, use neutral language and tool recommendations that do not assume a Windows environment.
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for key steps such as certificate creation and random string generation, without offering equivalent Linux or cross-platform alternatives. The use of Windows-centric tooling (PowerShell, Visual Studio) is assumed, and there are no references to Linux command-line tools or methods for these tasks.
Recommendations
- Provide equivalent Linux and macOS instructions for creating self-signed certificates (e.g., using OpenSSL).
- Include examples using bash or other cross-platform scripting languages for generating random strings.
- Mention alternative deployment methods for the API (e.g., using Azure CLI, GitHub Actions, or VS Code) that do not require Visual Studio.
- Clearly indicate which steps are platform-specific and offer parity for non-Windows environments.
- Add notes or links to official Azure documentation for Linux/macOS users where relevant.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting any mention of Linux-based web servers (such as Apache or Nginx). All application setup and testing guidance is focused on Windows/IIS, with no Linux equivalents or parity in examples. This may lead Linux administrators to feel excluded or unsupported when following the tutorial.
Recommendations
- Include Linux-based web application examples (e.g., Apache, Nginx) alongside IIS for testing the integration.
- Provide links or instructions for setting up a test web application on Linux, similar to the IIS setup guidance.
- Mention Linux-compatible SSL certificate management and web server configuration steps.
- Clarify that the solution is platform-agnostic and provide troubleshooting tips for both Windows and Linux environments.
- Ensure any references to application pools, server configuration, or troubleshooting are not exclusively tied to Windows/IIS terminology.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-onfido.md
...b/main/articles/active-directory-b2c/partner-onfido.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation shows a bias towards Windows by recommending Visual Studio for API deployment and referencing Azure Storage Explorer (a tool with limited Linux support) for file management. There are no explicit Linux or cross-platform alternatives provided for these steps, and no CLI or code-based examples are given for Linux users. The order and choice of tools suggest a Windows-first approach.
Recommendations
- Include cross-platform deployment instructions for the API, such as using the .NET CLI (`dotnet publish` and `az webapp deploy`) or GitHub Actions, in addition to Visual Studio.
- Provide examples for uploading files to Azure Blob Storage using Azure CLI (`az storage blob upload`) or AzCopy, both of which are cross-platform.
- Mention and link to cross-platform tools (e.g., Visual Studio Code, AzCopy, Azure CLI) alongside or before Windows-specific tools.
- Explicitly state that all steps can be performed on Linux, macOS, or Windows, and provide command-line alternatives where possible.
- Avoid assuming the use of Windows-only tools in instructions; always offer Linux/macOS equivalents.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides instructions for enabling Saviynt to delete users in Azure AD B2C exclusively using the Microsoft Graph PowerShell module, specifying installation on a Windows workstation or server. No Linux or cross-platform alternatives (such as Azure CLI, Bash, or PowerShell Core on Linux/macOS) are mentioned. The PowerShell example is given without any equivalent for non-Windows environments, and Windows is referenced first and exclusively in the tooling section.
Recommendations
- Add instructions for installing and using Microsoft Graph PowerShell on Linux and macOS, including PowerShell Core.
- Provide equivalent examples using Azure CLI or REST API calls, which are cross-platform.
- Explicitly state platform compatibility for all tools and commands.
- Include notes or links for Linux/macOS users on how to perform the same operations.
- Avoid language that implies Windows is required unless absolutely necessary, and clarify platform requirements.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-native-app-desktop.md
.../active-directory-b2c/quickstart-native-app-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio. All instructions and screenshots are for Windows tools and workflows, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for running or developing the sample application on Linux or macOS, nor are there suggestions for equivalent tools or frameworks.
Recommendations
- Provide instructions and examples for running a cross-platform desktop application (e.g., using .NET MAUI, Avalonia, or Electron) that can be developed and executed on Linux.
- Include guidance for setting up the development environment on Linux (e.g., using Visual Studio Code, JetBrains Rider, or the dotnet CLI).
- Offer alternative steps for restoring NuGet packages and running the application using the command line (dotnet restore, dotnet run) instead of Visual Studio.
- Add Linux/macOS-specific screenshots and troubleshooting tips.
- Clearly indicate which steps are Windows-only and provide parity for other platforms where possible.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-generic-saml-options.md
...irectory-b2c/identity-provider-generic-saml-options.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Debug SAML protocol' section, where Windows-specific tools (Microsoft Edge and Internet Explorer developer tools) are mentioned alongside browser extensions, and the Windows tools are listed last but with a dedicated link. No Linux-specific SAML debugging tools or command-line utilities are referenced, and there are no examples using Linux-native tools or patterns throughout the page. The documentation does not provide parity for Linux users in troubleshooting or debugging SAML integrations.
Recommendations
- Add references to Linux-compatible SAML debugging tools, such as command-line utilities (e.g., curl, openssl, xmlsec1) for inspecting SAML requests/responses.
- Include guidance or examples for using Linux browser developer tools (e.g., Chrome/Firefox DevTools on Linux) for SAML tracing.
- Mention cross-platform browser extensions explicitly as available on Linux, macOS, and Windows.
- Provide troubleshooting steps using Linux shell commands to parse or inspect SAML XML files.
- Avoid listing Windows tools exclusively or giving them prominence; ensure Linux and macOS users are equally supported in all example and tooling recommendations.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention Linux/macOS alternatives (such as curl or httpie), nor does it provide example commands for those platforms. This creates a subtle bias towards Windows users by implying PowerShell is the default or preferred tool, and omits guidance for Linux/macOS users.
Recommendations
- Mention cross-platform HTTP clients such as curl and httpie alongside PowerShell.
- Provide example commands for requesting tokens using curl or httpie.
- Clarify that any HTTP client can be used, and link to relevant documentation for Linux/macOS tools.
Active Directory B2C
Twilio Verify App with Azure Active Directory B2C
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on .NET (typically associated with Windows environments) and referencing configuration via web.config files. There are no examples or guidance for Linux/macOS users, such as using cross-platform .NET Core, environment variables, or deployment steps for Linux-based hosting. Instructions for uploading certificates and hosting the demo app are tailored to Azure App Service (commonly used with Windows), with no mention of Linux alternatives.
Recommendations
- Provide instructions for deploying the demo app on Linux-based environments (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
- Include configuration examples using environment variables or appsettings.json, which are more common in cross-platform .NET Core applications.
- Clarify whether the sample app supports .NET Core/.NET 6+ and provide steps for running it on Linux/macOS.
- Add certificate creation and management instructions for Linux (e.g., using OpenSSL).
- Ensure all code/configuration samples are platform-agnostic or provide parallel examples for Linux/macOS.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention or provide examples for Linux/macOS equivalents such as curl or HTTPie. No explicit Windows/Powershell code samples are given, but the only tool referenced is Windows-centric.
Recommendations
- Mention cross-platform HTTP clients such as curl and HTTPie alongside PowerShell.
- Provide example commands for Linux/macOS users (e.g., curl command for the POST request).
- Clarify that any HTTP client can be used and link to documentation for popular cross-platform tools.
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 →
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, with no equivalent Linux/macOS command-line examples (such as curl or httpie). Microsoft PowerShell is mentioned as the recommended tool for making POST requests, and Windows-centric patterns are presented first and exclusively. This creates friction for Linux/macOS users, who must translate the instructions to their own environment.
Recommendations
- Provide Linux/macOS equivalents for all command-line examples, such as curl or httpie commands for making HTTP requests.
- Mention cross-platform tools (curl, httpie, Postman) alongside PowerShell, and clarify that PowerShell is available on Linux/macOS but may not be installed by default.
- When showing code snippets for testing, present both Windows (PowerShell) and Linux/macOS (bash/curl) examples side by side.
- Avoid language that implies PowerShell is the only or preferred option for HTTP requests.
- Add a note or section on testing the REST API from different operating systems.
Active Directory B2C
Twilio Verify App with Azure Active Directory B2C
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias towards Windows environments by exclusively referencing .NET and web.config (Windows-centric), hosting guidance focused on Azure App Service (commonly used with Windows), and certificate creation instructions that link to Windows-oriented samples. No Linux/macOS equivalents or examples (e.g., for certificate creation, configuration, or hosting) are provided, and Windows patterns/tools are mentioned first and exclusively.
Recommendations
- Add explicit instructions and examples for Linux/macOS environments, such as using environment variables or appsettings.json for configuration instead of web.config.
- Provide guidance for hosting the demo app on Linux-based platforms (e.g., Azure App Service for Linux, Docker, or other Linux cloud hosts).
- Include cross-platform certificate creation instructions (e.g., using OpenSSL on Linux/macOS) alongside or before Windows-specific methods.
- Ensure code/configuration samples are platform-agnostic or provide both Windows and Linux/macOS variants.
Active Directory B2C
Set up OAuth 2.0 client credentials flow
.../active-directory-b2c/client-credentials-grant-flow.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references PowerShell for GUID generation and provides a PowerShell script as the first example for obtaining an access token, with cURL (cross-platform) shown second. The suggestion to use PowerShell for GUID generation is Windows-centric, and no explicit Linux/macOS alternatives are mentioned in that context.
Recommendations
- When suggesting GUID generation, mention platform-neutral methods (e.g., 'uuidgen' on Linux/macOS, or online generators) alongside PowerShell.
- Present cURL examples before or alongside PowerShell scripts to emphasize cross-platform compatibility.
- Explicitly state that all steps can be performed on Linux/macOS and provide command-line alternatives where relevant.
- Where screenshots or instructions reference Windows-specific tools, add notes or visuals for Linux/macOS equivalents.
Active Directory B2C
Deploy custom policies with Azure Pipelines
.../active-directory-b2c/deploy-custom-policies-devops.md
Medium Priority
View Details →
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 via Azure Pipelines. There are no examples or guidance for Linux/macOS users, such as Bash or cross-platform scripting alternatives. The instructions assume the use of PowerShell, which is natively available on Windows and only optionally available on Linux/macOS. This creates friction for non-Windows users and may block those unfamiliar with PowerShell.
Recommendations
- Provide equivalent Bash or cross-platform script examples for deploying policies.
- Mention that PowerShell Core is available on Linux/macOS and provide installation instructions or links.
- Add guidance for running the deployment script on Linux/macOS agents in Azure Pipelines.
- Clarify any platform-specific requirements or limitations for the provided scripts.
- Consider providing a platform-agnostic approach (e.g., using Azure CLI, REST API calls via curl, or Python scripts).
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only command-line example provided for configuring password expiry duration, and the Microsoft Graph PowerShell module is referenced exclusively. There are no CLI or scripting examples for Linux/macOS users (e.g., Bash, curl, or Azure CLI). Additionally, the PowerShell example appears before any mention of alternative methods, and there is no guidance for Linux/macOS environments.
Recommendations
- Provide equivalent examples using cross-platform tools such as curl, HTTPie, or Azure CLI for all Microsoft Graph API operations.
- Include instructions for installing and using the Microsoft Graph PowerShell module on Linux/macOS, or clarify its cross-platform support.
- Add Bash or shell script examples for PATCH requests to Microsoft Graph, demonstrating how Linux/macOS users can perform the same actions.
- Explicitly mention platform compatibility for all tools and commands.
- Consider reordering examples so that platform-neutral methods (e.g., direct API calls) appear before or alongside PowerShell examples.
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 →
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 used exclusively for key and certificate generation, with no equivalent Linux/macOS commands or tooling mentioned. Windows tools and patterns (PowerShell, New-SelfSignedCertificate) are referenced without alternatives, and Windows examples are presented first and solely. This creates friction for Linux/macOS users, who must find their own solutions for these steps.
Recommendations
- Provide equivalent Linux/macOS commands for generating symmetric keys (e.g., using openssl or dd).
- Include instructions for generating self-signed certificates on Linux/macOS (e.g., using openssl).
- Reference cross-platform tools and scripts where possible.
- Explicitly state that the PowerShell examples are for Windows and offer alternatives for other platforms.
- Consider reordering examples to present cross-platform or Linux/macOS options alongside or before Windows-specific instructions.