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 176-200 of 392 flagged pages
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/deploy-custom-policies-devops.md
.../active-directory-b2c/deploy-custom-policies-devops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively providing PowerShell scripts and instructions, with no mention of Bash, shell scripts, or cross-platform alternatives. All automation and deployment steps are described using PowerShell, which is traditionally associated with Windows environments, and there are no Linux-specific or cross-platform examples. The use of PowerShell as the only scripting language and the absence of any reference to Linux-native tools or commands may hinder users working in Linux-based CI/CD environments.
Recommendations
- Provide equivalent Bash or shell script examples for deploying policies, ensuring Linux users can follow along without needing PowerShell.
- Explicitly mention that PowerShell Core is cross-platform and provide guidance for installing and running scripts on Linux/macOS, if PowerShell must be used.
- Include notes or sections on how to adapt the deployment process for Linux agents in Azure Pipelines, such as using Bash tasks or alternative scripting languages.
- List both Windows and Linux prerequisites, including any required tools or dependencies for each platform.
- Where possible, use platform-agnostic language and tools, or clearly indicate when a step is specific to Windows or PowerShell.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/id-token-hint.md
...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for cryptographic key and certificate generation, referencing Windows-specific tools (e.g., New-SelfSignedCertificate), and omitting equivalent Linux/macOS commands or guidance. All code snippets for key/certificate generation assume a Windows environment, and there is no mention of cross-platform alternatives or ordering that gives Linux parity.
Recommendations
- For every PowerShell example (e.g., generating a symmetric key or self-signed certificate), provide equivalent commands for Linux/macOS, such as using OpenSSL or relevant shell commands.
- Explicitly mention that the steps can be performed on non-Windows platforms, and provide links or references to cross-platform tooling.
- When introducing tooling or code snippets, present both Windows and Linux/macOS options together, or alternate the order to avoid always listing Windows first.
- Add a section or note on cross-platform considerations, including any differences in file paths, certificate stores, or command-line utilities.
- Where possible, use language-neutral or platform-neutral pseudocode for generic steps, and only provide platform-specific details as needed.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs.md
...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (such as Server Manager and AD FS Management MMC), and does not provide any Linux-based alternatives or command-line instructions for managing AD FS. All configuration steps for AD FS are described using GUI tools available only on Windows Server, with no mention of PowerShell, CLI, or cross-platform approaches. There are no Linux or non-Windows examples for AD FS setup, and the documentation implicitly assumes the administrator is operating in a Windows environment.
Recommendations
- Provide PowerShell command-line equivalents for all AD FS configuration steps, as PowerShell can be run on Windows Server Core and remotely.
- Explicitly mention that AD FS is a Windows Server feature, but clarify what steps (if any) can be performed from non-Windows environments (e.g., via remote PowerShell, REST APIs, or Azure CLI).
- If possible, reference or link to any open-source or third-party tools that allow AD FS management from Linux or macOS, or clarify that such options are not available.
- Add a note early in the prerequisites section stating that AD FS management is only supported on Windows Server, and suggest alternatives for Linux-based identity providers if relevant.
- Where possible, provide parity by showing how to configure a generic OpenID Connect provider using Linux-based identity solutions (such as Keycloak or IdentityServer) as a comparative example.
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 First
Missing Linux Example
Summary
The documentation page primarily focuses on using the Azure portal, which is cross-platform, but in the section on revoking a user's session, it exclusively provides instructions and examples for Microsoft Graph PowerShell, specifically referencing 'Windows PowerShell' and omitting any Linux or cross-platform alternatives. There are no CLI, Bash, or platform-neutral examples for this task, and the language implies a Windows-first approach.
Recommendations
- Provide equivalent instructions and examples for revoking user sessions using the Microsoft Graph CLI, Azure CLI, or Bash scripts, which are cross-platform and work on Linux and macOS.
- Replace references to 'Windows PowerShell' with 'PowerShell', and clarify that PowerShell Core is available on Linux and macOS, or provide explicit instructions for those platforms.
- Wherever PowerShell is mentioned, add a note or section for Linux/macOS users, including any prerequisites or differences in command usage.
- Consider including REST API examples (e.g., using curl) for tasks currently only shown with PowerShell, to ensure platform neutrality.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs-saml.md
...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Windows-only tools (AD FS Management snap-in, Event Viewer, Server Manager) and PowerShell cmdlets for configuration and troubleshooting. There are no Linux or cross-platform alternatives or examples provided for key steps such as certificate creation, AD FS management, or log inspection. All procedural instructions assume a Windows server environment and do not mention or address Linux-based AD FS alternatives or how to interact with AD FS from non-Windows systems.
Recommendations
- Provide equivalent command-line or UI instructions for managing AD FS from non-Windows environments, if possible (e.g., via REST APIs, if available).
- Include examples for certificate creation and management using cross-platform tools such as OpenSSL.
- Document how to interact with AD FS from Linux or macOS clients, or clarify that AD FS is a Windows-only technology if that is the case.
- For PowerShell commands, suggest alternatives using cross-platform scripting or remote management tools, or note the requirement for Windows.
- Where troubleshooting steps reference Windows Event Viewer, suggest how to access logs remotely or via command-line tools that may be available on other platforms.
- Clearly state any platform limitations early in the documentation, and provide guidance for users on non-Windows platforms.
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 demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows (e.g., Visual Studio, .sln files, Web.config), omitting any mention of Linux-compatible editors, build tools, or configuration patterns. There are no Linux-specific instructions or examples, and the guidance assumes a Windows development environment.
Recommendations
- Include instructions for opening and editing the project using cross-platform editors such as VS Code or JetBrains Rider, and mention how to build and run the project using .NET CLI commands (dotnet build/run) instead of only referencing Visual Studio.
- Provide examples for editing configuration files on Linux (e.g., using nano, vim, or gedit) and clarify file path differences (forward slashes vs. backslashes).
- Mention how to run and debug the sample application on Linux and macOS, including any prerequisites (e.g., installing the .NET SDK on Linux).
- If the sample is Windows-specific (e.g., uses Windows-only libraries), clearly state this and, if possible, provide or reference a cross-platform alternative.
- Ensure that all code snippets and instructions are platform-agnostic where possible, or provide parallel instructions for both Windows and Linux environments.
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
Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell scripts for critical steps (such as creating self-signed certificates and random keys), referencing Visual Studio for deployment, and omitting equivalent Linux/macOS commands or tooling. There are no Bash, OpenSSL, or cross-platform alternatives, which may hinder users on non-Windows systems.
Recommendations
- Provide equivalent Bash/OpenSSL commands for creating self-signed certificates and random strings, suitable for Linux/macOS users.
- Include deployment instructions using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code, not just Visual Studio.
- Explicitly mention that PowerShell examples are for Windows and offer alternatives for other platforms.
- Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented equally, rather than Windows-first.
- Add notes or links to official Microsoft documentation for cross-platform certificate and key management.
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 is largely platform-neutral in its technical content, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, it lists Windows-specific tools (Microsoft Edge or Internet Explorer developer tools) alongside browser extensions, and provides a link to a Microsoft blog post about using Edge/IE developer tools. There are no explicit Linux or cross-platform debugging tool examples given, nor is there mention of command-line tools or approaches common on Linux (such as curl, openssl, or SAML-specific CLI utilities). The order of tool presentation also puts Microsoft/Windows tools last, but their inclusion without Linux equivalents suggests a mild Windows bias.
Recommendations
- Add examples or references to Linux-compatible SAML debugging tools, such as using curl, openssl, or SAML-specific CLI tools (e.g., saml2aws, xmlsec1) for inspecting SAML messages.
- Mention browser extensions as cross-platform tools more prominently, emphasizing their availability on Linux, macOS, and Windows.
- If referencing developer tools for browsers, clarify that Chrome and Firefox DevTools are available on Linux and macOS as well.
- Consider adding a section or note on how to capture and inspect SAML traffic using command-line tools or network analyzers (e.g., tcpdump, Wireshark) on Linux.
- Avoid linking exclusively to Microsoft/Windows-specific resources for debugging; provide equivalent Linux/macOS guidance or links where possible.
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 page demonstrates a Windows bias by exclusively referencing Visual Studio (a primarily Windows IDE) and providing instructions that assume the use of Windows-specific tools and workflows (such as Solution Explorer, right-click context menus, and F5 debugging). There are no examples or guidance for running or developing the sample application on Linux or using cross-platform tools like VS Code or the .NET CLI.
Recommendations
- Add instructions for running the sample using the .NET CLI (dotnet build/run) to support Linux and macOS users.
- Include examples for setting up and debugging the application in Visual Studio Code, which is cross-platform.
- Mention alternative editors and workflows for non-Windows environments, such as JetBrains Rider or command-line tools.
- Clarify which steps are specific to Visual Studio on Windows and provide equivalent steps for Linux/macOS where possible.
- Explicitly state the platform requirements and provide links to cross-platform .NET documentation.
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 a 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) as alternatives. No Linux-specific tools, commands, or deployment patterns are discussed, and all example application guidance assumes a Windows environment. There are no PowerShell commands, but the only concrete application example is Windows-centric.
Recommendations
- Include Linux-based web application examples (e.g., Apache, Nginx, or Tomcat) alongside or in place of IIS.
- Provide links to documentation for setting up test applications on Linux, such as guides for deploying Apache or Nginx.
- Mention that the solution is platform-agnostic and can be used with both Windows and Linux back-end applications.
- Where application setup is referenced, offer both Windows and Linux instructions or note any differences.
- Explicitly state that the configuration steps for F5 BIG-IP and Azure AD B2C are not limited to Windows environments.
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 exclusively referencing Visual Studio (a Windows-centric tool) for publishing the API, without mentioning cross-platform alternatives or providing Linux/macOS instructions. There are no command-line or non-Windows deployment examples, and the workflow assumes the user is operating in a Windows environment.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as the .NET CLI (dotnet publish) and Azure CLI, which work on Linux and macOS.
- Include examples or references for uploading certificates and configuring App Service settings using Azure CLI, PowerShell, and the Azure Portal, making clear which methods are cross-platform.
- Explicitly state that Visual Studio is optional and provide equivalent steps for Linux/macOS users.
- Review all steps for hidden Windows dependencies and ensure parity in documentation for Linux and macOS environments.
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 demonstrates a Windows bias by exclusively providing PowerShell-based instructions for enabling Saviynt to delete users in Azure AD B2C. It explicitly instructs users to install the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or cross-platform examples, and the use of Windows tools and terminology is prioritized.
Recommendations
- Provide equivalent instructions using Microsoft Graph CLI (az cli or msgraph-cli), which are cross-platform and work on Linux, macOS, and Windows.
- Include Bash or shell script examples for Linux users, especially for authentication and role assignment steps.
- Clarify that the Microsoft Graph PowerShell module is available on non-Windows platforms via PowerShell Core, and provide installation instructions for Linux/macOS.
- Avoid language that implies Windows is required (e.g., 'on a Windows workstation or server'); instead, use 'on your workstation' and specify cross-platform compatibility.
- Add a section or note explicitly addressing Linux/macOS users, ensuring parity in setup and troubleshooting guidance.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/secure-rest-api.md
.../main/articles/active-directory-b2c/secure-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the certificate creation section, where it explicitly recommends using Azure Key Vault or a PowerShell module for creating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) for certificate generation. The only scripting tool mentioned for local certificate creation is PowerShell, which is Windows-centric. No Linux or macOS equivalents are referenced, and no cross-platform CLI instructions are provided for key tasks like certificate generation.
Recommendations
- Add Linux/macOS-friendly instructions for generating self-signed certificates, such as using OpenSSL, alongside or before PowerShell examples.
- Explicitly mention that certificate generation can be performed on any OS and provide cross-platform command-line examples.
- Where PowerShell is referenced, offer equivalent bash or shell commands for Linux/macOS users.
- Review other sections for any implicit Windows-first assumptions and ensure parity in tool recommendations and example commands.
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, screenshots, and tooling references are Windows-centric, with no mention of Linux or cross-platform alternatives. There are no Linux or macOS instructions, nor are there any examples using cross-platform frameworks or tools.
Recommendations
- Provide equivalent instructions for running the sample on Linux and macOS, such as using .NET Core/MAUI or other cross-platform UI frameworks.
- Include examples for building and running the application using command-line tools (dotnet CLI) instead of only Visual Studio.
- Mention and provide guidance for alternative editors (e.g., VS Code) and package management approaches that work on Linux.
- Add screenshots and workflow steps for Linux/macOS environments.
- Clarify in the prerequisites and introduction whether the sample is Windows-only, and if so, provide or link to cross-platform alternatives.
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, with no equivalent example or guidance for Linux or cross-platform environments. It assumes the use of Windows tools and patterns (PowerShell, Invoke-RestMethod), and does not mention or prioritize Linux-compatible alternatives such as Bash, curl, or Python. This creates a Windows-first experience and excludes users on Linux or macOS.
Recommendations
- Provide a Bash or shell script example using curl or httpie to demonstrate how to perform the same API calls on Linux/macOS.
- Include a cross-platform example using a language like Python, which is available on both Windows and Linux.
- Explicitly mention that the PowerShell script is for Windows, and direct Linux/macOS users to equivalent instructions.
- Consider reordering the examples or providing both Windows and Linux/macOS options side-by-side to ensure parity.
- Reference platform-agnostic tools (e.g., Azure CLI, Microsoft Graph CLI) if available, or provide links to relevant documentation for non-Windows users.
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 example for programmatically accessing audit logs, with no equivalent example for Linux users (e.g., Bash/cURL). The script assumes use of PowerShell, which is traditionally a Windows tool, and there is no mention of Linux-native tools or cross-platform alternatives. This may disadvantage users on Linux or macOS platforms.
Recommendations
- Add a Bash/cURL example for querying the Microsoft Graph API to retrieve audit logs, demonstrating how to authenticate and paginate results.
- Explicitly mention that PowerShell Core is cross-platform and can be used on Linux/macOS, or provide installation instructions for non-Windows users.
- Where possible, provide both Windows (PowerShell) and Linux (Bash/cURL or Python) script examples side by side.
- Reference Linux-native tools (e.g., jq for JSON processing) in the context of handling API responses.
- Clarify in the documentation that the API can be accessed from any platform, not just Windows, and provide guidance for Linux users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/id-token-hint.md
...ob/main/articles/active-directory-b2c/id-token-hint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides code and tooling examples exclusively for Windows environments, specifically using PowerShell for key and certificate generation. There are no equivalent instructions or examples for Linux or cross-platform environments, and Windows tools are mentioned first and exclusively.
Recommendations
- Provide equivalent Linux and cross-platform examples for generating symmetric keys (e.g., using OpenSSL, /dev/urandom, or Python scripts).
- Include instructions for generating self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell example.
- Explicitly mention that the provided PowerShell commands are for Windows, and offer alternatives for other operating systems.
- Reference cross-platform tools (such as OpenSSL) before or alongside Windows-specific tools to avoid the impression of Windows being the default or only supported environment.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/client-credentials-grant-flow.md
.../active-directory-b2c/client-credentials-grant-flow.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references Microsoft PowerShell as the primary method for generating GUIDs and provides a PowerShell script as the first scripting example for obtaining an access token. While a cURL example is also provided, the ordering and explicit mention of PowerShell tools and commands suggest a Windows-first approach. There is no explicit Linux shell or cross-platform alternative for GUID generation, and the PowerShell script is presented before the cURL example.
Recommendations
- When suggesting GUID generation, provide both PowerShell (Windows) and Linux/macOS (e.g., `uuidgen` or `cat /proc/sys/kernel/random/uuid`) command examples, or mention cross-platform tools first.
- Present scripting examples in parallel (PowerShell and cURL/bash) or lead with a cross-platform tool like cURL, to avoid the impression of Windows-first bias.
- Explicitly mention that all steps and scripts are cross-platform where possible, and provide Linux/macOS equivalents for any Windows-specific instructions.
- Where referencing online tools, clarify that they are platform-agnostic.
- Consider including bash or Python script examples alongside PowerShell for parity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-wpf-desktop-app.md
...b2c/configure-authentication-sample-wpf-desktop-app.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 targeting WPF (Windows Presentation Foundation) desktop applications and requiring Visual Studio 2019. There are no examples or guidance for Linux or cross-platform desktop development, nor are alternative tools or frameworks mentioned. All code and instructions assume a Windows environment, and there is no mention of Linux equivalents or how to adapt the process for non-Windows platforms.
Recommendations
- Provide parallel instructions and examples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
- Include guidance for setting up the development environment on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI).
- Offer Linux-specific steps for cloning the repository, building, and running the sample application using the .NET CLI.
- Mention any platform-specific limitations or considerations for Azure AD B2C authentication in non-Windows environments.
- If WPF is inherently Windows-only, clarify this early and provide links or references to cross-platform alternatives for developers targeting Linux.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-call-rest-api.md
...-directory-b2c/custom-policies-series-call-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell scripts and referencing Microsoft PowerShell as the HTTP client for testing the Node.js app, without offering equivalent Linux/macOS command-line examples (such as curl or HTTPie). The only terminal-based example is PowerShell, and no mention is made of common cross-platform or Linux-native tools. This may hinder Linux/macOS users from following the testing steps directly.
Recommendations
- Provide equivalent Linux/macOS command-line examples using curl or HTTPie for making HTTP POST requests to the Node.js app, alongside the PowerShell example.
- Mention cross-platform tools (curl, HTTPie, Postman) as alternatives to PowerShell for testing HTTP endpoints.
- When referencing tools, avoid listing Microsoft/Windows tools first or exclusively; instead, present options for both Windows and Linux/macOS users.
- Explicitly state that the instructions are platform-agnostic where possible, and clarify any steps that are specific to Windows or require adaptation for other operating systems.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/deploy-custom-policies-devops.md
.../active-directory-b2c/deploy-custom-policies-devops.md
High Priority
View Details →
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 scripting alternatives. All code examples, instructions, and pipeline tasks are centered around PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux or macOS users, nor are there examples using platform-agnostic tools or scripts.
Recommendations
- Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
- Include instructions for running the deployment on non-Windows agents in Azure Pipelines.
- Mention and demonstrate the use of cross-platform tools (e.g., Azure CLI, curl, or REST API calls via Bash) as alternatives to PowerShell.
- Clarify any platform requirements or limitations for the provided scripts, and suggest how users on Linux/macOS can adapt the process.
- When listing steps or tools, avoid assuming PowerShell as the default and present cross-platform options side-by-side.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-wpf-desktop-app-options.md
...y-b2c/enable-authentication-wpf-desktop-app-options.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows, specifically WPF desktop applications, with all code samples and guidance tailored to the Windows ecosystem. There are no Linux or cross-platform examples, and Windows-specific patterns (such as WindowInteropHelper and WPF APIs) are used exclusively. The documentation does not mention or provide alternatives for Linux or other platforms.
Recommendations
- Include equivalent examples for cross-platform desktop frameworks (such as .NET MAUI, Avalonia, or GTK#) that run on Linux.
- Provide guidance or links for configuring Azure AD B2C authentication in Linux desktop applications.
- Clarify in the introduction that the guidance is specific to WPF/Windows, and link to cross-platform or Linux-specific documentation if available.
- When discussing redirect URIs and MSAL usage, note any platform-specific considerations for Linux or macOS.
- If possible, provide PowerShell and Bash/terminal command equivalents for any setup or configuration steps.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-spa-app.md
.../active-directory-b2c/enable-authentication-spa-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily in the 'Run your SPA application' section, where only PowerShell commands are shown for running the app. There is no mention of Linux or macOS command-line equivalents, nor any guidance for non-Windows users. Earlier steps use generic 'command shell' language, but the explicit use of PowerShell syntax and lack of cross-platform notes may confuse or exclude Linux/macOS developers.
Recommendations
- Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples, especially in the 'Run your SPA application' section.
- Use cross-platform command syntax where possible (e.g., 'node index.js' instead of 'npm ./index.js', which is not standard).
- Add notes clarifying that all steps can be performed on Linux/macOS, and specify any OS-specific considerations.
- Avoid using PowerShell-specific syntax unless necessary, or always pair it with bash equivalents.
- Explicitly mention that the instructions are cross-platform and tested on Windows, Linux, and macOS.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/force-password-reset.md
.../articles/active-directory-b2c/force-password-reset.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides PowerShell-based examples (specifically using the Microsoft Graph PowerShell module) for configuring password expiry, but does not offer equivalent CLI or scripting examples for Linux/macOS users. There is an implicit assumption that administrators will use PowerShell, which is more common on Windows. No mention is made of cross-platform alternatives such as Azure CLI, Bash, or REST API usage via curl, and there are no Linux/macOS-specific instructions or examples.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts (e.g., using curl to call Microsoft Graph API), which are natively available on Linux/macOS.
- Explicitly mention that PowerShell Core is cross-platform and provide installation instructions for non-Windows systems, if PowerShell must be used.
- Where possible, present REST API calls with both PowerShell and curl/Bash examples, so users on any OS can follow along.
- Reorder or parallelize examples so that Windows and Linux/macOS approaches are given equal prominence.
- Add a note clarifying that all operations can be performed from any OS, and link to relevant cross-platform tool documentation.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs-saml.md
...es/active-directory-b2c/identity-provider-adfs-saml.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias throughout. All AD FS configuration steps are described using Windows-specific tools such as Server Manager, AD FS Management snap-in, and PowerShell cmdlets. There are no Linux or cross-platform alternatives provided for any step, and all troubleshooting instructions reference Windows event logs and tools. The documentation assumes the administrator is operating in a Windows environment and does not mention or provide guidance for Linux-based AD FS alternatives or SAML identity providers.
Recommendations
- Provide equivalent instructions for configuring SAML identity providers using non-Windows AD FS alternatives (e.g., Shibboleth, SimpleSAMLphp) commonly used on Linux.
- Include examples of how to generate and manage certificates using Linux tools (e.g., OpenSSL) alongside any Windows-specific instructions.
- Offer guidance on how to view and troubleshoot SAML logs and events using Linux-based tools or generic SAML debugging tools.
- Clearly state at the beginning of the document that the instructions are Windows/AD FS-specific, and link to separate guides for Linux-based SAML providers if available.
- Where PowerShell or Windows GUI steps are given, provide equivalent CLI or configuration file examples for Linux-based SAML providers.