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 101-125 of 392 flagged pages
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 →
Scanned: 2025-09-12 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash/cURL or Python). PowerShell is primarily associated with Windows, and while it is available on Linux, it is not the default or most common scripting environment for Linux users. No mention is made of alternative tools or approaches more familiar to Linux administrators.
Recommendations
  • Add a Bash/cURL example for querying the Microsoft Graph API to retrieve audit logs, demonstrating how to authenticate and download logs using common Linux tools.
  • Provide a Python script example, as Python is widely used and cross-platform.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation instructions or a note for non-Windows users.
  • Reorder or supplement the scripting section to present both Windows (PowerShell) and Linux (Bash/cURL or Python) options, or present a cross-platform solution first.
  • Reference CLI tools (such as Azure CLI or Microsoft Graph CLI) if available, and provide examples for those as well.
GitHub Create Pull Request
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 →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: certificate generation and upload steps link to Windows-specific instructions, and there are no Linux or cross-platform alternatives provided for these steps. Application code samples and configuration focus on ASP.NET MVC (a Windows-centric framework), and there is no mention of Linux-based application frameworks or tools. The documentation assumes the use of Windows tools and patterns, omitting equivalent Linux guidance.
Recommendations
  • Provide Linux and cross-platform instructions for certificate generation and upload (e.g., using OpenSSL for certificate creation, with command-line examples).
  • Include alternative application samples using popular Linux-friendly frameworks (such as Node.js/Express, Python/Flask, or Java/Spring) for the OpenID Connect integration.
  • When referencing documentation links (such as for certificate management), ensure both Windows and Linux tabs are present and linked, or provide explicit cross-platform guidance.
  • Clarify that the steps and tools are not limited to Windows, and provide notes or links for Linux users where appropriate.
  • Add example commands and configuration snippets for Linux environments (e.g., bash commands for file operations, Docker usage, etc.).
GitHub Create Pull Request
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 →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-specific instructions and examples (e.g., using the Update-MgDomain cmdlet from the Microsoft Graph PowerShell module) without offering equivalent command-line examples for Linux or macOS users. The documentation references Windows tools and patterns exclusively, with no mention of cross-platform alternatives such as Azure CLI, Bash scripts, or REST API usage from non-Windows environments. All step-by-step instructions and code snippets assume the use of the Azure Portal or PowerShell, both of which are more familiar to Windows users.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, especially for updating password expiry settings.
  • Include REST API examples using curl or HTTPie for PATCH operations, demonstrating usage from Linux/macOS terminals.
  • Explicitly mention that the Microsoft Graph PowerShell module is available cross-platform, or provide installation instructions for Linux/macOS.
  • Where possible, structure instructions so that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
  • Add a section or note clarifying that all operations can be performed from any OS, and link to relevant cross-platform tool documentation.
GitHub Create Pull Request
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 →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes setting up and running a WPF (Windows Presentation Foundation) desktop application using Visual Studio, a Windows-only tool. All instructions, screenshots, and workflow steps are tailored for Windows environments, with no mention of Linux or cross-platform alternatives. There are no Linux or macOS instructions, nor are there references to cross-platform frameworks or tools.
Recommendations
  • Provide equivalent instructions for running a cross-platform desktop application (e.g., using .NET MAUI or Avalonia UI) that works on Linux and macOS.
  • Include setup and run instructions for Linux (and optionally macOS), such as using Visual Studio Code or JetBrains Rider, and relevant .NET CLI commands.
  • Add Linux/macOS-specific prerequisites, such as installing the .NET SDK and any required dependencies.
  • Offer alternative screenshots and workflow steps for Linux/macOS environments.
  • Clarify in the introduction that the current quickstart is Windows-specific, and link to cross-platform guides if available.
GitHub Create Pull Request
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 →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments, particularly in the section on creating self-signed certificates, where only PowerShell is mentioned as a method. There are no examples or instructions for Linux or cross-platform tools (such as OpenSSL) for certificate creation. The documentation assumes the use of Windows tooling and does not provide parity for Linux or macOS users.
Recommendations
  • Add instructions and examples for creating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
  • Wherever PowerShell is referenced, provide equivalent bash or shell commands for Linux/macOS environments.
  • Explicitly mention that the certificate creation steps can be performed on any OS, and provide links or references to cross-platform tooling.
  • Review other sections for similar tool-specific assumptions and ensure parity in examples and guidance for non-Windows users.
GitHub Create Pull Request
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 →
Scanned: 2025-09-11 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform shells (e.g., Bash, curl, Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) may disadvantage Linux users or those preferring non-Windows scripting environments. There is no mention of how to perform the same tasks using common Linux tools or languages.
Recommendations
  • Provide a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, including authentication via client credentials.
  • Include a Python script example using the requests library to demonstrate cross-platform access.
  • Explicitly mention that the API can be accessed from any platform and provide guidance for Linux/macOS users.
  • Where PowerShell is used, add a note or section for equivalent Linux/macOS commands or scripts.
  • Consider referencing platform-agnostic tools (e.g., HTTPie, curl, Python) before or alongside PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides PowerShell-specific instructions and examples (e.g., using the Microsoft Graph PowerShell module and cmdlets like Update-MgDomain) without offering equivalent command-line examples for Linux/macOS users. There is an implicit assumption that administrators will use Windows tools, and no cross-platform alternatives (such as Azure CLI, Bash, or REST API with curl) are mentioned. This limits accessibility for non-Windows users.
Recommendations
  • Provide equivalent examples using Azure CLI and/or REST API with curl for Linux/macOS users, especially for operations currently shown only with PowerShell.
  • Explicitly mention that PowerShell Core is cross-platform, if relevant, and provide installation instructions for non-Windows systems.
  • Where possible, present REST API examples alongside PowerShell, and show how to invoke them from different platforms.
  • Review all step-by-step instructions to ensure they are not dependent on Windows-only tools or interfaces, or provide alternatives where necessary.
GitHub Create Pull Request
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 →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by providing certificate creation instructions only via PowerShell (a Windows-centric tool) and omitting equivalent Linux/macOS command-line examples (e.g., OpenSSL). There are no references to Linux-native tools or cross-platform approaches for key tasks such as certificate generation, which may hinder non-Windows users.
Recommendations
  • For every PowerShell-based example (such as certificate creation), provide equivalent Linux/macOS instructions using OpenSSL or other cross-platform tools.
  • Explicitly mention that certificate/key generation can be performed on any OS, and provide links or code snippets for Linux/macOS users.
  • Where possible, use neutral, cross-platform language and tools in examples, or at least present Windows and Linux options side by side.
  • Add a section or callout for Linux/macOS users, highlighting any OS-specific considerations or recommended tools.
GitHub Create Pull Request
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 →
Scanned: 2025-09-10 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows, specifically referencing a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no Linux or cross-platform alternatives mentioned, and all instructions and screenshots are Windows-specific. No guidance is provided for running or developing the sample on Linux or macOS, nor are any cross-platform frameworks or tools suggested.
Recommendations
  • Provide equivalent instructions and examples for running the sample on Linux and macOS, such as using .NET Core/MAUI or Avalonia UI for cross-platform desktop apps.
  • Include steps for using alternative IDEs like VS Code or JetBrains Rider, which are available on Linux and macOS.
  • Offer guidance for restoring NuGet packages and running the application from the command line using dotnet CLI, which is cross-platform.
  • Add screenshots and walkthroughs for non-Windows environments, or clarify the Windows-only scope if no alternatives exist.
  • Mention any limitations or requirements for running the sample on platforms other than Windows.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 focus on PowerShell and lack of cross-platform command-line instructions introduces a Windows bias.
Recommendations
  • Provide equivalent examples using Azure CLI or Bash scripts (with curl) for Linux/macOS users alongside PowerShell commands.
  • Explicitly mention that the PowerShell module can be used on non-Windows platforms, if applicable, and provide installation instructions for those platforms.
  • Where possible, present REST API calls with sample commands using curl or HTTPie to demonstrate platform-agnostic approaches.
  • Ensure that any references to tools or commands are balanced, giving equal prominence to both Windows and Linux/macOS workflows.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias towards Windows by exclusively providing PowerShell scripts for testing the REST API, referencing Microsoft PowerShell as the primary HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The only terminal-based example for making HTTP requests is in PowerShell, and there is no mention of Linux-native tools or cross-platform alternatives. This may hinder Linux/macOS users from following the guide seamlessly.
Recommendations
  • Provide equivalent Linux/macOS command-line examples using curl or HTTPie alongside the PowerShell script.
  • When referencing HTTP clients, mention cross-platform tools (e.g., curl, HTTPie, Postman) before or alongside Microsoft PowerShell.
  • Explicitly state that the steps and tools are cross-platform where possible, or provide platform-specific instructions as needed.
  • Ensure that all code snippets and instructions are tested and applicable on both Windows and Linux/macOS environments.
  • Consider adding a table or section summarizing how to perform key steps (such as making HTTP requests) on different operating systems.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. It explicitly instructs users to generate GUIDs using Microsoft PowerShell before mentioning online alternatives, and the first scripting example for obtaining tokens is in PowerShell. While a cURL (cross-platform) example is provided, the ordering and language suggest a Windows-first approach. There are no Linux-specific tools or shell examples, and the PowerShell method is referenced as the default for certain tasks.
Recommendations
  • When instructing users to generate GUIDs, mention both PowerShell and Linux/macOS equivalents (e.g., `uuidgen`), or list the cross-platform/online method first.
  • Provide scripting examples in both PowerShell and Bash (or at least shell-agnostic cURL) side by side, or clearly indicate that both are supported.
  • Avoid presenting Windows-specific tools or commands as the default or only method; always include Linux/macOS alternatives.
  • Consider adding a table or section summarizing equivalent commands for common tasks (e.g., GUID generation, HTTP requests) across Windows, Linux, and macOS.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/configure-authentication-sample-wpf-desktop-app.md ...b2c/configure-authentication-sample-wpf-desktop-app.md
High Priority View Details →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 for development. There are no references to Linux or cross-platform alternatives, and all instructions and code samples assume a Windows environment. No Linux-compatible frameworks, tools, or development environments are mentioned or suggested.
Recommendations
  • Include a section or note clarifying that WPF is Windows-only, and suggest cross-platform alternatives (such as .NET MAUI or Avalonia) for Linux/macOS users.
  • Provide equivalent instructions and code samples for a cross-platform desktop application (e.g., using Avalonia or .NET MAUI) that can run on Linux.
  • Mention and provide guidance for using cross-platform IDEs (such as Visual Studio Code or JetBrains Rider) and the .NET CLI, instead of only Visual Studio 2019.
  • If possible, provide sample projects and setup instructions that work on Linux, including package restore and build/run commands using the .NET CLI.
  • Explicitly state the platform limitations early in the documentation to set expectations for non-Windows developers.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 by linking only to IIS setup instructions. There are no equivalent examples or instructions for deploying or testing with a Linux-based web application (such as Apache or Nginx). Additionally, the documentation does not mention or provide guidance for Linux tools or environments, and all application setup references are Windows-centric.
Recommendations
  • Provide parallel instructions for setting up a test web application on Linux (e.g., Apache, Nginx) alongside the IIS example.
  • Include links to official documentation for deploying and configuring Linux-based web servers.
  • When referencing application setup, use neutral language (e.g., 'a web application such as IIS, Apache, or Nginx') and provide examples for both Windows and Linux platforms.
  • Ensure troubleshooting and configuration steps are applicable to both Windows and Linux environments, or clearly indicate platform-specific differences.
  • If scripts or commands are provided, include both PowerShell (Windows) and Bash (Linux) equivalents where relevant.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as a method for preparing a self-signed certificate. There are no Linux or cross-platform alternatives (such as OpenSSL) provided for certificate generation, and no Linux command-line examples are present. The rest of the documentation is largely platform-neutral, focusing on Azure portal steps and XML configuration, but the omission of Linux tooling for a key security step is a notable gap.
Recommendations
  • Add Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL, alongside the PowerShell example.
  • Explicitly mention that certificate generation can be performed on any OS, and provide equivalent commands for macOS and Linux.
  • Wherever PowerShell or Windows-specific tooling is referenced, provide a parallel example for Linux/macOS users.
  • Consider including a table or section summarizing certificate creation options for Windows, Linux, and macOS, with links to official documentation for each.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is generally platform-neutral for most tasks, as it focuses on using the Azure portal (web interface). However, in the 'Revoke a consumer user's session' section, only Microsoft Graph PowerShell is provided as a command-line example, and the instructions explicitly reference 'Windows PowerShell' without mentioning cross-platform compatibility or alternatives for Linux/macOS users. There are no CLI, Bash, or platform-agnostic command examples, nor is it clarified that Microsoft Graph PowerShell is available on non-Windows platforms.
Recommendations
  • Clarify that Microsoft Graph PowerShell is cross-platform and can be used on Linux and macOS, not just Windows.
  • Replace references to 'Windows PowerShell' with 'PowerShell' or 'a PowerShell terminal', and provide installation instructions for Linux/macOS if needed.
  • Provide equivalent examples using Azure CLI, Bash, or direct Microsoft Graph API calls with curl or HTTPie for Linux/macOS users.
  • Explicitly state that all command-line instructions are platform-agnostic where possible, or provide separate instructions for each major OS.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no examples or instructions for Linux or cross-platform desktop frameworks, nor are alternative tools or workflows mentioned for non-Windows users.
Recommendations
  • Include equivalent instructions for running the sample on Linux and macOS, such as using .NET Core/MAUI or Avalonia UI for cross-platform desktop development.
  • Provide guidance for using alternative IDEs like VS Code or JetBrains Rider, which are available on Linux and macOS.
  • Add steps for restoring NuGet packages and running the application via the command line (dotnet CLI), not just through Visual Studio.
  • Mention any platform-specific limitations or requirements, and offer alternative sample applications or code for non-Windows environments.
  • Explicitly state the Windows-only nature of the WPF sample and link to cross-platform alternatives if available.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 solution files (.sln), and describes steps using Visual Studio UI elements (e.g., Solution Explorer, right-click actions, F5 to debug). There are no instructions or examples for running the sample on Linux or macOS, nor are alternative tools (such as VS Code, JetBrains Rider, or command-line .NET tools) mentioned.
Recommendations
  • Add instructions for running the sample using cross-platform tools such as Visual Studio Code or JetBrains Rider.
  • Include steps for building and running the application using the .NET CLI (dotnet build, dotnet run), which works on Linux and macOS.
  • Mention prerequisites for Linux/macOS users, such as installing the .NET SDK and any required dependencies.
  • Provide equivalent screenshots or terminal output for Linux/macOS environments where relevant.
  • Clarify that Visual Studio is optional and provide parity in guidance for non-Windows users.
GitHub Create Pull Request
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 →
Scanned: 2025-09-09 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell script example for accessing audit logs programmatically, with no equivalent example for Linux or cross-platform shells (e.g., Bash/cURL). The script uses PowerShell-specific cmdlets and patterns, and there is no mention of Linux-native tools or guidance for non-Windows users. The only automation example is Windows-centric, and the documentation does not acknowledge or address Linux or macOS environments.
Recommendations
  • Provide a Bash/cURL example for accessing the Microsoft Graph API to retrieve audit logs, including authentication and pagination handling.
  • Explicitly mention that the API can be accessed from any platform and provide cross-platform code samples.
  • Include instructions or links for using common Linux tools (e.g., wget, curl, jq) to perform the same tasks as the PowerShell script.
  • Reorganize the automation section to present both Windows (PowerShell) and Linux/macOS (Bash/cURL) examples side by side, or lead with a platform-neutral API example.
  • Add a note clarifying that the PowerShell script can be run in Azure Cloud Shell (which supports PowerShell and Bash), but also provide a Bash example for parity.
GitHub Create Pull Request
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 →
Scanned: 2025-09-06 00:00
Reviewed by: Unknown
Issues: 3 bias types
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 by linking to IIS setup instructions. There are no examples or guidance for setting up or testing with a Linux-based web application or server. Additionally, no Linux-specific tools, commands, or patterns are mentioned, and the only application setup guidance is for Windows environments.
Recommendations
  • Provide parallel instructions for setting up a test web application on Linux (e.g., using Apache, Nginx, or a simple Python/Node.js HTTP server).
  • Include Linux-based examples and links for setting up SSL certificates and configuring backend applications.
  • Reference both Windows and Linux application scenarios equally when discussing prerequisites and test environments.
  • Avoid assuming IIS as the default or only test application; offer cross-platform alternatives.
  • Where possible, use neutral language and examples that are applicable to both Windows and Linux environments.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-wpf-desktop-app-options.md ...y-b2c/enable-authentication-wpf-desktop-app-options.md
High Priority View Details →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows, specifically WPF (Windows Presentation Foundation) desktop applications, with all code samples and instructions tailored exclusively for Windows environments. There are no Linux or cross-platform equivalents, and Windows-specific libraries and patterns (such as WindowInteropHelper and WPF APIs) are used throughout. No mention is made of how to achieve similar functionality on Linux or with cross-platform desktop frameworks.
Recommendations
  • Add equivalent guidance and code samples for cross-platform desktop frameworks (e.g., .NET MAUI, Avalonia, or Electron) that can run on Linux.
  • Include instructions and examples for configuring authentication in Linux desktop environments, using appropriate libraries and UI patterns.
  • Clearly indicate in the introduction that the guide is Windows-specific, and provide links or references to cross-platform or Linux-specific documentation if available.
  • Where possible, use cross-platform APIs or highlight differences between Windows and Linux implementations.
  • Mention any limitations or alternative approaches for developers targeting Linux or macOS.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page 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 equivalent instructions or references for performing these tasks on Linux or cross-platform environments, nor are there any mentions of AD FS alternatives or SAML providers that run on Linux. Troubleshooting and log access are also described solely in terms of Windows event logs.
Recommendations
  • Provide equivalent instructions for configuring SAML identity providers using cross-platform or Linux-based SAML solutions (e.g., Shibboleth, SimpleSAMLphp, or Keycloak).
  • Include examples of how to generate and manage certificates using Linux tools (e.g., OpenSSL) in addition to or instead of Windows tools.
  • Offer troubleshooting guidance for SAML integration that is not specific to Windows/AD FS, such as how to access logs or debug SAML assertions on Linux-based identity providers.
  • Clearly indicate that the instructions are specific to AD FS/Windows, and provide links or references to documentation for integrating with SAML providers on other platforms.
  • Where PowerShell is used, provide equivalent command-line or script examples for Linux environments if possible.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell script example for programmatically accessing Azure AD B2C audit logs, with no equivalent Linux/bash/cURL example. The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) reinforce a Windows-centric approach. There is no mention of Linux-native tools or cross-platform scripting options, and the scripting section is labeled as 'PowerShell script' without alternatives.
Recommendations
  • Add a bash/cURL example for querying the Microsoft Graph API for audit logs, including authentication and pagination.
  • Explicitly mention that the API can be accessed from any platform and provide cross-platform code samples.
  • Reference Linux tools (such as jq, curl, wget) alongside PowerShell, and clarify that the process is not limited to Windows environments.
  • Reorganize the scripting section to present both PowerShell and bash/cURL examples, or provide a language selector for users to choose their preferred scripting environment.
  • Update language to avoid implying PowerShell is the only or primary method for automation.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-specific commands for configuring password expiry duration, referencing the Microsoft Graph PowerShell module, and omitting equivalent CLI or scripting examples for Linux/macOS environments. All command-line automation is shown using PowerShell, and there are no Bash, Azure CLI, or cross-platform REST API examples for these tasks. The documentation assumes the use of Windows tools and does not mention or prioritize Linux alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell commands, especially for updating password policies and interacting with Microsoft Graph.
  • Explicitly mention that the REST API examples can be used with curl or other cross-platform tools, and provide sample curl commands.
  • Clarify that the PowerShell module is available on Linux/macOS via PowerShell Core, or provide installation instructions for non-Windows platforms.
  • Where possible, present cross-platform command-line examples before or alongside PowerShell examples to ensure parity.
  • Add a section or note addressing Linux/macOS administrators and their tooling options for these tasks.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and documentation (such as Schannel and enabling TLS 1.2 in Windows environments) and omitting Linux-specific guidance or examples. There are no Linux or cross-platform instructions for checking or configuring TLS/cipher suites, and the external links and troubleshooting steps are focused on Windows.
Recommendations
  • Include Linux-specific instructions or references for configuring TLS 1.2 and cipher suites (e.g., using OpenSSL, Apache/Nginx configuration).
  • Add examples or links for verifying TLS/cipher suites on Linux, such as using the openssl s_client command.
  • Balance the 'Next steps' section with Linux and cross-platform resources, not just Windows-focused articles.
  • Mention both Windows and Linux tools when suggesting how to test endpoint compatibility, such as testssl.sh or OpenSSL for Linux.
  • Ensure that troubleshooting steps and further reading cover both Windows and Linux environments equally.
GitHub Create Pull Request
← Previous Page 5 of 16 Next →