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 251-275 of 392 flagged pages
Active Directory B2C
Register a Microsoft Graph application
...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While it avoids explicit Windows-only tools, the absence of Linux-friendly automation examples (e.g., Azure CLI commands, Bash scripts) and the reliance on portal navigation can be considered a 'Windows-first' bias, as the portal experience is typically more familiar to Windows users. There are no examples or guidance for Linux users or those who prefer scripting/automation over GUI steps.
Recommendations
- Add equivalent Azure CLI commands for application registration, permission assignment, and role assignment, which work cross-platform (Windows, Linux, macOS).
- Include Bash script examples for automating these tasks.
- If PowerShell examples are added, ensure Azure CLI or Bash alternatives are provided and presented equally.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and link to cross-platform tooling documentation.
- Consider reordering examples so that cross-platform command-line instructions appear before or alongside portal UI steps.
Create Pull Request
Active Directory B2C
Edit identity experience framework XML with Grit Visual Identity Experience Framework (IEF) Editor
...n/articles/active-directory-b2c/partner-grit-editor.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by omitting explicit Linux examples or instructions. The workflow and prerequisites focus on tools and patterns (such as Google Chrome and GitHub/CI/CD) that are cross-platform, but there is no mention of Linux-specific steps, considerations, or alternative tools. The language and workflow implicitly assume a Windows-centric user base, with no guidance for Linux users on file handling, deployment, or troubleshooting.
Recommendations
- Add explicit instructions or notes for Linux users, such as file download locations, permissions, and command-line alternatives for uploading/downloading policies.
- Include examples of using the Visual IEF Editor and Azure AD B2C policy deployment from Linux environments (e.g., using Bash, Linux file paths, or Linux-based CI/CD tools).
- Mention any platform-specific limitations or requirements (e.g., Chrome installation on Linux, compatibility notes).
- Provide troubleshooting steps or FAQs for common Linux issues (such as browser sandboxing, file permissions, or integration with Linux-based CI/CD pipelines).
Active Directory B2C
IDology integration with Azure Active Directory B2C
.../main/articles/active-directory-b2c/partner-idology.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions for publishing the API, without mentioning equivalent Linux workflows or cross-platform alternatives. There are no examples or guidance for deploying the API from Linux environments, nor are Linux tools or patterns referenced.
Recommendations
- Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code, which are available on Linux.
- Provide Linux-specific examples for API deployment, such as using dotnet CLI or zip deployment via Azure CLI.
- Reference documentation for configuring App Service settings via Azure CLI or portal, which is platform agnostic.
- Avoid referencing Visual Studio as the sole deployment method; mention it as one option among several.
- Add notes clarifying that all steps can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
Active Directory B2C
Twilio Verify App with Azure Active Directory B2C
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing .NET applications and configuration via web.config, which are Windows-centric technologies. There are no examples or instructions for Linux environments, such as hosting the demo app on Linux, using Linux-compatible configuration formats, or deploying with Linux tools. The guidance for hosting the application is focused on Azure App Service, without mention of Linux-based alternatives or deployment steps for Linux servers.
Recommendations
- Provide equivalent instructions for deploying the demo app on Linux-based environments (e.g., Ubuntu, CentOS), including configuration file formats and hosting options.
- Include examples for Linux command-line tools and deployment patterns, such as using environment variables or JSON/YAML config files instead of web.config.
- Offer guidance for hosting the application on Linux-based Azure App Service plans or other Linux-compatible cloud platforms.
- Mention cross-platform .NET Core/ASP.NET options and clarify compatibility with Linux.
- Add troubleshooting steps or notes relevant to Linux users, such as certificate management and file permissions.
Active Directory B2C
Troubleshoot custom policies and user flows in Azure Active Directory B2C
...lob/main/articles/active-directory-b2c/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-centric tools (such as Fiddler and Edge/Internet Explorer developer tools) and listing them before or alongside cross-platform alternatives. While most troubleshooting steps are platform-agnostic (focused on XML, VS Code, browser extensions), the mention of Fiddler and Microsoft browsers as debugging tools, and the inclusion of Edge/IE developer tools before Linux-native options, indicate a preference for Windows environments. There are no PowerShell-heavy examples or exclusive Windows command-line instructions, but Linux-specific alternatives (e.g., tcpdump, Wireshark, or Linux browser developer tools) are not mentioned.
Recommendations
- Explicitly mention Linux-compatible alternatives for network tracing, such as Wireshark, tcpdump, or browser developer tools available on Linux.
- When listing tools for SAML tracing or debugging, ensure Linux and macOS options are included and not listed after Windows-only tools.
- Clarify that Visual Studio Code and its extensions are cross-platform, and provide installation or usage notes for Linux/macOS users if relevant.
- Where possible, provide troubleshooting steps or tool recommendations that are platform-neutral, or offer parallel instructions for Linux/macOS environments.
Active Directory B2C
Configure Asignio with Azure Active Directory B2C for multifactor authentication
.../main/articles/active-directory-b2c/partner-asignio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently references the Azure portal and graphical user interface steps, which are most commonly accessed via Windows environments. There are no command-line examples (such as Azure CLI, Bash, or Powershell), nor are there instructions for Linux or cross-platform workflows. The documentation assumes use of the Azure portal and does not mention Linux-specific tools or alternatives, nor does it provide parity for Linux users who may prefer CLI or automation.
Recommendations
- Add Azure CLI and/or PowerShell command examples for all major steps, such as registering applications, configuring identity providers, and uploading policies.
- Explicitly mention that the Azure portal is accessible from any OS via browser, and clarify any steps that may differ for Linux/macOS users.
- Provide guidance for editing XML policy files using cross-platform editors (e.g., VS Code) and for uploading them via CLI (az ad b2c policy upload) if available.
- Include troubleshooting notes or links for Linux users, especially for authentication, file paths, and environment setup.
- Where possible, offer automation scripts or references for Linux environments to ensure parity with Windows-centric workflows.
Active Directory B2C
Authorization code flow - Azure Active Directory B2C
...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral in its HTTP examples and explanations. However, there is a subtle Windows bias: when suggesting tools for testing HTTP requests, only Microsoft PowerShell is mentioned, with no reference to Linux or cross-platform alternatives. This may lead Linux users to feel unsupported or unsure about equivalent tooling.
Recommendations
- Mention cross-platform tools such as curl, httpie, or wget alongside PowerShell for making HTTP requests.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (bash/curl) when demonstrating how to test HTTP requests.
- Explicitly state that any HTTP client can be used, and list popular options for different platforms.
- Ensure that future documentation does not assume the reader is using Windows or Microsoft-specific tools.
Active Directory B2C
Register a Microsoft Graph application
...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes using the Azure portal (web UI) for application registration and permission assignment, without mentioning or providing examples for command-line automation. There are no references to Linux tools, CLI commands, or cross-platform scripting methods (such as Azure CLI, Microsoft Graph CLI, or REST API calls). The absence of PowerShell-specific instructions avoids overt Windows bias, but the lack of Linux or cross-platform automation examples means Windows users (who are more likely to use the portal or PowerShell) are implicitly prioritized.
Recommendations
- Add examples using Azure CLI (az ad app create, az ad app permission add, etc.) for application registration and permission assignment.
- Include REST API or Microsoft Graph CLI examples for registering applications and granting permissions, suitable for Linux/macOS environments.
- Explicitly mention that all steps can be performed via CLI or API, and link to relevant documentation for cross-platform automation.
- Provide sample scripts for both Windows (PowerShell) and Linux/macOS (bash, curl, Azure CLI) to ensure parity.
Active Directory B2C
IDology integration with Azure Active Directory B2C
.../main/articles/active-directory-b2c/partner-idology.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides deployment instructions that reference publishing the API from Visual Studio, a Windows-centric tool, and links to Windows-focused documentation. There are no Linux or cross-platform deployment examples, nor are alternative tools or workflows mentioned for non-Windows environments.
Recommendations
- Include instructions for deploying the API using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code.
- Provide Linux-specific deployment steps or reference documentation for deploying .NET/ASP.NET apps from Linux/macOS environments.
- Mention alternative editors and deployment workflows (e.g., VS Code, command line) alongside Visual Studio.
- Ensure that links to deployment guides cover both Windows and Linux scenarios.
Active Directory B2C
Twilio Verify App with Azure Active Directory B2C
...b/main/articles/active-directory-b2c/partner-twilio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by only referencing .NET applications (typically associated with Windows environments), using web.config for configuration (a Windows/IIS convention), and providing hosting guidance specifically for Azure App Service without mentioning Linux or cross-platform alternatives. There are no examples or instructions for deploying the sample app on Linux, nor are Linux-specific configuration files or deployment patterns discussed.
Recommendations
- Provide equivalent instructions for deploying the demo app on Linux-based environments (e.g., Ubuntu, Docker, Nginx, Apache).
- Include examples using cross-platform configuration files (such as appsettings.json for .NET Core) instead of or alongside web.config.
- Offer guidance for hosting the application on Linux-based Azure App Service plans or other Linux hosting providers.
- Add PowerShell and Bash script examples for common setup tasks, or reference CLI tools that work on both platforms.
- Explicitly mention cross-platform compatibility of the sample app and clarify any Windows-specific steps.
Active Directory B2C
Trusona Authentication Cloud with Azure AD B2C
.../main/articles/active-directory-b2c/partner-trusona.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its references to Windows-specific authentication mechanisms (e.g., Windows Hello) and its lack of explicit Linux or cross-platform instructions or examples. The tutorial steps and scenario descriptions mention Windows Hello and Secure Enclave/Trusted Execution environment, but do not provide equivalent details for Linux (such as how WebAuthn works on Linux, or which Linux desktop environments and browsers are supported). There are no PowerShell commands or Windows-only tools, but the overall flow assumes familiarity with Windows-centric patterns and does not address Linux-specific considerations or troubleshooting.
Recommendations
- Include explicit examples or notes for Linux users, such as which browsers and desktop environments support WebAuthn and passkeys on Linux.
- Add troubleshooting steps or caveats for Linux environments, e.g., how to verify hardware security key support or biometric integration.
- Mention Linux equivalents to Windows Hello (such as biometric authentication via fprintd or KDE/GNOME integrations) where relevant.
- Clarify that the solution is cross-platform and provide links to external resources for configuring WebAuthn on Linux.
- Ensure screenshots and step-by-step instructions do not assume Windows-only UI or terminology.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md
...ob/main/articles/active-directory-b2c/access-tokens.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention any Linux or cross-platform alternatives (such as curl or HTTPie). No Linux-specific examples or tools are provided, and the only tool recommendation is Windows-centric.
Recommendations
- Mention cross-platform HTTP clients such as curl, HTTPie, or Postman alongside PowerShell.
- Provide example commands for Linux/macOS environments (e.g., curl command for the POST request).
- Avoid recommending only Windows tools; ensure parity by listing alternatives for other platforms.
- Consider reordering tool mentions so that cross-platform options appear before or alongside Windows-specific tools.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/authorization-code-flow.md
...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. The only mention of a specific tool for making HTTP requests is Microsoft PowerShell, which is a Windows-centric tool. No Linux or cross-platform alternatives (such as curl, httpie, or wget) are suggested. The mention of PowerShell occurs in the context of testing HTTP POST requests, and it is the only tool explicitly recommended. There are no explicit PowerShell code samples, but the tool recommendation is Windows-first and excludes Linux users.
Recommendations
- Suggest cross-platform HTTP clients such as curl, httpie, or wget alongside PowerShell when describing how to test HTTP requests.
- Add example command-line snippets for Linux/macOS users using curl or httpie for the POST requests to the /token endpoint.
- Explicitly state that any HTTP client can be used, and provide parity in tool recommendations for both Windows and Linux environments.
- Consider including a short section or note on how to perform the same actions on Linux/macOS, especially for developers who may not use PowerShell.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all steps and does not provide any command-line examples. There is no mention of Powershell, but there is also no reference to Linux CLI tools (such as Azure CLI or REST API calls) or automation scripts for Linux environments. The instructions implicitly assume a graphical workflow, which is more common on Windows, and do not address Linux-first or cross-platform automation scenarios.
Recommendations
- Add equivalent instructions using Azure CLI commands for registering applications, granting permissions, and assigning roles.
- Provide REST API examples for each major step, enabling automation from any platform.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and link to cross-platform tools.
- Include sample scripts for both Powershell and Bash to demonstrate parity.
- Clarify that the Azure portal is accessible from any OS, but offer alternatives for users who prefer command-line or automated workflows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-asignio.md
.../main/articles/active-directory-b2c/partner-asignio.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal and graphical UI workflows, which are most commonly accessed via Windows environments. There is no mention of command-line alternatives (such as Azure CLI, Bash, or PowerShell) for key steps like registering applications, configuring identity providers, or uploading policies. No Linux-specific instructions or parity examples are provided, and all steps assume use of the Azure portal web interface, which is more familiar to Windows users. There are no references to Linux tools, nor are any cross-platform command-line instructions given.
Recommendations
- Add Azure CLI and/or PowerShell command examples for all major configuration steps, such as registering applications, creating policy keys, and uploading custom policies.
- Explicitly mention that the Azure portal is accessible from any OS/browser, and provide guidance for Linux/macOS users where relevant.
- Include references to cross-platform tools (e.g., az CLI, REST API) and provide example commands for Linux environments.
- Where file editing is required (e.g., XML policy files), suggest cross-platform editors and provide instructions for common Linux workflows (e.g., using vim/nano, or VS Code on Linux).
- Ensure that any screenshots or UI references do not assume a Windows environment, or provide equivalent Linux/macOS visuals if relevant.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing .NET applications (typically Windows-centric), using web.config for configuration (a Windows/IIS convention), and providing guidance for Azure App Service hosting without mentioning Linux alternatives. There are no examples or instructions for Linux-based hosting, configuration files (e.g., appsettings.json), or cross-platform deployment. No PowerShell commands or Windows-specific tools are mentioned directly, but the overall workflow assumes a Windows development and hosting environment.
Recommendations
- Add instructions for deploying the demo app on Linux-based environments (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
- Include configuration examples using appsettings.json or environment variables, which are common in cross-platform .NET applications.
- Provide guidance for certificate creation and management on Linux (e.g., using OpenSSL).
- Clarify that the demo app and integration steps are compatible with both Windows and Linux, and highlight any platform-specific considerations.
- Offer troubleshooting tips for common Linux deployment issues (e.g., file permissions, environment variable setup).
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tutorial-create-tenant.md
...rticles/active-directory-b2c/tutorial-create-tenant.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not mention or provide examples for command-line or automation approaches, such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows users by not mentioning Linux-friendly tools like Azure CLI, which are widely used on Linux and macOS. There are no references to Linux-specific workflows, nor is there guidance for users who prefer or require non-GUI methods.
Recommendations
- Add equivalent instructions for creating and managing Azure AD B2C tenants using Azure CLI, which is cross-platform and popular among Linux users.
- Include examples for automating tenant creation and management using REST API or ARM templates, with sample commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
- Explicitly mention that the Azure portal is accessible from any OS, but provide links or references to command-line documentation for users who prefer or require non-GUI workflows.
- Ensure parity in troubleshooting and resource provider registration steps by showing how to perform these actions via Azure CLI and PowerShell, not just through the portal.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/troubleshoot.md
...lob/main/articles/active-directory-b2c/troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. While most troubleshooting guidance is platform-agnostic, tool recommendations and examples prioritize Windows-centric solutions. For SAML debugging, Edge and Internet Explorer developer tools are mentioned alongside Chrome and Firefox extensions, but no Linux-specific alternatives are suggested. Fiddler, a Windows-focused tool, is recommended for tracing, with no mention of Linux-friendly equivalents like mitmproxy or Wireshark. Visual Studio Code is recommended for XML editing and validation, which is cross-platform, but the screenshots and instructions (e.g., 'File>Preferences>Settings') follow Windows UI conventions. There are no PowerShell-specific examples, but Windows tools and patterns are referenced before Linux alternatives, which are missing.
Recommendations
- Explicitly mention Linux-compatible alternatives for network tracing (e.g., mitmproxy, Wireshark) alongside Fiddler.
- For SAML debugging, suggest platform-neutral browser extensions and clarify their availability on Linux.
- When describing Visual Studio Code usage, note that it is available on Linux and macOS, and provide instructions/screenshots for those platforms as well.
- Avoid referencing Windows-specific developer tools (e.g., Edge/IE developer tools) without mentioning cross-platform options.
- Add troubleshooting examples or workflows that demonstrate parity for Linux users, such as command-line tools or open-source alternatives.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references the Azure portal web UI for configuration steps and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). There is no mention of Linux-specific tools, nor are there any instructions or examples for performing these tasks on Linux or via cross-platform automation. The workflow assumes use of a graphical interface, which is most commonly associated with Windows environments, and does not address parity for Linux users or headless/cloud automation scenarios.
Recommendations
- Add equivalent Azure CLI and/or REST API instructions for all configuration steps, ensuring they work on Linux, macOS, and Windows.
- Explicitly mention cross-platform compatibility for all tools and commands.
- Provide example scripts for both Bash (Linux/macOS) and PowerShell (Windows), or use Azure CLI examples that work on all platforms.
- Include a note that the Azure portal is accessible from any OS, but offer alternatives for users who prefer command-line or automated approaches.
- Reference documentation for Linux users where relevant, such as installing and using the Azure CLI.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/authorization-code-flow.md
...ticles/active-directory-b2c/authorization-code-flow.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral in its HTTP request examples and explanations. However, there is a subtle Windows bias: when suggesting tools for testing HTTP requests, only Microsoft PowerShell is mentioned, with no reference to Linux-native tools (such as curl or wget). This may lead Linux users to feel unsupported or unsure about how to perform these actions on their platform.
Recommendations
- When suggesting HTTP clients for testing requests, mention cross-platform tools such as curl, wget, or httpie alongside PowerShell.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (curl, wget) when demonstrating how to send HTTP requests.
- Explicitly state that the instructions and examples are applicable on any platform, and link to documentation for popular Linux tools where appropriate.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md
...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing API protection instructions with a link that explicitly uses the 'windows' tab (secure-rest-api.md?tabs=windows), without mention of Linux or cross-platform alternatives. There are no examples or instructions for Linux, Bash, or cross-platform tooling; all references to command-line or environment setup are either generic or point to Windows-specific documentation. No PowerShell scripts or Windows-only tools are present, but the guidance does not provide parity for Linux users.
Recommendations
- Update all links to API protection or setup guides to include both Windows and Linux tabs, or use a neutral/default tab.
- Explicitly mention that the process can be performed on Linux and provide equivalent Bash or CLI examples where relevant.
- Add a note or section for Linux users, outlining any differences or confirming parity in steps and tools.
- Ensure all referenced documentation (e.g., secure-rest-api.md) is cross-platform and does not default to Windows unless necessary.
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 bias toward Windows environments by exclusively referencing Visual Studio and Visual Studio Code as development environments, without mentioning Linux-specific tools or workflows. There are no explicit Linux setup or run instructions, nor any examples of using Linux-native editors or command-line tools. The sample application and instructions are tailored to ASP.NET, which is cross-platform, but the documentation does not provide parity for Linux users in terms of environment setup or usage.
Recommendations
- Add explicit instructions for setting up and running the sample on Linux, including installation of .NET SDK on Linux distributions.
- Include examples using Linux-native editors (e.g., Vim, Emacs) or command-line workflows.
- Mention cross-platform compatibility of ASP.NET Core and clarify that the sample can be run on Linux and macOS, not just Windows.
- Provide troubleshooting tips for common Linux issues (e.g., file permissions, HTTPS certificate setup for localhost).
- List Linux prerequisites (e.g., apt-get install dotnet-sdk-6.0) alongside Windows instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on configuring Azure AD B2C authentication for Azure Web Apps but implicitly prioritizes Windows environments. It references Azure Web Apps using .NET Core (commonly associated with Windows), and all example URLs and instructions use the default Azure Web App domain (azurewebsites.net), which is more familiar to Windows users. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or deployment patterns mentioned. The instructions for configuring application settings mention the Azure portal and Azure CLI but do not provide CLI examples or clarify cross-platform usage. No mention is made of Linux-specific configuration files, deployment methods, or troubleshooting steps.
Recommendations
- Include explicit Linux examples for configuring Azure Web App authentication, such as using Linux-based runtimes or deployment methods.
- Provide Azure CLI commands for all configuration steps, ensuring they work on both Windows and Linux shells.
- Mention and demonstrate how to edit configuration files and manage secrets on Linux-based Azure Web Apps.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, environment variables).
- Clarify that the instructions apply to both Windows and Linux App Service plans, or specify any differences.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-in-azure-web-app.md
...ctory-b2c/configure-authentication-in-azure-web-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references Azure Web Apps using the default Azure domain (azurewebsites.net), which is typically associated with Windows-based hosting, and does not mention Linux-specific hosting options or provide any Linux-specific configuration guidance. There are no examples or instructions for Linux environments, nor are Linux tools or patterns referenced. All steps are described in a platform-neutral way but implicitly assume Windows defaults, and there is no parity for Linux users or explicit mention of Linux App Service plans.
Recommendations
- Explicitly mention both Windows and Linux hosting options for Azure Web Apps, including any differences in authentication configuration.
- Provide examples or notes for configuring authentication in Azure Web Apps running on Linux, including any relevant settings or troubleshooting tips.
- Reference Linux-specific documentation or tools where appropriate, such as command-line configuration using Bash or Azure CLI on Linux.
- Clarify that the instructions apply to both Windows and Linux App Service plans, or highlight any platform-specific considerations.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-python-web-app.md
...-b2c/configure-authentication-sample-python-web-app.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In the 'Run the sample web app' section, the Windows instructions are presented after Linux and macOS, but the Windows-specific command ('py' instead of 'python') is called out. Additionally, the note about path length limitations ("Extract the sample file to a folder where the total length of the path is 260 or fewer characters") is a Windows-specific constraint, but it is not explicitly labeled as such, potentially confusing Linux/macOS users for whom this limitation does not apply.
Recommendations
- Clearly label Windows-specific instructions and constraints, such as the path length limitation, and provide context for non-Windows users.
- Where possible, provide parity in examples and troubleshooting notes for Linux/macOS (e.g., mention that the path length limitation does not apply on those platforms).
- Consider listing Linux/macOS instructions first if the audience is cross-platform, or alternate the order in different sections.
- Ensure that any platform-specific commands (e.g., 'py' vs 'python') are explained, and provide guidance for users who may not have 'py' installed on Windows.