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 76-100 of 392 flagged pages
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
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by explicitly recommending Microsoft PowerShell as the example HTTP client for testing the POST request, without mentioning any Linux or cross-platform alternatives (such as curl or HTTPie). The only tool suggestion is Windows-centric and appears before any mention of Linux equivalents, which are absent. No Linux-specific or cross-platform command-line examples are provided for making token requests.
Recommendations
  • Include examples using curl and/or HTTPie for making HTTP requests, which are available on both Linux and Windows.
  • Mention cross-platform tools before or alongside Windows-specific tools like PowerShell.
  • Provide sample commands for Linux/macOS environments to ensure parity and inclusivity.
  • Clarify that any HTTP client can be used, and list several options for 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: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias in several areas. The instructions for generating a GUID mention Microsoft PowerShell first and provide a PowerShell command, with only a secondary reference to an online GUID generator. In the scripting section, the PowerShell example is presented before the cURL (Linux/macOS) example. There are no explicit Linux shell or CLI examples for generating GUIDs or interacting with Azure, and Windows-centric tools and patterns (PowerShell, Azure Portal screenshots) are referenced without Linux equivalents.
Recommendations
  • Provide Linux and macOS equivalents for all command-line instructions, such as using 'uuidgen' for GUID generation.
  • Present cURL (Linux/macOS) examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention cross-platform tools (e.g., Azure CLI) and provide examples for both Windows and Linux environments.
  • Include screenshots or instructions that are platform-neutral or show both Windows and Linux interfaces where relevant.
  • Reference Linux shell commands and utilities where applicable, not just Windows/PowerShell tools.
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-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only a PowerShell script example for programmatically accessing Azure AD B2C audit logs, with no equivalent example for Linux users (e.g., Bash, curl, or Python). The use of PowerShell and references to Azure Cloud Shell (which supports PowerShell by default) implicitly favors Windows environments and tools, potentially excluding or inconveniencing Linux and macOS users.
Recommendations
  • Add a Bash/curl example for querying the Microsoft Graph API to retrieve audit logs, showing how to authenticate and download logs using common Linux tools.
  • Provide a Python script example using the requests library to demonstrate cross-platform access to the API.
  • Explicitly mention that the API can be accessed from any platform, and link to platform-agnostic Microsoft Graph API documentation.
  • If referencing Azure Cloud Shell, clarify that both Bash and PowerShell environments are available, and provide examples for both.
  • Review other automation or scripting sections to ensure parity between Windows/PowerShell and Linux/Bash tooling.
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-15 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 Azure AD B2C audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash with curl or Python). The script assumes the use of PowerShell, which is natively available on Windows and Azure Cloud Shell, but not on most Linux distributions by default. No mention is made of Linux tools or alternative scripting approaches, and the only automation example is Windows-centric.
Recommendations
  • Add a Bash (curl/jq) example for querying the Microsoft Graph API and saving audit logs, suitable for Linux and macOS users.
  • Provide a Python example script for cross-platform compatibility.
  • Explicitly mention that PowerShell Core is available for Linux and macOS, and provide installation instructions or a note about this.
  • Ensure that automation and scripting guidance is not limited to Windows/PowerShell, and that Linux-first or cross-platform approaches are equally represented.
  • Where possible, use generic HTTP request examples (e.g., with curl or HTTPie) alongside PowerShell to ensure parity.
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-09-14 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 WPF desktop applications, and provides only C#/.NET code samples that are relevant to Windows environments. There are no Linux or cross-platform desktop application examples, nor any mention of Linux tools, patterns, or alternative frameworks. The guidance assumes the developer is working on Windows with WPF, omitting parity for Linux or macOS desktop application development.
Recommendations
  • Add equivalent examples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
  • Include code samples and configuration steps for Linux and macOS environments, or explicitly state the Windows-only scope if applicable.
  • Mention and link to MSAL libraries and authentication patterns for Linux-compatible desktop applications.
  • If WPF is the only supported scenario, clarify this limitation early in the documentation and provide links to cross-platform alternatives.
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-09-14 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and documentation (such as Schannel SSP and Windows-focused TLS configuration guides) in the 'Next steps' section, without providing equivalent Linux guidance or examples. There are no Linux or cross-platform configuration instructions or references, and the troubleshooting and enabling guides are Windows-centric.
Recommendations
  • Include links to Linux-focused resources for configuring TLS 1.2 and cipher suites (e.g., OpenSSL, Apache, Nginx documentation).
  • Provide examples or references for checking and enabling TLS 1.2 and required cipher suites on common Linux distributions.
  • Balance the 'Next steps' section by adding Linux and cross-platform articles alongside Windows resources.
  • Mention cross-platform tools (such as OpenSSL command-line utilities) for testing endpoint compatibility, in addition to SSL Labs.
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-09-14 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All AD FS configuration steps are described exclusively using Windows GUI tools (Server Manager, AD FS Management snap-in) and PowerShell cmdlets, with no mention of Linux equivalents or cross-platform alternatives. Troubleshooting guidance is focused on Windows Event Viewer. There are no examples or instructions for performing any step on Linux or macOS, nor is it acknowledged that AD FS is a Windows-only technology, which could help set expectations for non-Windows users.
Recommendations
  • Clearly state early in the documentation that AD FS is a Windows Server technology and requires Windows for configuration and management.
  • Where possible, provide PowerShell command-line alternatives for all GUI steps, and ensure these are presented alongside or before GUI instructions.
  • If any steps (such as certificate generation or SAML metadata inspection) can be performed on Linux/macOS, provide equivalent OpenSSL or command-line examples.
  • For troubleshooting, mention cross-platform tools (such as reading logs remotely, or using SAML-tracer browser extensions) where appropriate.
  • If Linux-based SAML identity providers are supported, link to or reference documentation for configuring those as alternatives.
  • Explicitly acknowledge the Windows dependency for AD FS and suggest alternatives for Linux environments, such as Shibboleth or SimpleSAMLphp, where relevant.
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-14 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 tools such as Bash, curl, or Python. The script assumes use of PowerShell (which is native to Windows), and there is no mention of Linux command-line tools or how to perform the same task on non-Windows platforms. This creates a bias towards Windows users and may hinder Linux administrators from following the instructions easily.
Recommendations
  • Provide equivalent Bash/curl and/or Python script examples for accessing the Microsoft Graph API and downloading audit logs, demonstrating how to authenticate and paginate results.
  • Explicitly mention that the API can be accessed from any platform, and link to cross-platform SDKs or CLI tools (such as Microsoft Graph CLI, Azure CLI, or REST API usage with curl).
  • Add a section or note clarifying that PowerShell Core is available on Linux and macOS, and provide installation instructions or alternatives.
  • Ensure that all automation and scripting examples have Linux-friendly equivalents, and present them either alongside or before Windows/PowerShell examples to promote parity.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/deploy-custom-policies-devops.md .../active-directory-b2c/deploy-custom-policies-devops.md
High Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell. All scripting and automation examples are provided exclusively in PowerShell, with no mention of Bash, shell scripts, or cross-platform alternatives. The instructions assume the use of PowerShell and Windows-style tooling throughout, with no guidance for Linux or macOS users. This could hinder adoption or create confusion for developers working in non-Windows environments.
Recommendations
  • Provide equivalent Bash or shell script examples for deploying policies, alongside the PowerShell script.
  • Explicitly mention that the process can be performed on Linux/macOS agents and provide any necessary adjustments (e.g., file paths, script execution).
  • Include guidance on installing required tools (such as PowerShell Core) on Linux/macOS, or clarify if the script requires Windows PowerShell-specific features.
  • Show how to configure Azure Pipelines to use a Linux agent and run the deployment script, either via Bash or PowerShell Core.
  • Consider using cross-platform scripting languages (e.g., Python) for automation examples, or at least acknowledge alternatives.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-spa-app.md .../active-directory-b2c/enable-authentication-spa-app.md
High Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing command-line examples in PowerShell syntax, referencing 'command shell' without clarifying cross-platform compatibility, and omitting explicit Linux/macOS instructions or terminal examples. The 'npm ./index.js' command is not standard for Node.js on Linux/macOS, and there are no mentions of Bash or Linux-specific considerations.
Recommendations
  • Provide both Windows (PowerShell/cmd) and Linux/macOS (Bash) command examples for all terminal instructions.
  • Replace or supplement 'npm ./index.js' with 'node ./index.js', which is cross-platform and standard for running Node.js apps.
  • Clarify that the steps are applicable to all platforms and specify any platform-specific differences where relevant.
  • Explicitly mention that the instructions work on Windows, Linux, and macOS, and provide guidance for installing Node.js and npm on each platform if not already covered elsewhere.
  • Use neutral terms like 'terminal' or 'shell' and avoid assuming a Windows environment.
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-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing only PowerShell examples (specifically the Microsoft Graph PowerShell module) for configuring password expiry duration, without offering equivalent CLI or scripting examples for Linux/macOS users. There are no references to cross-platform tools or instructions for performing these tasks outside of the Azure Portal or PowerShell, and no mention of Bash, Azure CLI, or REST API usage from non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for updating password expiry duration.
  • Explicitly mention that the Microsoft Graph API can be used from any platform, and provide curl or HTTP request examples for relevant operations.
  • Clarify that the Azure Portal is web-based and accessible from any OS, but for scripting/automation, offer both Windows (PowerShell) and Linux/macOS (CLI, Bash, curl) instructions.
  • Add a section or note highlighting cross-platform options for administrators who do not use Windows or PowerShell.
GitHub 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 →
Scanned: 2025-09-13 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 Windows bias by providing only PowerShell scripts for key generation and certificate creation, referencing Windows-specific tools (e.g., PowerShell's New-SelfSignedCertificate), and omitting equivalent Linux/macOS commands. No cross-platform or Linux alternatives are mentioned, and Windows tooling is presented as the default or only option.
Recommendations
  • Provide equivalent Linux/macOS command-line instructions for generating symmetric keys (e.g., using openssl or /dev/urandom).
  • Include Linux/macOS examples for creating self-signed certificates (e.g., using openssl).
  • When referencing PowerShell or Windows tools, add a note or section for cross-platform alternatives.
  • Consider reordering or parallelizing instructions so that Windows and Linux/macOS approaches are presented together, rather than Windows-first.
  • Explicitly state that the process is platform-agnostic and provide links or references to cross-platform tooling.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-adfs.md ...rticles/active-directory-b2c/identity-provider-adfs.md
High Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing AD FS (Active Directory Federation Services), which is a Windows Server feature. All configuration steps for setting up the identity provider are described using Windows GUI tools (Server Manager, AD FS Management), with no mention of command-line alternatives or Linux-based equivalents. There are no examples or guidance for performing similar tasks on Linux or cross-platform environments, nor is there any mention of open-source alternatives to AD FS.
Recommendations
  • Provide PowerShell and command-line alternatives for AD FS configuration steps, which can be run on Windows Server Core or remotely.
  • Acknowledge that AD FS is a Windows-only technology and suggest open-source or cross-platform alternatives (such as Keycloak, IdentityServer, or other OpenID Connect providers) for Linux users.
  • Include a section or links for configuring a generic OpenID Connect provider from Linux, with example commands and configuration files.
  • Clarify in the prerequisites that AD FS requires Windows Server and provide links to documentation for setting up AD FS from scratch, including any available automation scripts.
  • If possible, add parity by showing how to perform similar identity provider integration using a Linux-based OpenID Connect provider, so non-Windows users have a clear migration or integration path.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/identity-provider-generic-saml-options.md ...irectory-b2c/identity-provider-generic-saml-options.md
High Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias in the 'Debug SAML protocol' section, where Windows-specific tools (Microsoft Edge or Internet Explorer developer tools) are mentioned alongside browser extensions, and a Microsoft TechCommunity link is provided for gathering SAML tokens using Edge or IE. There are no explicit Linux or cross-platform command-line examples or references to Linux tools (such as curl, openssl, or Linux browser debugging tools). The rest of the documentation is platform-neutral, focusing on XML configuration and SAML protocol details.
Recommendations
  • In the 'Debug SAML protocol' section, add references to Linux-compatible tools for SAML debugging, such as using curl, wget, or command-line SAML tracing tools.
  • Include instructions or links for using browser developer tools on Linux (e.g., Chrome/Chromium or Firefox on Linux) for SAML tracing.
  • Avoid mentioning Microsoft Edge or Internet Explorer developer tools before cross-platform alternatives; instead, present browser extensions (SAML DevTools, SAML-tracer) first, then mention platform-specific tools as optional.
  • If any command-line or scripting examples are added in the future, ensure both Windows (PowerShell, CMD) and Linux (bash, shell) equivalents are provided.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/multiple-token-endpoints.md ...icles/active-directory-b2c/multiple-token-endpoints.md
High Priority View Details →
Scanned: 2025-09-13 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 toward Windows development environments. It references Visual Studio (a Windows-centric IDE), .sln solution files, and Web.config XML configuration—all typical of Windows/.NET workflows. There are no examples or instructions for Linux or cross-platform development environments, nor are alternative editors or build tools mentioned. The guide assumes the user is using Windows and Visual Studio, with no mention of how to perform equivalent steps on Linux or with cross-platform tools.
Recommendations
  • Include instructions for opening and editing the project using cross-platform editors such as VS Code, JetBrains Rider, or command-line tools.
  • Provide guidance on building and running the sample using the .NET CLI (dotnet build/run), which works on Linux, macOS, and Windows.
  • Mention how to edit configuration files and run the sample on Linux, including any differences in file paths or environment variables.
  • Clarify that the sample can be used on non-Windows platforms and provide any prerequisites or caveats for Linux users.
  • Where Visual Studio is referenced, add alternatives or note that other editors can be used.
GitHub Create Pull Request
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 →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio (a Windows-centric tool) as the publishing method for the API and linking to Visual Studio-specific deployment instructions. There are no examples or instructions for deploying the API from Linux or using cross-platform tools like VS Code, Azure CLI, or GitHub Actions. The absence of Linux or cross-platform deployment guidance makes it less accessible for non-Windows users.
Recommendations
  • Add instructions for deploying the API using cross-platform tools such as Azure CLI, VS Code, or GitHub Actions.
  • Provide Linux/macOS command-line examples for API deployment and configuration.
  • Include references to non-Windows development environments and editors where applicable.
  • Ensure that all tooling and deployment steps have Linux/macOS equivalents or alternatives documented alongside Windows/Visual Studio instructions.
GitHub Create Pull Request
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 →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell scripts for certificate and key generation, referencing Visual Studio for deployment, and omitting equivalent Linux/macOS commands or tools. No cross-platform alternatives (such as OpenSSL or Bash scripts) are mentioned, and the workflow assumes a Windows-centric development environment.
Recommendations
  • Provide equivalent Linux/macOS instructions for generating self-signed certificates (e.g., using OpenSSL) and random strings (e.g., with Bash or Python).
  • Include deployment guidance for non-Windows environments, such as using Azure CLI or VS Code instead of only Visual Studio.
  • Clearly label PowerShell/Windows-specific steps and offer parallel steps for other platforms.
  • Reference cross-platform tools and patterns where possible, and avoid assuming the user is on Windows.
  • Add a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-onfido.md ...b/main/articles/active-directory-b2c/partner-onfido.md
High Priority View Details →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Visual Studio, Azure Storage Explorer) and workflows without providing equivalent Linux alternatives or instructions. The only code publishing example mentions Visual Studio, and file upload/management is described using Azure Storage Explorer, which is primarily a Windows application. There are no CLI, cross-platform, or Linux-specific instructions or examples provided for these steps.
Recommendations
  • Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or VS Code, including command-line examples suitable for Linux and macOS users.
  • Include instructions for uploading and managing files in Azure Blob Storage using the Azure CLI (az storage blob upload), PowerShell (for Windows), and/or cross-platform tools like AzCopy.
  • Mention and link to cross-platform editors (e.g., VS Code) and deployment methods, not just Visual Studio.
  • When referencing Azure Storage Explorer, note its availability on Linux and macOS, or suggest alternative CLI-based workflows.
  • Ensure that all steps involving file editing, uploading, or deployment have Linux-compatible examples or notes.
GitHub Create Pull Request
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 →
Scanned: 2025-09-13 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based instructions for enabling Saviynt to delete users, explicitly stating the use of a 'Windows workstation or server.' There are no equivalent examples or guidance for Linux or macOS users, and the use of PowerShell and Windows terminology is presented as the default and only method.
Recommendations
  • Provide equivalent instructions for Linux and macOS environments, such as using Microsoft Graph CLI, Azure CLI, or PowerShell Core (pwsh) on non-Windows platforms.
  • Clarify that PowerShell Core is cross-platform and provide installation steps for Linux/macOS if PowerShell is still the preferred method.
  • Include alternative command-line examples using Azure CLI or REST API calls with curl for broader compatibility.
  • Avoid language that assumes the user is on Windows; instead, offer platform-agnostic steps or clearly separate instructions for each OS.
  • Add notes or links to Microsoft documentation on using Microsoft Graph tools on Linux/macOS.
GitHub Create Pull Request
Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-directory-quota.md ...ive-directory-b2c/tenant-management-directory-quota.md
High Priority View Details →
Scanned: 2025-09-13 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 for monitoring directory quota, with no equivalent example for Linux or cross-platform environments. The script uses Windows-specific tools (PowerShell cmdlets), and there is no mention of how to perform the same task using Bash, curl, or other common Linux utilities.
Recommendations
  • Add a Bash example using curl or httpie to obtain the access token and call the Microsoft Graph API, so Linux and macOS users can follow the steps without PowerShell.
  • Clearly indicate that the PowerShell script is for Windows users, and provide equivalent instructions for Linux/macOS.
  • Consider using cross-platform tools or scripting languages (such as Python) for examples, or at least provide them as alternatives.
  • Mention that PowerShell Core is available on Linux/macOS if users wish to use PowerShell scripts, but do not assume it as the default.
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-13 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 for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash or Python). The script assumes the use of PowerShell, which is natively available on Windows and Azure Cloud Shell, but not on most Linux distributions by default. There is no mention of alternative tools or scripting languages commonly used on Linux, nor guidance for users who may not have access to PowerShell.
Recommendations
  • Provide a Bash/cURL example for accessing the Microsoft Graph API to retrieve audit logs, suitable for Linux and macOS users.
  • Include a cross-platform example using a language like Python (with the requests library), which is widely available on both Windows and Linux.
  • Explicitly state that PowerShell Core is available for Linux and provide installation instructions or a note for Linux users who wish to use the PowerShell script.
  • Where possible, present both Windows and Linux examples side-by-side, or at least mention alternatives to PowerShell for non-Windows environments.
  • Review other sections for similar single-platform bias and ensure parity in automation and scripting guidance.
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-12 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. All instructions, screenshots, and prerequisites are tailored to Windows environments, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for running or developing the sample on Linux or macOS.
Recommendations
  • Provide equivalent instructions for running the sample on Linux (and macOS), such as using .NET Core cross-platform capabilities and alternative IDEs like VS Code or JetBrains Rider.
  • Include Linux/macOS prerequisites (e.g., .NET SDK installation, compatible editors, and command-line build/run instructions).
  • Offer screenshots and workflow steps for Linux/macOS environments to ensure parity.
  • Mention and link to any cross-platform sample applications (e.g., using Avalonia or MAUI instead of WPF) if available, or clarify Windows-only limitations.
  • Explicitly state platform requirements and suggest alternatives for non-Windows users.
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-12 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 only PowerShell examples for configuring password expiry duration, referencing the Microsoft Graph PowerShell module, and omitting equivalent instructions or examples for Linux or cross-platform environments (such as Bash, Azure CLI, or REST API via curl). The documentation assumes the use of Windows tools and patterns, and does not mention or prioritize Linux-compatible alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux and macOS users, especially for tasks currently demonstrated only with PowerShell.
  • Include REST API examples using curl or similar cross-platform tools for all operations shown with PowerShell.
  • When referencing tools or commands, mention both Windows and Linux options, or clarify if the instructions are cross-platform.
  • Reorder sections or examples to present cross-platform or Linux-compatible instructions before or alongside Windows/PowerShell examples.
  • Explicitly state the platform requirements for each example, and link to official documentation for installing required tools on both Windows and Linux.
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-12 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 providing a link to IIS setup instructions. There are no equivalent examples or instructions for Linux-based web servers (such as Apache or Nginx), nor are Linux tools or patterns mentioned. The documentation assumes the use of Windows environments for application testing and setup, which may exclude or disadvantage Linux users.
Recommendations
  • Provide parallel examples and setup instructions for common Linux web servers (e.g., Apache, Nginx) alongside the IIS example.
  • Include links to official documentation for setting up test applications on Linux.
  • When referencing application setup, use neutral language (e.g., 'a web application such as IIS, Apache, or Nginx') rather than only mentioning Windows tools.
  • Ensure that any configuration steps or screenshots that are OS-specific are balanced with Linux equivalents.
  • Explicitly state that the solution is platform-agnostic where possible, and clarify any steps that are unique to Windows or Linux.
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-12 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the certificate creation section where only PowerShell is mentioned for generating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) for certificate generation. The rest of the documentation is largely platform-neutral, focusing on Azure portal steps and XML configuration, but the lack of Linux or cross-platform tooling in key security setup steps may hinder non-Windows users.
Recommendations
  • Add Linux and cross-platform examples for generating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
  • Wherever PowerShell is referenced, provide equivalent Bash or shell commands for Linux/macOS users.
  • Explicitly mention that certificate generation can be performed on any OS, and link to official documentation for OpenSSL or other cross-platform tools.
  • Review other sections for any implicit assumptions of Windows environments (e.g., file paths, tool usage) and clarify or generalize as needed.
GitHub Create Pull Request
← Previous Page 4 of 16 Next →