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 151-175 of 392 flagged pages
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 (a Windows-centric IDE), .sln solution files, and Web.config XML configuration, all of which are typical of Windows/.NET development. There are no instructions or examples for Linux-based development environments, editors, or deployment scenarios. No mention is made of cross-platform .NET Core/ASP.NET Core, nor are there any Linux command-line or editor alternatives provided.
Recommendations
- Include instructions for opening and editing the project using cross-platform editors such as VS Code or JetBrains Rider, and clarify that .NET projects can be developed on Linux and macOS as well as Windows.
- Provide examples for updating configuration using appsettings.json (used in .NET Core/ASP.NET Core) in addition to Web.config, or clarify the applicability to .NET Framework vs .NET Core.
- Offer command-line instructions using the dotnet CLI (e.g., 'dotnet build', 'dotnet run') for building and running the sample, rather than assuming Visual Studio usage.
- Explicitly mention that the sample and approach are applicable to Linux and macOS environments, and provide any necessary caveats or adjustments.
- If any steps are specific to Windows (such as using Visual Studio), provide equivalent steps for Linux (e.g., using VS Code, nano, or vim to edit files).
Create Pull Request
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
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page primarily uses generic command shell instructions for most steps, but in the final 'Run your SPA application' section, it provides a PowerShell-specific command example (npm ./index.js), which is not valid on Linux/macOS shells. There are no explicit Linux/macOS instructions or clarifications, and no mention of platform differences, leading to a subtle Windows/PowerShell bias.
Recommendations
- Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples, especially for running Node.js applications (e.g., 'node index.js' instead of 'npm ./index.js').
- Clarify that the instructions are cross-platform and specify any platform-specific differences where relevant.
- Avoid using PowerShell-specific syntax unless necessary, or always accompany it with the equivalent bash command.
- Explicitly mention that the steps work on Windows, Linux, and macOS, and provide troubleshooting tips for each platform if needed.
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section on revoking a consumer user's session. It exclusively provides instructions and examples for using Microsoft Graph PowerShell in 'Windows PowerShell', without mentioning cross-platform alternatives or providing equivalent Linux/macOS command-line guidance. The use of 'Windows PowerShell' and lack of Bash/CLI/Cloud Shell examples may hinder Linux and macOS users.
Recommendations
- Clarify that Microsoft Graph PowerShell is cross-platform and can be used in PowerShell Core on Linux and macOS, not just 'Windows PowerShell'.
- Provide explicit instructions and examples for running Microsoft Graph PowerShell on Linux/macOS (e.g., using pwsh).
- Offer alternative examples using Azure CLI or direct Microsoft Graph API calls with curl or httpie, which are platform-agnostic.
- Avoid language that implies Windows is required (e.g., 'In your Windows PowerShell'), and instead use neutral phrasing such as 'In your terminal' or 'In PowerShell'.
- Add a note or section for Linux/macOS users, highlighting any platform-specific considerations or prerequisites.
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 patterns (such as ASP.NET MVC, OWIN middleware, and .NET code samples) without providing equivalent Linux or cross-platform alternatives. Certificate management and application examples are oriented toward Windows environments, and there is a lack of explicit Linux-based instructions or examples for key steps such as application development, certificate creation, and configuration.
Recommendations
- Provide Linux-based examples for certificate creation and management (e.g., using OpenSSL commands) alongside or instead of Windows-centric instructions.
- Include sample applications and code snippets that use cross-platform frameworks (such as Node.js, Python Flask/Django, or Java Spring) in addition to or instead of ASP.NET MVC/OWIN.
- Reference Linux-compatible tools and workflows for application deployment and configuration, such as using Docker containers, shell scripts, or Linux-native editors.
- Ensure that all steps (especially those involving file manipulation, certificate handling, and application configuration) have clear instructions for both Windows and Linux users.
- Where possible, use platform-agnostic language and avoid assuming the reader is using Windows.
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 Windows-centric, focusing exclusively on a WPF (Windows Presentation Foundation) desktop application and requiring Visual Studio 2019, which is only available on Windows. There are no instructions, examples, or mentions of Linux or cross-platform alternatives for building or running the sample application. The tooling and workflow described (Visual Studio, WPF, F5 debugging) are all Windows-specific, and there is no guidance for Linux users.
Recommendations
- Provide equivalent instructions for Linux users, such as using .NET Core cross-platform desktop frameworks (e.g., Avalonia or MAUI) if possible.
- Include examples for building and running the sample application using the .NET CLI, which is available on Linux and macOS.
- Mention and link to cross-platform IDEs or editors (e.g., VS Code, JetBrains Rider) and provide steps for using them.
- If the sample is inherently Windows-only (WPF), clearly state this limitation at the top and suggest alternatives or similar samples for Linux users.
- Consider providing a cross-platform sample application alongside the WPF sample to ensure parity for non-Windows developers.
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 requiring installation of the Microsoft Graph PowerShell module on a Windows workstation or server. There are no equivalent instructions or examples for Linux or cross-platform environments, and no mention of alternative tools (such as Azure CLI or Microsoft Graph CLI) that are available on Linux and macOS. This may limit accessibility for users operating in non-Windows environments.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI or Microsoft Graph CLI, which are supported on Linux and macOS.
- Explicitly state that the PowerShell module can be used on PowerShell Core, which is available on Linux and macOS, if applicable.
- Include Linux/macOS-specific setup steps or command-line examples where relevant.
- Avoid language that restricts steps to 'Windows workstation or server' unless strictly necessary; instead, use 'workstation' or 'machine' and clarify OS compatibility.
- Add a note or table summarizing tool availability and compatibility across 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 demonstrates a Windows bias by referencing Visual Studio (a primarily Windows tool) as the publishing method for the API, without mentioning cross-platform alternatives or providing Linux/macOS deployment instructions. There are no examples or guidance for deploying the API from non-Windows environments, and the only linked deployment instructions are for Visual Studio. This may hinder Linux or macOS users from following the tutorial seamlessly.
Recommendations
- Include alternative deployment instructions for the API using cross-platform tools such as the Azure CLI, GitHub Actions, or command-line dotnet publish and az webapp deploy commands.
- Provide explicit Linux/macOS deployment steps or reference documentation that covers these platforms.
- When referencing tools like Visual Studio, also mention Visual Studio Code and/or command-line methods that work on all major operating systems.
- Ensure that all steps that involve tooling or commands have parity between Windows and Linux/macOS 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 exclusively providing PowerShell scripts for critical steps such as creating self-signed certificates and generating random keys, without offering equivalent Linux/macOS commands or guidance. The use of PowerShell and references to Visual Studio (a Windows-centric tool) further reinforce this bias, making it less accessible for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Bash/OpenSSL commands for creating self-signed certificates and generating random strings, ensuring Linux and macOS users can follow the tutorial.
- Include explicit notes or sections for cross-platform compatibility, clarifying how each step can be performed on Windows, Linux, and macOS.
- Mention and demonstrate the use of cross-platform tools (such as VS Code, Azure CLI, or OpenSSL) alongside Windows-specific tools like PowerShell and Visual Studio.
- Where PowerShell is used, offer alternative scripts or command-line instructions for Bash/zsh.
- Review all steps for hidden Windows assumptions (e.g., file paths, certificate stores) and document Linux/macOS equivalents.
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 to monitor directory quota usage, with no equivalent example for Linux or cross-platform shells. The script uses Windows-specific cmdlets (Invoke-RestMethod, New-Object), and there is no mention of alternatives (such as Bash with curl or Python). This presents a clear Windows/Powershell bias and may hinder Linux or macOS users.
Recommendations
- Provide a Bash (curl) or Python example for Linux/macOS users to call the Microsoft Graph API and retrieve the directory quota.
- Explicitly mention that the PowerShell script is for Windows, and offer equivalent instructions for other platforms.
- Use cross-platform tools or note any platform-specific requirements.
- Consider using the Microsoft Graph CLI or Azure CLI, which are cross-platform, as alternative examples.
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 a PowerShell example for configuring password expiry duration using the Microsoft Graph PowerShell module, but does not offer equivalent command-line examples for Linux/macOS users (e.g., using Azure CLI, Bash, or REST with curl). The documentation also references PowerShell cmdlets and modules without mentioning cross-platform alternatives, which may disadvantage users on non-Windows systems.
Recommendations
- Provide equivalent examples using Azure CLI or direct REST API calls with curl, which are cross-platform and accessible to Linux/macOS users.
- Explicitly mention that the Microsoft Graph PowerShell module is available cross-platform (if true), or clarify any OS limitations.
- Where PowerShell is used, add a parallel example using Bash/curl for REST API operations.
- Review all step-by-step instructions to ensure they do not assume use of Windows-specific tools or interfaces.
- Add a note or section on how to perform these tasks from Linux/macOS environments, including installation instructions for any required tools.
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 some Windows bias, particularly in the instructions for generating GUIDs (recommending PowerShell's 'new-guid' command first) and in scripting examples (PowerShell script is presented before cURL). Windows/PowerShell tools and patterns are mentioned or shown before their Linux/Unix equivalents, and there is no explicit mention of Linux-native methods for certain tasks.
Recommendations
- When instructing users to generate a GUID, provide both PowerShell (Windows) and Linux/macOS (e.g., 'uuidgen' command) options side by side.
- Present scripting examples (PowerShell and cURL) in parallel or clarify that cURL is cross-platform and may be preferred on Linux/macOS.
- Avoid listing Windows/PowerShell tools or commands before cross-platform or Linux-native equivalents; instead, present them together or in a platform-neutral order.
- Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary command-line alternatives.
- Consider including bash or shell script examples for common automation tasks, not just PowerShell.
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 towards Windows 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 (such as curl or HTTPie). The documentation does not mention or show how to perform the same steps on non-Windows platforms, and Windows tools are referenced before any cross-platform alternatives.
Recommendations
- Provide equivalent Linux/macOS command-line examples using curl or HTTPie for testing the REST API.
- When referencing PowerShell, clarify that it is available cross-platform, or provide both Windows (PowerShell) and Linux/macOS (bash/curl) examples side by side.
- Mention and demonstrate the use of cross-platform tools (e.g., curl, wget, HTTPie) for making HTTP requests.
- Avoid referencing Microsoft-specific tools exclusively or first; instead, present cross-platform options or alternate between platforms in examples.
- Add a note that all steps can be performed on Linux/macOS, and specify any platform-specific considerations.
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 using WPF and Visual Studio. It assumes the use of Windows-only technologies and tools, such as WPF, Visual Studio, and .NET desktop development, without mentioning or providing alternatives for Linux or cross-platform scenarios. There are no instructions or examples for Linux users, nor any mention of equivalent Linux tools or frameworks.
Recommendations
- Add a section or note clarifying that WPF is Windows-only, and suggest cross-platform alternatives (e.g., Avalonia, MAUI) for Linux or macOS users.
- Provide guidance or links for setting up and running the sample on Linux using cross-platform .NET and compatible UI frameworks.
- Include instructions for using cross-platform IDEs (e.g., VS Code, JetBrains Rider) and command-line tools (e.g., dotnet CLI) instead of only Visual Studio.
- Explicitly state the platform limitations and, where possible, provide parity examples or references for Linux environments.
- Consider providing a separate Linux-focused sample or documentation page for desktop authentication with Azure AD B2C.
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 or examples of Bash, shell, or cross-platform scripting alternatives. All automation and pipeline steps assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS. The instructions and examples are Windows-centric, potentially excluding or confusing users working in non-Windows environments.
Recommendations
- Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
- Explicitly mention that PowerShell Core (pwsh) is cross-platform and provide instructions for using it on Linux/macOS, or clarify if Windows PowerShell is required.
- Add a section or notes on how to adapt the deployment process for Linux-based Azure Pipeline agents, including any prerequisites or differences.
- Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API calls via curl) in examples, or at least mention them as alternatives.
- Ensure that all steps, including script creation and pipeline task configuration, include Linux/macOS-compatible instructions and screenshots where relevant.
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 demonstrates a Windows bias by exclusively referencing Windows tools (e.g., Server Manager, AD FS Management), using only GUI-based instructions specific to Windows Server, and omitting any Linux or cross-platform alternatives for AD FS setup or management. There are no PowerShell or command-line examples, but all setup steps assume a Windows Server environment and do not mention or provide guidance for Linux-based AD FS alternatives or management approaches.
Recommendations
- Provide equivalent command-line (PowerShell and, where possible, cross-platform CLI) instructions for AD FS configuration, so that users can automate or script the process.
- Acknowledge that AD FS is a Windows Server technology, but mention and link to any open source or cross-platform alternatives for federated identity (e.g., Keycloak, IdentityServer) and how they could be integrated with Azure AD B2C.
- If possible, include a note or section for Linux users, clarifying that AD FS is not available on Linux, and suggest supported alternatives for similar scenarios.
- Where GUI steps are described, offer PowerShell or REST API equivalents to improve automation and accessibility for non-Windows environments.
- Reorder or supplement instructions to clarify platform dependencies early in the prerequisites section.
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 page demonstrates a bias toward Windows environments by providing only PowerShell examples for scripting and automation, referencing the Microsoft Graph PowerShell module exclusively, and omitting equivalent Linux or cross-platform command-line instructions. There are no CLI, Bash, or REST API examples tailored for Linux users, and no mention of how to perform these tasks outside of the Azure portal or PowerShell context.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users, especially for tasks currently demonstrated with PowerShell.
- Include REST API examples with curl commands to show how to interact with Microsoft Graph from any platform.
- Mention cross-platform tools (such as Azure CLI or Microsoft Graph CLI) alongside PowerShell, and clarify that PowerShell Core is available cross-platform if relevant.
- Reorder sections or add notes to ensure Linux/macOS options are presented equally and not as an afterthought.
- Explicitly state when a step or tool is Windows-specific, and offer alternatives for other operating systems.
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 by exclusively referencing Windows tools (Server Manager, AD FS Management snap-in, Event Viewer), providing only PowerShell command examples for configuration, and omitting any mention of Linux or cross-platform alternatives for AD FS management or troubleshooting. All step-by-step instructions assume a Windows environment, with no guidance for Linux administrators.
Recommendations
- Provide equivalent instructions or notes for environments where AD FS is accessed remotely or managed via non-Windows systems (e.g., via REST APIs, if available, or using cross-platform tools).
- Include references to any available cross-platform AD FS management tools or clarify that AD FS is a Windows-only technology, but highlight how Linux administrators can interact with it (e.g., via browser-based management, remote PowerShell from Linux, or REST endpoints).
- Where PowerShell is used, mention if and how PowerShell Core (pwsh) on Linux/macOS can be used, or provide alternative command-line examples if possible.
- For certificate creation and management, include Linux-based commands (e.g., using OpenSSL) alongside Windows-centric instructions.
- Explicitly state the Windows-only nature of certain steps, and provide guidance for mixed-environment teams (e.g., how a Linux admin can coordinate with a Windows admin for AD FS configuration).
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 by presenting command-line instructions and examples in a way that implicitly assumes a Windows environment. Specifically, the use of 'powershell' syntax in the 'Run your SPA application' step, and the lack of explicit Linux/macOS terminal instructions or parity, may disadvantage non-Windows users. There are no references to Windows-specific tools, but the command shell instructions and examples are not cross-platform neutral.
Recommendations
- Provide explicit Linux/macOS equivalents for all command-line instructions, especially for running Node.js applications (e.g., 'node index.js' instead of 'npm ./index.js').
- Use cross-platform neutral terminology such as 'terminal' or 'command line' instead of 'command shell', and avoid referencing 'powershell' unless necessary.
- Where code blocks are labeled as 'powershell', ensure that equivalent 'bash' or 'sh' code blocks are also provided, or use unlabeled code blocks for commands that are identical across platforms.
- Add a note or section clarifying that the instructions apply to Windows, Linux, and macOS, and highlight any platform-specific differences.
- Consider including a table or sidebar with common command-line differences for Windows vs. Linux/macOS for Node.js app development.
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 (a Windows-only web server) as the example application for testing, and providing a link to IIS setup instructions. There are no equivalent examples or guidance for Linux-based web applications or servers (such as Apache or Nginx). The documentation does not mention or provide steps for Linux environments, nor does it reference Linux tools or patterns, which may limit accessibility for users deploying on non-Windows platforms.
Recommendations
- Provide parallel examples for Linux-based web applications (e.g., Apache, Nginx) alongside IIS.
- Include setup instructions or references for deploying and testing with a Linux web server.
- Mention Linux as a supported environment where applicable, and clarify any platform-specific steps.
- Ensure that all prerequisite and configuration steps are platform-agnostic or have clear alternatives for both Windows and Linux users.
- Reference Linux tools and commands where relevant, not just Windows-specific technologies.
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 page demonstrates a moderate Windows bias, primarily in the section on creating self-signed certificates, where only a PowerShell-based approach is referenced (via an include), and no Linux/macOS alternatives (such as OpenSSL) are mentioned. The rest of the documentation is largely platform-neutral, focusing on Azure Portal UI and XML configuration, but the lack of cross-platform command-line examples for certificate creation may disadvantage Linux/macOS users.
Recommendations
- Add explicit instructions or examples for creating self-signed certificates on Linux/macOS using OpenSSL, alongside the existing PowerShell/Windows approach.
- Wherever PowerShell or Windows-specific tools are referenced, provide equivalent bash/OpenSSL or cross-platform alternatives.
- In sections that reference uploading or generating certificates, clarify that certificates can be created on any OS and provide links or steps for common Linux/macOS workflows.
- Review all included snippets (such as the referenced PowerShell module include) to ensure Linux parity or add a note directing users to alternative methods if only Windows is covered.
- Consider a short table or callout summarizing certificate creation options for Windows (PowerShell), Linux (OpenSSL), and macOS (OpenSSL/Keychain), with links to official documentation.
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, particularly in the 'How-to guide' sections for generating cryptographic keys and certificates. All code examples for key and certificate generation use PowerShell and reference Windows-specific tools (e.g., New-SelfSignedCertificate). There are no equivalent examples or instructions for performing these tasks on Linux or macOS, and Windows tooling is mentioned exclusively and first. This may hinder Linux/macOS users from following the guide without additional research.
Recommendations
- Provide equivalent command-line examples for Linux (e.g., using openssl for key and certificate generation).
- Explicitly mention cross-platform alternatives (e.g., bash scripts, openssl, or other widely available tools) alongside PowerShell/Windows examples.
- Structure instructions so that Windows and Linux/macOS approaches are presented in parallel, or at least mention non-Windows options before or alongside Windows-specific tools.
- Link to external resources or official documentation for Linux/macOS users on generating keys and certificates.
- Clarify in each step if a tool or command is Windows-specific, and suggest alternatives where possible.
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
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell script for programmatic access to audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash/cURL or Python). The script assumes use of PowerShell and Windows-centric tooling, and the Azure Cloud Shell reference implicitly favors PowerShell. There is no mention of Linux-native tools or cross-platform scripting approaches, nor are Linux examples provided alongside the Windows/PowerShell example.
Recommendations
- Provide a Bash/cURL example for accessing the Microsoft Graph API to retrieve audit logs, suitable for Linux and macOS users.
- Include a Python script example, which is cross-platform and widely used for automation.
- Explicitly mention that the API can be accessed from any OS, and link to relevant SDKs or CLI tools (e.g., Microsoft Graph CLI, Azure CLI) that work on Linux.
- When presenting scripts, offer both Windows (PowerShell) and Linux (Bash/cURL or Python) versions side by side.
- Avoid language that implies PowerShell is the only or primary way to automate these tasks.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell scripts for testing the REST API, mentioning Microsoft PowerShell as the example HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). Additionally, the documentation references Windows-centric tools (PowerShell) without mentioning or prioritizing cross-platform or Linux-native alternatives.
Recommendations
- Provide equivalent Linux/macOS examples using common tools such as curl or httpie alongside PowerShell scripts.
- When referencing PowerShell, clarify that it is available cross-platform, or provide Bash/zsh alternatives.
- List cross-platform or Linux-native tools (curl, wget, httpie) before or alongside Windows tools in all example sections.
- Explicitly mention that all steps can be performed on Linux/macOS, and note any OS-specific differences.
- Consider including screenshots or terminal output from both Windows and Linux environments to reinforce 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, specifically targeting WPF (Windows Presentation Foundation) desktop applications and requiring Visual Studio 2019. There are no examples or guidance for developing or running equivalent applications on Linux or macOS, nor are cross-platform .NET or authentication approaches discussed. All tooling and code samples assume a Windows environment.
Recommendations
- Provide equivalent instructions and code samples for cross-platform .NET desktop applications (e.g., using .NET MAUI or Avalonia UI) that can run on Linux and macOS.
- Include guidance for setting up the development environment and running the sample on Linux (e.g., using VS Code, JetBrains Rider, or the .NET CLI).
- Mention and demonstrate how to use the Microsoft Authentication Library (MSAL) in a cross-platform context.
- Clarify which steps are Windows-specific and offer alternatives or notes for non-Windows users.
- If WPF is required, explicitly state that the sample is Windows-only and link to cross-platform alternatives where possible.
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 demonstrates a mild Windows bias by providing command-line instructions and examples that implicitly or explicitly target Windows users. The only explicit shell example for running the application is labeled as 'powershell', and there is no mention of Linux or macOS-specific shell commands, nor any guidance for non-Windows environments. There are no references to Windows-only tools, but the use of 'powershell' and lack of Linux parity in command-line instructions may confuse or exclude Linux/macOS users.
Recommendations
- Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/sh) command examples for all shell instructions, especially for installing dependencies and running the app.
- Use neutral shell syntax (e.g., $ npm install, $ node index.js) or provide tabs for different OSes.
- Avoid labeling generic npm or node commands as 'powershell' unless there are actual PowerShell-specific commands.
- Explicitly state that the instructions work on Windows, Linux, and macOS, and mention any OS-specific considerations if applicable.
- Add a note or section for Linux/macOS users, clarifying any differences (such as using 'node index.js' instead of 'npm ./index.js', which is not standard npm usage).