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 126-150 of 392 flagged pages
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 strong Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE) for running the sample application, and by providing instructions and workflows that assume a Windows environment. There are no examples or guidance for Linux users, such as using cross-platform .NET CLI tools or alternative editors like VS Code. The documentation omits Linux-specific instructions for running or debugging the ASP.NET application.
Recommendations
- Add instructions for running the sample application using the .NET CLI (dotnet run), which works on Linux, macOS, and Windows.
- Include examples for setting up and debugging the application in Visual Studio Code, a cross-platform editor.
- Mention any prerequisites for Linux users, such as installing the .NET SDK and required dependencies.
- Provide equivalent steps for Linux/macOS environments, such as using terminal commands instead of Visual Studio UI actions.
- Clarify that Visual Studio is optional and that the sample can be run on any platform supported by .NET.
Create Pull Request
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, specifically targeting WPF (Windows Presentation Foundation) desktop applications and requiring Visual Studio 2019. There are no Linux or cross-platform equivalents mentioned, nor are there instructions or examples for developing, building, or running the sample on Linux or macOS. All tooling and code samples are Windows-specific, and the documentation assumes a Windows development environment throughout.
Recommendations
- Add a section describing how to build and run a similar desktop application using cross-platform frameworks such as .NET MAUI or Avalonia, which support Linux and macOS.
- Provide instructions for setting up the development environment on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI) and for restoring NuGet packages and building the project via command line.
- Include examples or notes on how to adapt the authentication flow for non-Windows platforms, highlighting any differences in browser invocation or redirect URI handling.
- Clarify in the prerequisites and introduction that the guide is Windows-specific, and link to cross-platform alternatives if available.
- Offer sample code or links for equivalent authentication flows in Linux-friendly desktop frameworks.
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 PowerShell for generating GUIDs and provides a PowerShell script as the first scripting example for obtaining tokens. The mention of PowerShell and Microsoft tools precedes alternatives, and no explicit Linux or cross-platform command-line alternatives are given for all steps (e.g., GUID generation). While a cURL example is provided, the overall pattern puts Windows-centric tools and workflows first.
Recommendations
- When instructing users to generate a GUID, provide a cross-platform alternative (e.g., 'uuidgen' for Linux/macOS) alongside PowerShell.
- Present scripting examples in a neutral order or offer both PowerShell and Bash/cURL examples together, clarifying their platform compatibility.
- Avoid referencing Microsoft/Windows tools exclusively; always mention or link to Linux/macOS equivalents where relevant.
- Explicitly state that steps can be performed on any OS, and provide guidance for users on Linux/macOS for all command-line operations.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by providing only PowerShell examples for testing the REST API, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). The only tool-specific guidance for making HTTP requests is for PowerShell, a Windows-centric tool, and it is mentioned before any cross-platform alternatives. No Linux or macOS-specific instructions or examples are given for testing the Node.js app locally or after deployment.
Recommendations
- Provide equivalent Linux/macOS command-line examples using curl or httpie alongside the PowerShell example for making HTTP requests to the REST API.
- When referencing tools, mention cross-platform options (e.g., curl, Postman, httpie) before or alongside Windows-specific tools like PowerShell.
- Explicitly state that the Node.js app and instructions are cross-platform, and clarify that all steps can be performed on Linux, macOS, or Windows.
- Add a note or section for Linux/macOS users, including terminal commands and any environment-specific considerations.
- Where possible, use neutral language (e.g., 'terminal' instead of 'PowerShell') and avoid assuming the user is on Windows.
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 samples and pipeline task instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for Linux or macOS users. The documentation does not address how to adapt the process for non-Windows agents or provide equivalent examples using other scripting languages or tools.
Recommendations
- Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
- Mention that PowerShell Core is cross-platform and clarify if the provided script is compatible with PowerShell Core on Linux/macOS.
- Include instructions for running the deployment script on Linux-based Azure Pipeline agents, including any prerequisites (e.g., installing PowerShell Core).
- Offer guidance or templates for using other common CI/CD scripting languages (e.g., Python) if possible.
- Explicitly state platform requirements and provide troubleshooting tips for non-Windows environments.
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
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by providing only PowerShell examples for key generation and certificate creation, referencing Windows-specific tools (e.g., PowerShell's New-SelfSignedCertificate), and omitting equivalent Linux/macOS commands or guidance. All code samples for cryptographic operations are Windows-centric, and there is no mention of cross-platform alternatives or parity for non-Windows environments.
Recommendations
- For every PowerShell or Windows-specific example, provide equivalent Linux/macOS commands (e.g., using OpenSSL for key and certificate generation).
- Explicitly mention that the steps can be performed on Linux/macOS and provide sample shell commands.
- Reference cross-platform tools (such as OpenSSL, or .NET CLI commands) alongside Windows tools.
- Reorder sections or add notes to avoid implying Windows is the default or only supported environment.
- Link to external documentation for Linux/macOS cryptographic operations where appropriate.
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 Windows bias primarily in the 'Run your SPA application' section, where only PowerShell commands are shown for running the app (e.g., 'npm install', 'npm ./index.js'), and no Linux/macOS shell equivalents are provided. Throughout the rest of the document, instructions are generally cross-platform, but the explicit use of PowerShell syntax and lack of Linux-specific notes or examples may confuse or exclude non-Windows users.
Recommendations
- Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples wherever commands are shown, especially in the 'Run your SPA application' section.
- Use neutral, cross-platform terminology such as 'terminal' or 'command line' instead of 'command shell', and clarify that the instructions apply to all major operating systems.
- Where file paths or commands may differ between platforms, explicitly note the differences or provide side-by-side examples.
- Test and document the startup commands for Linux/macOS (e.g., 'node index.js' instead of 'npm ./index.js', which is not standard on any platform).
- Consider adding a prerequisites note confirming that the instructions are valid for Windows, Linux, and macOS, and link to platform-specific Node.js installation guides if appropriate.
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 assumes the use of Windows-based AD FS management tools (Server Manager, AD FS Management console) and provides only GUI-based instructions specific to Windows environments. There are no Linux or cross-platform command-line alternatives, nor any mention of how to perform equivalent steps on non-Windows systems. The documentation also references Windows-specific endpoints and concepts before any mention of general OpenID Connect standards.
Recommendations
- Provide PowerShell and command-line alternatives for AD FS configuration, and clarify if these can be run on non-Windows platforms (e.g., via Windows Admin Center, remote management, or cross-platform tools).
- Explicitly state that AD FS is a Windows Server role and clarify any platform limitations early in the prerequisites.
- If possible, mention or link to open-source or Linux-compatible alternatives to AD FS for OpenID Connect integration.
- Add a note or section explaining that the described steps require access to a Windows Server environment, and offer guidance for users working in mixed or non-Windows environments.
- Where possible, use OpenID Connect terminology and standards first, then describe how AD FS implements them, to reduce Windows-centric framing.
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 generally 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) and provides a link to a Microsoft blog post about using these tools, while only briefly mentioning browser extensions for Chrome and Firefox. There are no Linux-specific tools or command-line approaches mentioned, and no PowerShell or Windows command-line examples are present, but the tool recommendations and order of mention show a subtle Windows bias.
Recommendations
- Include Linux-friendly SAML debugging tools, such as command-line utilities (e.g., curl, openssl, xmlsec1) or Linux-compatible browser extensions.
- List browser-agnostic tools and extensions first, and group them by browser/platform rather than mentioning Microsoft tools last.
- If referencing developer tools, clarify that Chrome and Firefox developer tools are also available on Linux and macOS, and provide equivalent instructions or links.
- Consider adding a section or note on how to capture and analyze SAML traffic using cross-platform tools like Wireshark or Fiddler Everywhere.
- Avoid linking only to Microsoft/Windows-specific blog posts; provide or link to platform-neutral guidance where possible.
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. It exclusively references Visual Studio, .sln files, and Web.config (XML), which are Windows-centric tools and patterns. There are no examples or instructions for Linux or cross-platform development environments (e.g., VS Code, command-line builds, or configuration via appsettings.json). The documentation assumes the reader is using Windows and does not mention Linux equivalents or alternatives.
Recommendations
- Include instructions for opening and editing the project using cross-platform tools such as VS Code or JetBrains Rider.
- Provide examples for configuring the application using appsettings.json or environment variables, which are commonly used in Linux and containerized environments.
- Add guidance for building and running the sample using the .NET CLI (dotnet build/run) instead of relying solely on Visual Studio.
- Mention how to locate and edit configuration files on Linux systems, and clarify any OS-specific paths or commands.
- Ensure that any screenshots or UI references (e.g., Azure portal) are not Windows-specific, or provide notes for Linux/macOS users if differences exist.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/integrate-with-app-code-samples.md
...ctive-directory-b2c/integrate-with-app-code-samples.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. While it covers a broad range of platforms (iOS, Android, Node.js, Python), .NET and Windows desktop samples are given prominence, with a dedicated sample for Windows Desktop (.NET WPF) but no equivalent Linux desktop application. The .NET samples implicitly target Windows environments, and there is no mention of Linux-specific tools or desktop frameworks. Additionally, the only desktop app sample is for Windows, with no parity for Linux desktop environments.
Recommendations
- Add Linux desktop application samples (e.g., using .NET MAUI, GTK#, or Electron) to provide parity with the Windows desktop sample.
- Explicitly mention cross-platform compatibility for .NET samples, and provide instructions or notes for running them on Linux (e.g., using .NET Core on Linux).
- Where desktop or console samples are provided, clarify if they are cross-platform or provide Linux-specific instructions and troubleshooting.
- Consider including examples or references for common Linux development environments and tools 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 a Windows bias by referencing IIS as the example application for testing, providing a link to IIS setup instructions, and omitting any mention or example of Linux-based web servers (such as Apache or Nginx). There are no Linux-specific instructions, tools, or examples, and the only application setup guidance is for a Windows environment.
Recommendations
- Add parallel instructions and examples for deploying and testing with a Linux-based web server (e.g., Apache, Nginx) alongside the IIS example.
- Provide links to official documentation for setting up common Linux web servers.
- Explicitly mention that the solution is platform-agnostic and can be used with both Windows and Linux applications.
- Include troubleshooting tips relevant to Linux environments.
- Balance references to Windows tools (like IIS) with Linux equivalents to ensure parity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-akamai-secure-hybrid-access.md
...e-directory-b2c/partner-akamai-secure-hybrid-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and workflows (such as ASP.NET MVC, OWIN middleware, and .NET code samples) without providing equivalent Linux or cross-platform examples. Certificate management and application examples are also Windows-centric, and there is a lack of guidance for Linux-based environments or tools.
Recommendations
- Provide Linux-based or cross-platform examples for application integration, such as using Java (Spring), Python (Flask/Django), or Node.js for OIDC/SAML flows.
- Include instructions for certificate generation and management using Linux tools (e.g., OpenSSL) alongside or instead of Windows-specific instructions.
- Offer sample configurations and code snippets for popular Linux web servers (e.g., Apache, Nginx) and application frameworks.
- Reference cross-platform tools and avoid assuming the use of Windows-only technologies (such as OWIN or ASP.NET MVC) as the default.
- Where application examples are given (e.g., header-demo-app), provide deployment and testing steps for both Windows and Linux 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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by only referencing Visual Studio (a Windows-centric tool) for publishing code and omitting any Linux/macOS deployment or configuration examples. There are no CLI, VS Code, or cross-platform instructions, and the workflow assumes use of Windows-based tooling and patterns.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as Azure CLI, Azure DevOps, or GitHub Actions, which work on Linux and macOS.
- Include examples for publishing the code from VS Code or command-line interfaces (dotnet CLI), not just Visual Studio.
- Explicitly mention that the deployment and configuration steps can be performed from Linux/macOS environments and provide relevant guidance.
- Ensure that any references to uploading certificates or configuring app settings in Azure App Service include both portal and CLI/PowerShell methods, with parity for Linux users.
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
Missing Linux Example
Windows First
Summary
The documentation page is generally platform-neutral when describing Azure portal operations, but introduces Windows bias in the section on revoking user sessions. Only Microsoft Graph PowerShell is mentioned, with explicit references to 'Windows PowerShell' and no mention of Linux/macOS equivalents or cross-platform instructions. There are no CLI or bash examples, and PowerShell is presented as the primary (and only) scripting tool, which may exclude Linux users.
Recommendations
- Explicitly state that Microsoft Graph PowerShell is cross-platform and can be used on Windows, Linux, and macOS.
- Replace references to 'Windows PowerShell' with 'PowerShell', or clarify that the instructions apply to all supported platforms.
- Provide equivalent examples using Azure CLI, Bash, or direct Microsoft Graph API calls via curl or httpie for Linux/macOS users.
- Add a note or section for Linux/macOS users, outlining any prerequisites or differences in running PowerShell or using alternative tools.
- Ensure that scripting and automation examples are not Windows-centric, and that parity is maintained for all major operating systems.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-grit-authentication.md
...es/active-directory-b2c/partner-grit-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows Hello as the primary example of biometric authentication, both in the introductory explanation and the scenario walkthrough. There is no mention of Linux or macOS biometric solutions, nor are there examples or guidance for users on those platforms. The documentation assumes familiarity with Windows-specific tools and does not provide parity for Linux users.
Recommendations
- Include examples and references to biometric authentication solutions available on Linux (e.g., fprintd, fingerprint-gui) and macOS (e.g., Touch ID).
- When describing scenarios, provide equal detail for non-Windows platforms, such as how enrollment and authentication would work on Linux or macOS devices.
- Avoid using Windows Hello as the default or only example; instead, mention it alongside other platform-specific solutions.
- Add troubleshooting or setup notes for Linux users who may need to configure biometric hardware or software.
- Explicitly state platform requirements and provide links to relevant documentation for biometric setup on all major operating systems.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows by referencing Visual Studio (a Windows-centric tool) as the primary publishing method for the API, without mentioning cross-platform or Linux alternatives. There are no examples or instructions for deploying the API from Linux or using non-Windows tools, and the only deployment instructions link to Visual Studio documentation. This may create the impression that the integration is best or only supported on Windows environments.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, which can be run from Linux, macOS, or Windows.
- Include examples for deploying the API using the 'dotnet publish' and 'az webapp deploy' commands, which are platform-agnostic.
- Explicitly mention that the API can be deployed from any OS, and provide links to documentation for Linux/macOS users.
- Avoid referencing only Windows-specific tools (like Visual Studio) as the primary or sole method for deployment.
- Add a note or section for Linux/macOS users to ensure parity and inclusivity.
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 generating certificates and random keys, with no equivalent Linux or cross-platform instructions. The use of PowerShell and references to Visual Studio for deployment further reinforce a Windows-centric approach, while omitting guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Bash or 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, VS Code, or GitHub Actions, not just Visual Studio.
- Explicitly mention that the PowerShell examples are for Windows and offer alternative steps for other operating systems.
- Add notes or links to official Microsoft documentation on performing these tasks on Linux/macOS.
- Ensure that all code snippets and instructions are platform-agnostic where possible, or present both Windows and Linux/macOS options side by side.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation shows a Windows bias by referencing Visual Studio as the publishing tool for the API, mentioning Azure Storage Explorer (a Windows-centric tool) for managing Azure storage, and omitting any Linux/macOS-specific instructions or alternatives. There are no CLI, PowerShell, or Bash examples, but the only tooling guidance assumes a Windows environment. No Linux or cross-platform deployment or file upload methods are described.
Recommendations
- Include instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, not just Visual Studio.
- Provide alternative methods for uploading and managing files in Azure Storage, such as using the Azure CLI (az storage blob upload), AzCopy, or REST API, alongside Azure Storage Explorer.
- Explicitly mention that the steps can be performed from Linux/macOS environments and provide any necessary command-line examples.
- If referencing GUI tools like Visual Studio or Storage Explorer, also link to or describe equivalent steps using cross-platform or Linux-native tools.
- Add notes or sections for developers working on non-Windows platforms to ensure parity and inclusivity.
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 providing only PowerShell-based instructions for enabling Saviynt to delete users, explicitly stating the need for a 'Windows workstation or server' and referencing the Microsoft Graph PowerShell module. There are no equivalent instructions or examples for Linux or cross-platform environments (e.g., using Azure CLI, Bash, or REST API). This may hinder users on non-Windows systems from following the guide effectively.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI or Microsoft Graph REST API, which can be used on Linux, macOS, and Windows.
- Explicitly mention that the PowerShell module can be used on non-Windows platforms if supported, or clarify platform requirements.
- Add Linux/macOS command-line examples (e.g., Bash scripts or curl commands for REST API calls) alongside PowerShell examples.
- Rephrase steps to be platform-agnostic where possible, or present Windows and Linux instructions in parallel.
- Include a note about cross-platform compatibility and link to relevant documentation for non-Windows environments.
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 mild Windows bias, particularly in the certificate creation section, where only PowerShell is mentioned as a method for creating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) provided for certificate generation. The rest of the documentation is largely platform-agnostic, focusing on Azure portal steps and XML configuration, but the omission of Linux tooling in certificate management is notable.
Recommendations
- Add Linux and cross-platform examples for creating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
- Explicitly mention that certificate creation can be performed on any OS, and provide equivalent command-line instructions for macOS and Linux users.
- Wherever PowerShell or Windows-specific tooling is referenced, ensure a Linux alternative is also provided or linked.
- Consider including a table or section comparing certificate creation methods across Windows (PowerShell), Linux (OpenSSL), and macOS.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Visual Studio, Azure Storage Explorer) and workflows without providing Linux equivalents or alternatives. There are no command-line examples or instructions for Linux users, and the only publishing workflow mentioned is via Visual Studio, which is primarily a Windows application. The documentation also references Azure Storage Explorer, which, while cross-platform, is often associated with Windows, and does not mention alternative CLI tools or methods for Linux users.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or VS Code, including command-line examples.
- Explicitly mention and provide examples for Linux and macOS users, such as using the 'az storage' CLI for blob uploads and CORS configuration.
- When referencing tools like Visual Studio or Azure Storage Explorer, clarify their cross-platform availability or suggest alternatives (e.g., VS Code, azcopy, Azure CLI).
- Include shell (bash) command examples for common tasks like uploading files to Azure Blob Storage, setting CORS, and managing app settings.
- Ensure that all steps that can be performed via the Azure Portal are also described for CLI/automation scenarios, which are common on Linux.
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 tools (Server Manager, AD FS Management), providing only GUI-based instructions for AD FS configuration, and omitting any Linux-based or cross-platform alternatives. There are no PowerShell or command-line examples, but all setup steps assume a Windows Server environment with AD FS, and no mention is made of how to achieve similar outcomes on Linux or with non-Windows identity providers. The documentation also introduces Windows-specific concepts and tools before any platform-agnostic configuration steps.
Recommendations
- Add command-line (PowerShell and, if possible, cross-platform CLI) instructions for AD FS configuration to supplement or replace GUI steps.
- Explicitly state that AD FS is a Windows Server feature, and provide guidance or links for integrating with non-Windows OpenID Connect providers (e.g., Keycloak, IdentityServer, or cloud-based IdPs) for Linux users.
- Where possible, generalize the instructions to apply to any OpenID Connect provider, and provide a parallel example using a popular Linux-compatible IdP.
- Include a section or note for Linux administrators explaining the lack of AD FS support on Linux and suggesting alternatives for similar integration.
- Reorder or supplement examples so that platform-agnostic or Linux-friendly options are presented alongside or before Windows-specific instructions.
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 demonstrates a strong Windows bias: all administrative steps for configuring AD FS are described using Windows-only tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux or cross-platform alternatives or notes, and Windows-specific patterns are always presented first and exclusively. Troubleshooting and configuration guidance assumes a Windows environment throughout.
Recommendations
- Explicitly note that AD FS is a Windows Server technology and clarify platform requirements early in the documentation.
- Where possible, provide equivalent SAML identity provider configuration steps for common Linux-based SAML providers (e.g., Shibboleth, SimpleSAMLphp) or link to relevant guides.
- For certificate creation and management, include Linux/OpenSSL command-line examples alongside any Windows-specific instructions.
- For troubleshooting, suggest generic SAML troubleshooting tools (such as SAML-tracer browser extension, or logs from Linux SAML IdPs) in addition to Windows Event Viewer.
- If PowerShell is required, clarify that these steps are only for AD FS on Windows, and suggest alternative approaches for non-Windows environments where feasible.
- Consider adding a section or links for users who wish to integrate with non-Windows SAML providers, outlining the differences and additional considerations.
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 WPF, a Windows-only technology, and all code samples are in C# using Windows-specific APIs (e.g., WindowInteropHelper). There are no examples or mentions of Linux or cross-platform desktop application frameworks, nor any guidance for developers targeting non-Windows environments. The documentation assumes a Windows development environment and does not provide parity for Linux users.
Recommendations
- Add equivalent guidance and code samples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
- Include instructions and examples for configuring authentication in Linux desktop applications using Azure AD B2C.
- Clarify in the introduction that the guidance is specific to WPF/Windows, and provide links or references to cross-platform alternatives.
- If possible, provide MSAL usage examples in a cross-platform context (e.g., .NET Core/MAUI) that work on Linux.
- Mention any platform-specific limitations or requirements explicitly, and suggest alternatives for non-Windows developers.