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 201-225 of 392 flagged pages
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/https-cipher-tls-requirements.md
.../active-directory-b2c/https-cipher-tls-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates 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. No Linux or cross-platform configuration instructions are provided, and the linked resources are primarily Windows-focused.
Recommendations
- Include examples or references for configuring TLS 1.2 and cipher suites on common Linux web servers (e.g., Apache, Nginx) and platforms.
- Add links to official Linux/OpenSSL documentation for managing cipher suites and TLS versions.
- Balance the 'Next steps' section with resources relevant to both Windows and Linux environments.
- Mention cross-platform tools (such as OpenSSL's s_client) for endpoint testing, in addition to SSL Labs.
- Explicitly state that the requirements apply to all platforms and provide parity in troubleshooting guidance for non-Windows systems.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows-specific tools (such as Server Manager and AD FS Management), providing only GUI-based instructions for AD FS setup, and omitting any Linux or cross-platform alternatives. There are no command-line or Linux-based examples for configuring AD FS or equivalent identity providers, and all instructions assume a Windows Server environment.
Recommendations
- Provide equivalent command-line instructions using PowerShell and, if possible, cross-platform tools or APIs.
- Acknowledge that AD FS is a Windows-only technology, but suggest or link to Linux-compatible alternatives (such as Shibboleth, Keycloak, or other OpenID Connect providers) for non-Windows environments.
- Include a section or appendix outlining how to integrate Azure AD B2C with OpenID Connect providers running on Linux, with example configurations.
- Clarify early in the documentation that the steps are specific to Windows Server and AD FS, and offer guidance for users on other platforms.
- Where possible, reference REST APIs or scripting approaches that could be used from non-Windows systems to automate or replicate the configuration.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-users-portal.md
...n/articles/active-directory-b2c/manage-users-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Revoke a consumer user's session' section, where only Microsoft Graph PowerShell commands are provided and explicitly reference 'Windows PowerShell.' There are no equivalent examples for Linux or macOS users, nor is there mention of using cross-platform tools like the Microsoft Graph CLI or direct API calls via curl. The rest of the documentation focuses on portal-based actions, which are platform-agnostic, but the only programmatic example is Windows-centric.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using Microsoft Graph PowerShell on those platforms (since it is cross-platform), or using the Microsoft Graph CLI or REST API via curl.
- Avoid phrases like 'In your Windows PowerShell' and instead use 'In your terminal' or specify that the commands work on all supported platforms.
- Include explicit Linux/macOS command-line examples where programmatic actions are shown, or at least mention that the tools are cross-platform.
- Where possible, link to documentation for installing and using Microsoft Graph PowerShell on Linux/macOS, and/or provide REST API examples for users who prefer not to use PowerShell.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/multiple-token-endpoints.md
...icles/active-directory-b2c/multiple-token-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation assumes a Windows development environment throughout. It references Visual Studio (a Windows-centric IDE), .sln solution files, and Web.config XML configuration, all of which are typical of Windows/.NET workflows. There are no instructions or examples for Linux or cross-platform development environments, nor are alternative tools or editors mentioned. The guide does not address how to perform equivalent steps on Linux (e.g., using VS Code, JetBrains Rider, or command-line tools), nor does it mention .NET Core cross-platform capabilities.
Recommendations
- Include instructions for opening and editing the project using cross-platform tools such as VS Code or JetBrains Rider.
- Mention how to run and test the sample application on Linux or macOS, including any prerequisites (e.g., .NET SDK installation, command-line build/run instructions).
- Provide examples of editing configuration files using common Linux tools (nano, vim) or via the command line.
- Clarify that the instructions are applicable to .NET Core/.NET 5+ projects, which are cross-platform, and note any differences for non-Windows environments.
- Add a section or notes on how to deploy and test the application on Linux-based servers or containers.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-akamai-secure-hybrid-access.md
...e-directory-b2c/partner-akamai-secure-hybrid-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by referencing Windows-specific tools and workflows (such as ASP.NET MVC and OWIN middleware), providing links and instructions that default to Windows (e.g., certificate management), and omitting equivalent Linux-based examples or guidance. There are no Linux or cross-platform code samples for application integration, and the only application example for OIDC is a .NET/Windows stack. Certificate management and other operational steps reference Windows tabs or tools without Linux alternatives.
Recommendations
- Provide Linux-based examples for application integration, such as using a Python Flask or Node.js app for OIDC instead of only ASP.NET MVC.
- Include instructions for obtaining and uploading certificates using Linux tools (e.g., OpenSSL) alongside or instead of Windows-centric instructions.
- Ensure that all referenced documentation (such as certificate management) includes Linux tabs or sections, not just Windows.
- When describing application configuration, offer both Windows and Linux deployment scenarios, especially for sample/demo apps.
- Use cross-platform terminology and avoid assuming the reader is using Windows by default.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-jumio.md
...ob/main/articles/active-directory-b2c/partner-jumio.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell scripts for critical steps such as generating self-signed certificates and random signing keys, with no equivalent Linux or cross-platform commands. The use of PowerShell and references to Visual Studio for deployment further reinforce a Windows-centric approach, while omitting guidance for Linux or macOS users.
Recommendations
- Provide equivalent Bash/OpenSSL commands for generating self-signed certificates and random strings for Linux/macOS users.
- Include deployment instructions using cross-platform tools such as Azure CLI, GitHub Actions, or VS Code instead of only referencing Visual Studio.
- Explicitly mention that the PowerShell examples are for Windows and offer alternatives for other operating systems.
- Review all steps to ensure that Linux and macOS users can follow the tutorial without needing to switch to a Windows environment.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-f5.md
.../blob/main/articles/active-directory-b2c/partner-f5.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing IIS as the example application for testing, linking to Microsoft IIS setup guides, and omitting any mention of Linux-based web servers (such as Apache or Nginx) or their configuration. All application testing and setup guidance is Windows-centric, with no Linux alternatives or parity in examples or instructions.
Recommendations
- Add parallel instructions and examples for deploying and testing with a Linux-based web application (e.g., Apache, Nginx, or a generic Python/Node.js app).
- Include links to official documentation for setting up a test web application on Linux.
- When referencing IIS, also mention Linux alternatives and provide equivalent configuration steps.
- Ensure troubleshooting and SSL certificate management sections include Linux-relevant guidance (e.g., using OpenSSL, configuring certificates on Apache/Nginx).
- Use neutral language when referring to test applications, e.g., 'a web application (such as IIS on Windows or Apache on Linux)' instead of only mentioning IIS.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-idology.md
.../main/articles/active-directory-b2c/partner-idology.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio and linking to Windows-centric deployment instructions, without mentioning or providing equivalent guidance for Linux-based development environments or deployment tools. There are no examples or instructions for deploying the API from Linux or using cross-platform tools, and the only deployment path described is via Visual Studio, which is primarily a Windows tool.
Recommendations
- Add instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, which can be used from Linux, macOS, or Windows.
- Provide examples for deploying the API using the dotnet CLI (dotnet publish) and Azure CLI (az webapp up), which are available on Linux.
- Include a note or section highlighting that Visual Studio is not required and that developers can use VS Code or other editors on Linux.
- Where deployment instructions are given, offer both Windows (Visual Studio) and Linux (CLI-based) alternatives, and avoid assuming the user is on Windows.
- Review all linked documentation to ensure Linux users are not excluded or left without guidance.
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. It references Windows-specific tools (Visual Studio, Azure Storage Explorer) without mentioning cross-platform or Linux alternatives, and omits command-line or deployment examples for Linux users. There are no explicit Linux or macOS instructions, and the only tool mentioned for code publishing is Visual Studio, which is primarily a Windows application.
Recommendations
- Provide alternative instructions for deploying the API using cross-platform tools such as the Azure CLI, Azure DevOps, or GitHub Actions, including Linux/macOS command-line examples.
- Mention and link to cross-platform editors (e.g., VS Code) and deployment methods (e.g., dotnet CLI, az webapp deploy) alongside Visual Studio.
- For managing Azure Storage, suggest cross-platform tools such as the Azure CLI (az storage blob upload), AzCopy, or the Azure Portal, not just Azure Storage Explorer.
- Explicitly state that all steps can be performed from Linux/macOS as well as Windows, and provide any necessary shell or command-line examples.
- Review all tool and workflow mentions to ensure parity for Linux and macOS users, not just Windows.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-saviynt.md
.../main/articles/active-directory-b2c/partner-saviynt.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing PowerShell-based instructions for enabling Saviynt to delete users in Azure AD B2C. It explicitly instructs users to install the Microsoft Graph PowerShell module on a Windows workstation or server, with no mention of Linux or cross-platform alternatives. No CLI, Bash, or platform-agnostic examples are provided, and the use of PowerShell is assumed throughout the configuration steps.
Recommendations
- Provide equivalent instructions using the Microsoft Graph CLI or REST API with curl, which are cross-platform and work on Linux, macOS, and Windows.
- Explicitly mention that the Microsoft Graph PowerShell module is available for Linux and macOS via PowerShell Core, and provide installation steps for those platforms.
- Include Bash or shell script examples alongside PowerShell commands, or at least reference how to perform the same operations on Linux.
- Avoid language that assumes a Windows environment (e.g., 'on a Windows workstation or server') unless absolutely necessary, and clarify when steps are platform-specific.
- Add a section or note about platform compatibility and alternative tooling for non-Windows users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/partner-twilio.md
...b/main/articles/active-directory-b2c/partner-twilio.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by referencing .NET and web.config (Windows-centric technologies), omitting Linux-specific deployment or configuration guidance, and providing hosting instructions only for Azure App Service (commonly used with Windows). There are no examples or instructions for Linux-based hosting, configuration (such as environment variables or appsettings.json), or cross-platform .NET Core usage.
Recommendations
- Provide Linux-specific deployment instructions, such as hosting the .NET app on Linux-based services (e.g., Azure App Service for Linux, Docker, or on-premises Linux servers).
- Include configuration examples using appsettings.json and environment variables, which are cross-platform and preferred for .NET Core/5+/6+ applications.
- Offer guidance for running the sample app using the dotnet CLI, including Linux/macOS terminal commands.
- Mention cross-platform certificate creation and management tools (e.g., OpenSSL) alongside or instead of Windows certificate tools.
- Clarify that the sample app and instructions are compatible with both Windows and Linux, and highlight any platform-specific considerations.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-native-app-desktop.md
.../active-directory-b2c/quickstart-native-app-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows, specifically using a WPF (Windows Presentation Foundation) desktop application and Visual Studio as the development environment. There are no examples or instructions for running the sample on Linux or macOS, nor are any cross-platform frameworks or tools mentioned. All screenshots and workflow steps are tailored to Windows users, and the use of Visual Studio (Windows-only for WPF) further excludes Linux users.
Recommendations
- Provide equivalent instructions and sample applications for Linux (and macOS), such as using .NET MAUI or Avalonia for cross-platform desktop apps.
- Include steps for running the sample using Visual Studio Code or JetBrains Rider, which are available on Linux.
- Offer command-line instructions for building and running the application using the .NET CLI, which is cross-platform.
- Add Linux-specific prerequisites and troubleshooting sections.
- Include screenshots and workflow descriptions for non-Windows environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/quickstart-web-app-dotnet.md
...cles/active-directory-b2c/quickstart-web-app-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio (a primarily Windows IDE) for running the sample application, and all instructions assume the use of Windows tooling and workflows. There are no examples or guidance for running the sample on Linux or using cross-platform tools such as VS Code, .NET CLI, or alternative editors. Linux users are left without instructions on how to set up, run, or debug the sample application.
Recommendations
- Add a section with instructions for running the sample on Linux using the .NET CLI (e.g., dotnet build, dotnet run) and editors like VS Code.
- Mention cross-platform prerequisites, such as installing the .NET SDK, and provide download links for Linux and macOS.
- Include Linux/macOS-specific steps for cloning the repository, restoring dependencies, and running both the web app and API.
- Provide screenshots or terminal output examples for Linux environments where appropriate.
- Clarify that Visual Studio is optional and that the sample can be run on any platform supporting .NET Core/ASP.NET Core.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/secure-rest-api.md
.../main/articles/active-directory-b2c/secure-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the certificate creation section, where only PowerShell is mentioned as a method for creating self-signed certificates. There are no equivalent Linux or cross-platform command-line examples (such as OpenSSL) provided for certificate generation. The rest of the documentation is largely platform-agnostic, focusing on Azure portal UI and XML configuration, but the lack of Linux guidance in key operational steps may hinder non-Windows users.
Recommendations
- Provide Linux and cross-platform examples for creating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
- When referencing command-line tools or scripts, ensure both Windows (PowerShell) and Linux (Bash/OpenSSL) options are presented, or link to platform-agnostic Azure CLI documentation where possible.
- Explicitly state that certificate creation can be performed on any OS, and provide step-by-step instructions for at least the two major platforms (Windows and Linux).
- Review any included scripts or downloadable resources to ensure they are not Windows-only, or provide equivalents for Linux/macOS users.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/tenant-management-directory-quota.md
...ive-directory-b2c/tenant-management-directory-quota.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a PowerShell script for monitoring directory quota, with no equivalent example for Linux or cross-platform environments. It assumes the use of Windows tools and patterns (PowerShell, Invoke-RestMethod, New-Object), and does not mention or prioritize Linux-compatible alternatives. This may hinder users on Linux or macOS from following the guide easily.
Recommendations
- Provide a cross-platform example using curl and jq (or similar tools) for Linux/macOS users.
- Include a note that the PowerShell script can be run on PowerShell Core, which is available on Linux and macOS, if applicable.
- List both Windows (PowerShell) and Linux/macOS (bash/curl) examples side by side, or at least mention Linux alternatives.
- Avoid assuming the user is on Windows; use more neutral language and tool recommendations.
- Add a section or callout for Linux users, explaining how to achieve the same result with native tools.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/view-audit-logs.md
.../main/articles/active-directory-b2c/view-audit-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically accessing audit logs via the Microsoft Entra reporting API. There are no equivalent examples using Linux-native tools (such as curl, wget, or Python), nor are there references to Bash or shell scripting. The script assumes familiarity with PowerShell, which is primarily a Windows tool, and suggests using Azure Cloud Shell (which does support PowerShell, but Bash is also available). This creates a bias toward Windows users and may hinder Linux users or those preferring cross-platform scripting.
Recommendations
- Provide equivalent examples using Bash shell scripting with curl or wget to demonstrate how to access the API and process results on Linux or macOS.
- Include a Python example for querying the Microsoft Graph API, as Python is cross-platform and widely used.
- Explicitly mention that the API can be accessed from any platform and that PowerShell is just one option.
- Add a note or section on using Azure CLI or other cross-platform tools where applicable.
- Reorder or parallelize examples so that Windows and Linux approaches are presented together, or alternate which comes first.
Active Directory B2C
Request an access token in Azure Active Directory B2C
...ob/main/articles/active-directory-b2c/access-tokens.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation mentions Microsoft PowerShell as an example HTTP client for testing the POST request, but does not mention any Linux/macOS alternatives (such as curl or HTTPie), nor does it provide example commands for those platforms. This creates a subtle bias toward Windows users by implying PowerShell is the default or preferred tool.
Recommendations
- List cross-platform HTTP clients (e.g., curl, HTTPie, Postman) alongside PowerShell.
- Provide example commands for Linux/macOS users using curl or HTTPie.
- Clarify that any HTTP client can be used and provide links to relevant documentation for non-Windows tools.
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 focuses on configuring and deploying a .NET demo web app, referencing web.config and certificate management patterns typical of Windows/IIS environments. There are no explicit instructions or examples for Linux/macOS users, such as using appsettings.json, environment variables, or Linux-native certificate handling. Hosting guidance is only provided for Azure App Service (which can be Windows or Linux), but no Linux-specific deployment steps or troubleshooting are mentioned. All configuration snippets and references assume a Windows-centric workflow.
Recommendations
- Add instructions for configuring the demo app on Linux/macOS, including environment variable usage and appsettings.json alternatives to web.config.
- Provide guidance for certificate creation and management using Linux tools (e.g., OpenSSL) and how to reference certificates in non-Windows environments.
- Include deployment steps for Linux-based hosting providers (e.g., Azure App Service on Linux, Docker, or other cloud platforms).
- Present cross-platform examples side-by-side, or clearly indicate platform-specific steps.
- Clarify any .NET Core/ASP.NET compatibility for Linux and how to adapt the sample app for non-Windows environments.
Active Directory B2C
Call a REST API by using Azure AD B2C custom policy
...-directory-b2c/custom-policies-series-call-rest-api.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell examples for making HTTP requests to the REST API, referencing Microsoft PowerShell as the suggested HTTP client, and omitting equivalent Linux/macOS command-line examples (e.g., curl). Windows tools and patterns are mentioned first and exclusively, creating friction for Linux/macOS users who must adapt instructions to their environment.
Recommendations
- Provide equivalent Linux/macOS examples using common tools such as curl or httpie alongside PowerShell scripts.
- Explicitly mention cross-platform alternatives for HTTP requests, e.g., 'You can use PowerShell (Windows) or curl (Linux/macOS) to test the API.'
- Avoid referencing Microsoft PowerShell as the only HTTP client; suggest platform-neutral tools where possible.
- Where command-line instructions are given, present both Windows and Linux/macOS versions, or clarify which platforms are supported.
Active Directory B2C
Deploy custom policies with Azure Pipelines
.../active-directory-b2c/deploy-custom-policies-devops.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies, with no mention of Bash, shell, or cross-platform alternatives. All code samples, pipeline steps, and instructions assume PowerShell usage, which is native to Windows and only optionally available on Linux/macOS. There are no Linux/macOS-specific instructions or examples, and the documentation does not address how to run these tasks on non-Windows agents.
Recommendations
- Provide equivalent Bash or shell script examples for deploying policies using curl or other cross-platform tools.
- Explicitly mention that PowerShell Core (pwsh) can be used on Linux/macOS, and provide instructions for installing it if required.
- Add guidance on configuring Azure Pipelines agents running on Linux/macOS, including how to execute the deployment script in those environments.
- List any platform-specific prerequisites or caveats for non-Windows users.
- Present examples for both Windows and Linux/macOS side-by-side, or clarify cross-platform compatibility.
Active Directory B2C
Define an ID token hint technical profile in a custom policy
...ob/main/articles/active-directory-b2c/id-token-hint.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'How-to guide' sections for generating symmetric and asymmetric keys. PowerShell is exclusively used for key and certificate generation, with no Linux/macOS alternatives (e.g., OpenSSL) provided. Windows tools and patterns are mentioned first and exclusively, and the GitHub samples referenced are .NET/ASP.NET-centric, which are more common on Windows. Linux/macOS users are left to infer or research their own solutions for key/certificate generation and related tasks.
Recommendations
- Provide equivalent Linux/macOS command-line examples for key and certificate generation (e.g., OpenSSL for symmetric keys and self-signed certificates).
- Mention cross-platform tools and approaches before or alongside Windows-specific ones.
- Reference sample code in other languages/platforms (e.g., Node.js, Python) where possible.
- Explicitly state that the PowerShell examples are Windows-specific and offer alternatives for other OSes.
Active Directory B2C
Configure a force password reset flow in Azure AD B2C
.../articles/active-directory-b2c/force-password-reset.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only CLI tool shown for scripting password expiry, with no equivalent Linux/macOS shell or REST API example. The use of PowerShell cmdlets is presented as the default automation method, and no alternative for Linux users (e.g., Bash, curl, or Azure CLI) is provided. All portal instructions are platform-neutral, but the scripting/automation section is Windows-centric.
Recommendations
- Provide equivalent examples using Bash and curl for REST API operations.
- Include Azure CLI commands for password policy management, if available.
- Explicitly mention that PowerShell cmdlets can be run cross-platform, or clarify Windows-only requirements.
- Present scripting examples for both Windows (PowerShell) and Linux/macOS (Bash/curl) side by side.
- Add a note on how Linux/macOS users can install and use Microsoft Graph PowerShell, or suggest alternatives.
Active Directory B2C
Create & delete Azure AD B2C consumer user accounts in the Azure portal
...n/articles/active-directory-b2c/manage-users-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral except for the 'Revoke a consumer user's session' section, which exclusively provides instructions using Microsoft Graph PowerShell and explicitly references 'Windows PowerShell'. No Linux/macOS alternatives (such as Bash, CLI, or direct Graph API usage) are given, and the PowerShell approach is presented as the primary method.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using Microsoft Graph API via curl or HTTP requests.
- Mention that Microsoft Graph PowerShell is cross-platform and can be used in PowerShell Core on Linux/macOS, not just 'Windows PowerShell'.
- Include examples using Azure CLI or other platform-agnostic tools where possible.
- Avoid language that implies Windows is required (e.g., 'In your Windows PowerShell'), and use 'PowerShell' or 'terminal' instead.
Active Directory B2C
Tutorial to configure Azure Active Directory B2C with Jumio
...ob/main/articles/active-directory-b2c/partner-jumio.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of PowerShell for certificate creation and random string generation, with no mention of Linux/macOS alternatives. Windows-centric tools and workflows (e.g., Visual Studio, PowerShell) are referenced without parity for cross-platform users. Linux/macOS users are left to find their own methods for critical steps, such as certificate creation and key generation.
Recommendations
- Provide equivalent Linux/macOS commands for creating self-signed certificates (e.g., using openssl).
- Include examples for generating random strings on Linux/macOS (e.g., using openssl, pwgen, or /dev/urandom).
- Mention cross-platform deployment options in addition to Visual Studio, such as VS Code, Azure CLI, or GitHub Actions.
- Clarify any platform-specific requirements for certificate import/export and provide links to relevant Linux/macOS documentation.
- Present examples for both Windows and Linux/macOS side-by-side, or indicate which steps are platform-agnostic.
Active Directory B2C
Tutorial to configure Saviynt with Azure Active Directory B2C
.../main/articles/active-directory-b2c/partner-saviynt.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias in the section on enabling Saviynt to delete users. It exclusively instructs users to install and use the Microsoft Graph PowerShell module on a Windows workstation or server, provides only PowerShell commands, and does not mention or provide equivalent instructions for Linux or macOS environments. No alternative CLI or cross-platform options are discussed, and Windows tooling is assumed as the default.
Recommendations
- Provide equivalent instructions using Microsoft Graph CLI, Azure CLI, or REST API calls, which are cross-platform and work on Linux/macOS.
- Explicitly mention that the PowerShell module is available on Linux/macOS via PowerShell Core, and provide installation instructions for those platforms.
- Include example commands for Linux/macOS users, or clarify any platform-specific requirements.
- Reorder or parallelize examples so that Windows and Linux/macOS instructions are presented with equal prominence.