331
Pages Scanned
26
Pages Flagged
331
Changed Pages
7.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
18:40:04
Scan Information
Started At: 2026-01-06 18:40:04
Finished At: 2026-01-06 22:23:51
Status: cancelled
Target Repo: Azure
Current Phase: discovery
Files Queued: 13808
Files Completed: 331
Problematic Pages
26 issues found
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/https-cipher-tls-requirements.md
.../active-directory-b2c/https-cipher-tls-requirements.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific resources (such as Schannel cipher suites), linking to Windows-focused articles, and omitting Linux-specific guidance or examples. No Linux/OpenSSL equivalents or commands are provided for checking or configuring TLS/cipher suites.
Recommendations
- Include Linux/OpenSSL equivalents for checking and configuring TLS and cipher suites (e.g., using openssl ciphers, nmap, or testssl.sh).
- Add links to Linux-focused documentation or guides for enabling/disabling TLS versions and cipher suites.
- Provide example commands for both Windows (e.g., PowerShell) and Linux (e.g., bash/openssl) to check endpoint compatibility.
- Ensure that references to Windows tools (like Schannel) are balanced with references to common Linux libraries (like OpenSSL or GnuTLS).
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
windows_first
missing_linux_example
Summary
The documentation demonstrates a clear Windows bias, particularly in the 'How-to guide' sections. All command-line examples for generating keys and certificates use PowerShell and reference Windows-specific tools (e.g., New-SelfSignedCertificate). There are no equivalent examples for Linux or macOS environments, and Windows tooling is mentioned first and exclusively. This may hinder cross-platform adoption and usability for developers on non-Windows systems.
Recommendations
- Provide equivalent Linux/macOS command-line examples for generating symmetric keys (e.g., using OpenSSL or /dev/urandom).
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell example.
- When referencing tools or commands, mention cross-platform or OS-agnostic options first, or present them in parallel.
- Clarify in the documentation that the examples are platform-specific and provide links or guidance for other platforms.
- Consider including sample scripts or commands for common developer environments (Bash, zsh, etc.) to improve accessibility.
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-specific tools such as Server Manager, AD FS Management snap-in, Event Viewer, and PowerShell cmdlets. There are no Linux equivalents or cross-platform alternatives provided, and all examples and troubleshooting steps assume a Windows environment. Linux-based AD FS alternatives or SAML identity providers are not mentioned.
Recommendations
- Provide guidance or references for configuring SAML identity providers on Linux (e.g., Shibboleth, SimpleSAMLphp) as alternatives to AD FS.
- Include example commands or steps for managing certificates and SAML metadata using cross-platform tools (e.g., OpenSSL for certificate creation, curl/wget for metadata retrieval).
- When referencing PowerShell or Windows-specific tools, add equivalent commands or instructions for Linux environments where possible.
- Clarify at the beginning that the guide is Windows/AD FS-specific, and link to documentation for Linux-based SAML providers if full parity is not feasible.
- Add troubleshooting steps that are relevant for Linux-based SAML providers, such as checking logs or configuration files.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-microsoft-account.md
...e-directory-b2c/identity-provider-microsoft-account.md
High Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively references the Azure portal (a web UI) for all configuration steps, with no mention of command-line alternatives (such as Azure CLI, Bash, or PowerShell). There are no Linux-specific instructions, nor are any cross-platform tools or automation options (like az CLI or REST API) demonstrated. The UI navigation patterns and terminology are strongly aligned with Windows/Entra portal conventions, and there is no guidance for users working from Linux or macOS environments.
Recommendations
- Add equivalent instructions using Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
- Provide REST API examples for key configuration steps, enabling automation and parity for non-Windows environments.
- Include notes or sections clarifying that all steps can be performed from any OS via the web portal, but highlight CLI/script options for Linux users.
- If PowerShell is referenced in related docs, ensure Bash or shell script equivalents are also provided.
- Explicitly mention cross-platform compatibility and provide links to CLI tool installation guides for Linux and macOS.
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 'Revoke a consumer user's session' section, where only Windows PowerShell and Microsoft Graph PowerShell examples are provided. The instructions explicitly mention 'Windows PowerShell' and do not reference Linux or cross-platform alternatives. There are no CLI, Bash, or platform-neutral examples for session revocation or other tasks, and Windows-centric tools are mentioned before any Linux equivalents (which are absent).
Recommendations
- Provide equivalent examples using Azure CLI, Bash, or platform-neutral commands for session revocation and other tasks.
- Clarify that Microsoft Graph PowerShell is cross-platform and provide installation and usage instructions for Linux and macOS.
- Include examples using REST API calls (e.g., with curl) for tasks like session revocation to ensure platform neutrality.
- Avoid specifying 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or clarify cross-platform compatibility.
- Add a note or section highlighting how Linux and macOS users can perform these operations, including any prerequisites or differences.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-idology.md
.../main/articles/active-directory-b2c/partner-idology.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API. There are no examples or instructions for deploying the API from Linux or using cross-platform tools (e.g., VS Code, CLI). The documentation assumes use of Windows tooling and does not mention Linux alternatives or provide parity in deployment guidance.
Recommendations
- Add instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
- Include Linux-specific deployment examples (e.g., using dotnet CLI on Ubuntu, or deploying from a Linux machine).
- Reference platform-agnostic documentation for publishing web apps to Azure, rather than only Visual Studio.
- Explicitly state that the API can be deployed from any OS and provide links to relevant Linux/macOS guides.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a strong Windows bias by providing only PowerShell scripts for certificate and key generation, referencing Visual Studio for deployment, and omitting any Linux or cross-platform alternatives. No bash, OpenSSL, or cross-platform CLI examples are given, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
- Provide equivalent Linux/macOS examples for certificate creation using OpenSSL.
- Include bash or cross-platform shell commands for generating random strings.
- Mention and provide instructions for deploying the API using cross-platform tools (e.g., Azure CLI, GitHub Actions, or VS Code).
- Clearly indicate that PowerShell is Windows-specific and offer alternatives for non-Windows users.
- Add a section or callouts 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-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 critical steps (such as enabling user deletion), explicitly stating the need for a 'Windows workstation or server,' and referencing the Microsoft Graph PowerShell module without mentioning or providing alternatives for Linux or macOS users. No CLI, Bash, or cross-platform examples are given, and Windows tools and patterns are presented as the default/only option.
Recommendations
- Provide equivalent instructions using the Microsoft Graph CLI (az or mgc) or REST API with curl, which are cross-platform and work on Linux/macOS.
- Explicitly mention that the PowerShell module can be installed on Linux/macOS (if supported), and provide installation instructions for those platforms.
- Add Bash or shell script examples for key operations, or reference official Microsoft documentation for non-Windows environments.
- Avoid language that implies Windows is required (e.g., 'on a Windows workstation or server'); instead, use 'on your workstation or server' and clarify platform options.
- Ensure all critical steps have at least one cross-platform alternative to PowerShell.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-lexisnexis.md
...in/articles/active-directory-b2c/partner-lexisnexis.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio as the primary deployment tool for the API, without mentioning Linux-compatible alternatives or providing cross-platform instructions. There are no examples or guidance for Linux users (e.g., deploying via CLI, VS Code, or GitHub Actions), and the only tool explicitly mentioned for publishing code is Visual Studio, which is primarily a Windows application.
Recommendations
- Provide alternative deployment instructions using cross-platform tools such as the Azure CLI, Azure Cloud Shell, or Visual Studio Code.
- Include Linux/macOS-specific examples for deploying the API (e.g., using 'dotnet publish' and 'az webapp deploy').
- Mention Visual Studio Code as an alternative to Visual Studio for editing and deploying code, as it is available on all major platforms.
- Ensure that any screenshots or UI instructions are not Windows-specific, or provide equivalents for other operating systems.
- Explicitly state that the API and UI deployment steps can be performed from Linux, macOS, or Windows, and provide links to relevant documentation.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md
...b/main/articles/active-directory-b2c/partner-twilio.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on .NET and web.config configuration (Windows-centric technologies), referencing Azure App Service (commonly used with Windows), and omitting any Linux-specific instructions or examples. There are no Linux hosting or configuration examples, and no mention of Linux tools or deployment patterns.
Recommendations
- Add instructions for configuring and running the sample app on Linux (e.g., using .NET Core on Ubuntu, configuring appsettings.json instead of web.config).
- Provide examples for deploying the application to Linux-based hosting environments (such as Azure App Service for Linux, Docker containers, or on-premises Linux servers).
- Include guidance for certificate creation and management using Linux tools (e.g., OpenSSL commands) alongside or instead of Windows-centric instructions.
- Mention cross-platform .NET capabilities and clarify that the sample app can be run on both Windows and Linux.
- If using Azure App Service, specify both Windows and Linux hosting options and provide relevant steps for each.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-native-app-desktop.md
.../active-directory-b2c/quickstart-native-app-desktop.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows development, specifically using a WPF desktop application and Visual Studio. All examples, screenshots, and instructions are tailored for Windows, with no mention of Linux or cross-platform alternatives. There are no instructions for running the sample on Linux, nor are there references to Linux-compatible development tools or frameworks.
Recommendations
- Provide equivalent instructions and examples for Linux desktop development, such as using .NET MAUI or Avalonia for cross-platform apps.
- Include steps for running the sample application on Linux, including required dependencies and alternative IDEs (e.g., VS Code, JetBrains Rider).
- Add screenshots and walkthroughs for Linux environments.
- Mention cross-platform .NET development patterns and clarify which parts are Windows-specific.
- Offer guidance for building and debugging the sample app on Linux, including command-line instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-web-app-dotnet.md
...cles/active-directory-b2c/quickstart-web-app-dotnet.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio (a Windows-centric IDE), uses Windows-specific solution files (.sln), and provides instructions tailored to Visual Studio's GUI and workflow. There are no examples or instructions for running or debugging the sample application on Linux or macOS, nor are there mentions of cross-platform tools like Visual Studio Code, JetBrains Rider, or command-line approaches (e.g., dotnet CLI).
Recommendations
- Add instructions for running and debugging the sample application using the dotnet CLI, which is cross-platform and works on Linux and macOS.
- Include guidance for using Visual Studio Code or JetBrains Rider, both of which are available on Linux and macOS, for opening and running the solution.
- Mention prerequisites for Linux/macOS users, such as installing the .NET SDK and any required dependencies.
- Provide alternative steps for tasks currently described with Visual Studio GUI actions (e.g., configuring multiple startup projects) using launch.json or command-line equivalents.
- Explicitly state that the sample can be run on Linux/macOS and provide troubleshooting tips for those platforms.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-arm-template.md
.../articles/api-center/set-up-api-center-arm-template.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides deployment examples using Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is mentioned as a primary method, which may bias towards Windows users. References to uploading files in Azure Cloud Shell are neutral, but the lack of bash or Linux-native command examples is notable.
Recommendations
- Add explicit bash/Linux shell examples for deploying ARM templates, such as using curl/wget with az CLI.
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and consider listing CLI examples before PowerShell.
- If PowerShell is included, note that PowerShell Core is cross-platform, or provide bash equivalents for all PowerShell commands.
- Review included prerequisite content to ensure Linux and macOS environments are addressed equally.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-bicep.md
...ob/main/articles/api-center/set-up-api-center-bicep.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced in prerequisites and deployment steps. There is no mention of Linux-native shells or tools (e.g., Bash), and PowerShell is included as a primary workflow, which may bias the documentation towards Windows users.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool, since it works natively on Linux, macOS, and Windows.
- Clearly state that all Azure CLI commands work on Bash (Linux/macOS) and Windows Command Prompt/PowerShell.
- Add explicit Bash shell examples or notes for Linux/macOS users, especially for file operations (e.g., uploading Bicep files in Cloud Shell or copying files).
- If PowerShell is included, clarify that it is available cross-platform, or provide a note for Linux users on how to install and use PowerShell if desired.
- Review included prerequisite content to ensure Linux and macOS users are equally addressed, not just Windows/PowerShell users.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-notification-workflow.md
...in/articles/api-center/set-up-notification-workflow.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation exclusively uses Azure Portal (a web UI most commonly accessed from Windows environments) and Microsoft Teams for workflow automation, with no mention of Linux-native tools or alternatives. All examples and screenshots are based on the Azure Portal and Microsoft Teams, which are typically associated with Windows-centric workflows. There are no CLI, Bash, or Linux automation examples, nor are Linux notification tools (such as Slack, email, or open-source equivalents) referenced. The only alternative workflow tool mentioned is Power Automate, another Microsoft/Windows-centric solution.
Recommendations
- Add examples using Azure CLI and Bash scripts to configure API Center, Logic Apps, and event subscriptions, making the workflow accessible from Linux environments.
- Include automation and notification examples using open-source or cross-platform tools (e.g., Slack, email via SendGrid, or other webhook-compatible services) alongside Microsoft Teams.
- Provide instructions for configuring workflows via REST API calls, which can be executed from any OS, not just via the Azure Portal.
- Mention and demonstrate how Linux users can perform equivalent tasks without relying on Windows-specific tools or GUIs.
- Reference PowerShell only as one option, and provide parity with Bash or other Linux shell scripting examples.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md
...2c/configure-authentication-sample-web-app-with-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by primarily referencing Visual Studio and Visual Studio Code as development environments, with no explicit mention of Linux or macOS alternatives for building and running the sample. There are no terminal or command-line examples for Linux (e.g., using dotnet CLI), and the instructions assume a GUI-based workflow typical of Windows users. While Visual Studio Code is cross-platform, the lack of explicit Linux/macOS instructions or screenshots, and the absence of Linux-specific troubleshooting or environment setup, means Linux parity is not achieved.
Recommendations
- Add explicit instructions and examples for Linux users, such as using the dotnet CLI to build and run the sample projects (e.g., 'dotnet build', 'dotnet run').
- Include a section or tab for Linux/macOS setup, covering prerequisites like installing .NET SDK on Linux, and using editors like VS Code or JetBrains Rider.
- Provide Linux/macOS-specific screenshots or notes where file paths, environment variables, or UI elements differ.
- Mention and link to official .NET installation guides for Linux and macOS.
- Clarify that Visual Studio Code is cross-platform and supported on Linux/macOS, and ensure all steps are validated on those platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-web-app.md
...rectory-b2c/configure-authentication-sample-web-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio and Visual Studio Code as development environments, with no mention of Linux-specific tools or workflows. The instructions and prerequisites focus on Windows-centric IDEs and do not provide guidance for Linux users, such as using command-line .NET tools or alternative editors. There are no explicit Linux examples or deployment instructions, and the sample application is ASP.NET-based, which is traditionally Windows-focused, though .NET Core is cross-platform.
Recommendations
- Add explicit instructions for Linux users, including installation of .NET SDK on Linux distributions and use of command-line tools (dotnet CLI) for building and running the sample.
- Include examples of opening and running the project using Linux-friendly editors (e.g., Vim, Emacs, JetBrains Rider) or just the terminal.
- Provide troubleshooting tips for common Linux issues, such as HTTPS certificate setup for localhost development.
- Clarify that the sample can be run on Linux and macOS, and provide any necessary configuration differences.
- Mention deployment options for Linux servers (e.g., using Nginx/Apache as reverse proxies for ASP.NET Core apps).
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md
...ctory-b2c/custom-policies-series-sign-up-or-sign-in.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation requires Visual Studio Code (VS Code) as a prerequisite, but does not specify that it is cross-platform or mention any Linux-specific setup or alternatives. There are no command-line examples, but all tool references (e.g., VS Code, Azure Portal) are platform-agnostic except for the implicit assumption that VS Code is installed, which may be interpreted as a Windows-centric tool by some users. No explicit Linux or macOS instructions or screenshots are provided, and no mention is made of Linux-specific considerations.
Recommendations
- Clarify that Visual Studio Code is available on Windows, Linux, and macOS, and provide installation links for all platforms.
- Explicitly mention that all steps can be performed on Linux and macOS, not just Windows.
- If any command-line steps are added in the future, provide both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Include a note or section addressing any platform-specific differences, even if minimal, to assure Linux users of parity.
- Consider providing screenshots or terminal snippets from Linux environments where relevant.
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
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is exclusively focused on WPF desktop applications, which are Windows-only. All code samples are in C# and tailored for WPF, with no mention of Linux or cross-platform desktop frameworks. There are no examples or guidance for Linux desktop applications or alternative frameworks (e.g., GTK#, Avalonia, Electron). The documentation assumes a Windows development environment and does not address Linux parity.
Recommendations
- Add equivalent examples for cross-platform desktop frameworks (e.g., Avalonia, Electron, GTK#) that run on Linux.
- Include guidance for configuring Azure AD B2C authentication in Linux desktop applications.
- Mention and provide code samples for MSAL usage in .NET Core/MAUI apps that can run on Linux.
- Clarify in the introduction that the guidance is Windows-specific, and link to cross-platform alternatives if available.
- If possible, provide parity in documentation for Linux and macOS desktop environments, including redirect URI configuration and authentication flows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api.md
...irectory-b2c/enable-authentication-web-app-with-api.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily focused on ASP.NET web applications and development workflows typical of Windows environments. All code and tooling examples assume .NET Core usage, but the only IDEs mentioned are Visual Studio and Visual Studio Code, with package installation commands given for both. However, the Visual Studio Code example uses Install-Package, which is a PowerShell/NuGet CLI command not natively available on Linux/macOS terminals. There is no explicit mention of Linux or macOS development environments, nor are there instructions for running the app outside of Windows (e.g., using bash, configuring HTTPS certificates on Linux, or using cross-platform .NET CLI commands for package management). The documentation does not mention Linux-specific considerations, such as file paths, shell commands, or troubleshooting steps for non-Windows platforms.
Recommendations
- Add explicit instructions and examples for Linux/macOS environments, including using bash/zsh shells and .NET CLI commands for package installation and running the app.
- Clarify that Visual Studio Code is cross-platform and provide package installation commands using 'dotnet add package' for all platforms, rather than 'Install-Package' which is PowerShell-specific.
- Include notes on file path differences (e.g., '/' vs '\') and HTTPS certificate setup for Linux/macOS.
- Mention any platform-specific prerequisites or troubleshooting steps for running ASP.NET Core apps on Linux/macOS.
- Ensure parity in documentation by listing Linux/macOS instructions alongside Windows, rather than only referencing Windows tools and patterns.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-application.md
...directory-b2c/enable-authentication-web-application.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on ASP.NET web applications, which are traditionally associated with Windows development. The instructions and examples assume the use of Visual Studio and Visual Studio Code, both of which are more commonly used on Windows. There is no mention of Linux-specific development environments, nor are there any examples or guidance for running the application on Linux (e.g., using the dotnet CLI on Linux, configuring for nginx or Apache, or troubleshooting Linux-specific issues). Package installation examples use dotnet CLI and Install-Package, but do not clarify cross-platform usage or provide parity for Linux users.
Recommendations
- Add explicit instructions for setting up and running the ASP.NET Core app on Linux (e.g., Ubuntu), including prerequisites like installing the .NET SDK on Linux.
- Include examples of using the dotnet CLI on Linux terminals (bash/zsh), and clarify that the dotnet commands work cross-platform.
- Mention alternative editors such as JetBrains Rider or simply using VS Code on Linux, and provide guidance for Linux users.
- Provide troubleshooting tips or notes for common Linux-specific issues (e.g., file permissions, HTTPS certificate setup for localhost).
- Clarify that ASP.NET Core is cross-platform and can be developed and hosted on Linux, macOS, and Windows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-web-app-with-api-options.md
...-b2c/enable-authentication-web-app-with-api-options.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively provides examples and instructions for ASP.NET Core applications, which are traditionally associated with Windows environments. There are no platform-specific instructions, but the use of .NET, C#, and references to files like Startup.cs and appsettings.json implicitly target Windows developers. There are no Linux-specific examples, nor any mention of cross-platform considerations (such as running on Linux, using bash, or deploying on non-Windows environments).
Recommendations
- Explicitly state that ASP.NET Core is cross-platform and can run on Linux, macOS, and Windows.
- Include instructions or examples for deploying and configuring the application on Linux (e.g., using systemd, configuring environment variables in bash, file paths).
- Mention any platform-specific considerations for file locations, permissions, or dependencies.
- Provide sample commands for both Windows (PowerShell/Command Prompt) and Linux (bash) where relevant, such as for environment setup or running the application.
- Reference Linux-friendly tools and workflows (e.g., using Visual Studio Code, dotnet CLI on Linux, Docker containers) alongside Windows equivalents.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant.md
...rectory-b2c/identity-provider-azure-ad-multi-tenant.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively references the Azure portal (web UI) for all configuration steps and does not provide any command-line examples (e.g., Azure CLI, PowerShell, or Bash). Where browser instructions are given, only Microsoft browsers (Edge, Chrome) are mentioned. There is no mention of Linux-specific tools, nor are there any examples or guidance for users working from Linux environments. The documentation assumes a GUI-first, Windows-centric workflow.
Recommendations
- Add Azure CLI examples for app registration, policy key creation, and claims provider configuration, alongside or in place of portal UI steps.
- Mention cross-platform browsers (e.g., Firefox) when suggesting private browsing for testing.
- Explicitly state that all steps can be performed from any OS (Windows, Linux, macOS) via the Azure portal, and clarify any OS-specific limitations if present.
- Provide sample scripts or commands for Linux users to automate or perform the same tasks described in the portal.
- If PowerShell is referenced in related content, ensure Azure CLI or Bash equivalents are provided.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-grit-iam.md
...main/articles/active-directory-b2c/partner-grit-iam.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation focuses exclusively on Azure AD B2C and Grit IAM integration, referencing Azure-specific tools and portals (which are primarily accessed via web interfaces or Microsoft-centric environments). There are no command-line examples, but all infrastructure and configuration guidance assumes use of Azure (a Microsoft platform), with no mention of Linux-specific workflows, tools, or alternative environments. There is no reference to Powershell, but the absence of Linux CLI, shell, or open-source tool examples constitutes a subtle Windows bias.
Recommendations
- Include examples or guidance for Linux users, such as using Azure CLI on Linux, or accessing Grit IAM via Linux-based environments.
- Mention cross-platform compatibility for portals and APIs, clarifying if they can be accessed from Linux or macOS systems.
- Provide sample scripts or automation steps using bash or other Linux-native tools, where relevant.
- Explicitly state any platform requirements or limitations, and offer alternatives for non-Windows users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/solution-articles.md
...ain/articles/active-directory-b2c/solution-articles.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by primarily referencing ASP.NET Core applications (which are historically Windows-centric, though now cross-platform) and omitting explicit examples or guidance for Linux environments. There are no mentions of Linux tools, shell commands, or Linux-specific development patterns. The training and solution guides do not clarify platform parity or provide Linux-focused instructions, potentially leaving Linux developers underserved.
Recommendations
- Include explicit examples for both Windows and Linux environments when demonstrating Azure AD B2C integration, such as showing configuration steps using Bash or Linux-native tools.
- Add references to Linux-compatible development stacks (e.g., Node.js, Python, Java) alongside ASP.NET Core.
- Clarify that Azure AD B2C can be used from Linux and provide links to cross-platform SDKs and documentation.
- Ensure downloadable guides and training materials mention platform-agnostic approaches or provide separate sections for Windows and Linux users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-web-application-firewall.md
...tive-directory-b2c/partner-web-application-firewall.md
Low Priority
View Details â
Detected Bias Types
missing_linux_example
Summary
The documentation exclusively uses the Azure Portal (web UI) for configuration steps and does not provide any command-line examples. There are no PowerShell or Windows-specific tools mentioned, but there is also a lack of parity for Linux users: no Azure CLI (cross-platform) or Bash examples are given. This omission can disadvantage users who prefer or require CLI-based automation, especially on Linux or macOS.
Recommendations
- Add Azure CLI examples for all major configuration steps (e.g., creating a WAF policy, associating it with a Front Door profile, enabling logging).
- Where possible, provide both Portal (UI) and CLI instructions side-by-side.
- Explicitly mention that the Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
- If scripting is required, provide Bash script snippets in addition to any PowerShell or Windows batch examples.
- Link to Azure CLI documentation for relevant commands (e.g., `az network front-door waf-policy`).