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 376-392 of 392 flagged pages
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/policy-keys-overview.md
.../articles/active-directory-b2c/policy-keys-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific command-line examples or tooling references (such as PowerShell or Windows tools), but it also does not include any Linux-specific examples or mention of Linux command-line tools. All instructions are given via the Azure Portal UI or Microsoft Graph API, which are platform-agnostic. However, the absence of any CLI or scripting examples (for either Windows or Linux) means there is a lack of parity for users who may prefer or require automation via shell scripts or Linux-native tools.
Recommendations
- Add examples for managing policy keys using cross-platform command-line tools, such as Azure CLI and Microsoft Graph API via curl or HTTPie, with explicit Linux and macOS shell examples.
- If scripting is discussed in future updates, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are provided.
- Mention that the Azure Portal and Microsoft Graph API are accessible from any operating system, and provide links to relevant CLI documentation for both Windows and Linux users.
- Include troubleshooting or automation tips that are relevant for Linux environments, such as using cron jobs for key rotation automation.
Create Pull Request
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md
...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation contains a subtle Windows bias by linking to further instructions for securing REST APIs with a URL that includes '?tabs=windows', suggesting that Windows-specific instructions are the default or primary guidance. There are no explicit Linux or cross-platform command-line examples, and the only referenced tab is 'windows'. However, the main content is generally platform-neutral and does not rely on Windows-only tools or PowerShell.
Recommendations
- Provide explicit Linux/macOS examples or instructions where platform-specific steps are referenced, especially in linked documentation.
- When linking to further documentation (e.g., for securing REST APIs), use a neutral or multi-tab link (such as '?tabs=linux' or a link to a tabbed page) to avoid suggesting Windows as the default.
- If there are command-line or scripting steps, include both Windows (PowerShell/CMD) and Linux/macOS (Bash) equivalents.
- Review all linked documentation to ensure Linux parity and that Linux users are not required to adapt Windows-specific instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation displays a mild Windows bias in the instructions for generating the Android signature hash for the redirect URI. The Windows command is presented first and uses Windows-specific environment variables and paths, while the Linux/macOS equivalent is labeled as 'iOS' and provided second. No PowerShell-specific examples, Windows-only tools, or missing Linux equivalents are present elsewhere in the documentation.
Recommendations
- Present platform instructions in parallel (e.g., 'For Windows', 'For Linux/macOS') rather than 'Windows first'.
- Label the non-Windows example as 'Linux/macOS' rather than 'iOS', since the command is for Android development on those platforms.
- Consider providing a brief explanation of environment variable differences between platforms.
- Where possible, provide cross-platform commands or clarify any platform-specific steps.
- Ensure parity in tool references and avoid implying Windows as the default development environment.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-user-data.md
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or tooling, but it also does not include any command-line or scripting examples at all. There is no explicit Windows bias, but the lack of concrete examples (such as PowerShell, Windows command line, Bash, or Linux tools) means Linux parity is not addressed. If future examples are added, care should be taken to include both Windows and Linux approaches.
Recommendations
- If adding code or command-line examples (e.g., using Microsoft Graph API), provide both PowerShell (Windows) and Bash/cURL (Linux/macOS) examples.
- Mention cross-platform tools (such as Azure CLI or REST API via cURL) before or alongside any Windows-specific tools.
- Explicitly state that the instructions apply equally to all platforms, or call out any platform-specific differences.
- If referencing scripts or automation, provide samples for both Windows and Linux environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides detailed instructions for registering a Microsoft Graph application in Azure AD B2C, but all steps are described exclusively via the Azure Portal (web UI) and do not include any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users, as no CLI (such as Azure CLI or Microsoft Graph CLI) or scripting examples are provided. This omission may disadvantage users who prefer or require command-line automation, especially on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI commands for all portal-based steps, such as application registration, permission assignment, and client secret creation.
- Provide Microsoft Graph CLI or REST API examples for registering applications and managing permissions.
- Include sample scripts (in Bash or cross-platform scripting languages) to automate the registration and configuration process.
- Explicitly mention that all steps can be performed via CLI on Linux/macOS, and link to relevant CLI documentation.
- Ensure that any automation guidance is not limited to Windows or PowerShell, but is accessible to users on all platforms.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-user-data.md
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or tooling, but it also does not include any command-line or scripting examples at all. This omission means there is no explicit Windows bias, but there is a lack of parity in that neither Windows (e.g., PowerShell) nor Linux (e.g., Bash/cURL) approaches are demonstrated. Readers are left without practical, platform-agnostic examples for interacting with the Microsoft Graph API.
Recommendations
- Add practical examples for deleting and exporting user data using both PowerShell (for Windows users) and Bash/cURL (for Linux/macOS users).
- Ensure that any command-line examples are provided in both Windows and Linux formats, or use platform-agnostic tools where possible.
- Explicitly mention that the Microsoft Graph API can be accessed from any OS, and link to relevant SDKs or CLI tools for different platforms.
- If using screenshots or UI walkthroughs, ensure they are not Windows-specific or provide Linux/macOS equivalents.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/custom-policies-series-store-user.md
...ive-directory-b2c/custom-policies-series-store-user.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples, tools, or patterns. However, it assumes the use of Visual Studio Code (VS Code) as a prerequisite without mentioning Linux-specific alternatives or considerations. There are no OS-specific instructions, scripts, or screenshots, and no mention of PowerShell or Windows-only tools. The documentation is largely platform-neutral but lacks explicit Linux parity guidance or examples.
Recommendations
- Explicitly state that Visual Studio Code is cross-platform and provide installation links or instructions for Linux and macOS users.
- Mention that all XML editing and Azure portal steps can be performed on Linux, macOS, or Windows.
- If any command-line or scripting steps are added in the future, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) examples.
- Include a note clarifying that the process is OS-agnostic and does not require Windows.
- If screenshots are used, consider including examples from both Windows and Linux environments, or use neutral browser-based screenshots.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples or tool references (such as PowerShell or Windows-specific tools). However, it is biased toward GUI-based instructions via the Azure Portal and does not provide any CLI-based examples (such as Azure CLI, Bash, or scripting), which are commonly used on Linux and cross-platform environments. There are no instructions or examples for performing these tasks using command-line tools that are available and popular on Linux.
Recommendations
- Add equivalent instructions for registering applications, granting permissions, and creating client secrets using the Azure CLI (az commands), which is cross-platform and widely used on Linux.
- Provide sample scripts or command-line snippets for automating these tasks in Bash or shell environments.
- Explicitly mention that all steps can be performed via CLI and link to relevant CLI documentation.
- Ensure parity by including both portal (GUI) and CLI/script-based workflows in all sections where management actions are described.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) version, with no explicit mention of Linux. No other sections show Windows-specific tools, PowerShell, or missing Linux examples.
Recommendations
- Explicitly mention Linux alongside iOS/macOS for Unix-like environments in the signature hash generation step (e.g., 'For Linux/macOS:').
- Consider presenting cross-platform or Linux instructions before or alongside Windows instructions to avoid the impression of Windows primacy.
- Where possible, clarify that the non-Windows command works for both Linux and macOS, not just iOS.
- Review other documentation pages linked from this one to ensure Linux parity in all prerequisite and follow-up steps.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/authorization-code-flow.md
...ticles/active-directory-b2c/authorization-code-flow.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is largely platform-neutral, focusing on HTTP requests and OAuth 2.0 protocol details. However, there is a subtle Windows bias in the suggestion to use 'Microsoft PowerShell' as an example HTTP client for testing POST requests, without mentioning Linux or cross-platform alternatives such as curl or HTTPie. No PowerShell-specific scripts or Windows-only tools are shown, but the only tool recommendation is Windows-centric.
Recommendations
- When suggesting HTTP clients for testing, mention cross-platform tools such as 'curl' or 'HTTPie' alongside or before 'Microsoft PowerShell'. For example: 'If you're testing this POST HTTP request, you can use any HTTP client such as curl, HTTPie, or Microsoft PowerShell.'
- If providing example command-line invocations, include both Windows (PowerShell) and Linux/macOS (bash/curl) examples where appropriate.
- Ensure that any tool recommendations or example commands are either cross-platform or that platform-specific alternatives are provided in parity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md
...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation contains a subtle Windows bias by linking to API protection instructions that default to Windows-specific guidance. Specifically, the link to 'secure-rest-api.md?tabs=windows&pivots=b2c-custom-policy#using-oauth2-bearer' uses the 'windows' tab by default, potentially leading users to Windows-centric instructions before Linux equivalents. However, the main content, code samples, and configuration steps are platform-agnostic and do not reference Windows-only tools or PowerShell.
Recommendations
- Update documentation links to use a neutral or platform-agnostic tab (e.g., 'tabs=linux' or omit the tab parameter) when referencing external guides, or explicitly mention that Linux and macOS instructions are available.
- Wherever platform-specific instructions are referenced, provide clear navigation or callouts for both Windows and Linux/macOS users.
- Review linked documentation to ensure Linux and macOS parity, and consider including direct links to Linux/macOS instructions alongside Windows links.
- Add a short note in the prerequisites or relevant sections stating that all steps can be performed on Windows, Linux, or macOS, and provide links to platform-specific setup guides if needed.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) equivalent. There are no explicit Linux examples, but the iOS command uses Unix-style paths and syntax, which is applicable to Linux/macOS. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found elsewhere in the document.
Recommendations
- Explicitly mention Linux alongside iOS when providing Unix-like command examples, or provide a separate 'For Linux/macOS' heading.
- Present Windows and Linux/macOS commands together, or alternate which platform is shown first to avoid the appearance of prioritizing Windows.
- Where possible, clarify that the Unix-style command works for both Linux and macOS, not just iOS.
- Consider adding a short note or table summarizing the equivalent commands for Windows, Linux, and macOS to improve clarity and parity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/b2c-global-identity-proof-of-concept-regional.md
...y-b2c/b2c-global-identity-proof-of-concept-regional.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation contains a subtle Windows bias by linking to further instructions for securing REST APIs with a URL that explicitly includes a 'tabs=windows' query parameter. This suggests that the default or primary guidance is for Windows environments, with no mention or example for Linux or cross-platform scenarios. No PowerShell-specific commands or Windows-only tools are present, but the reference to Windows-first documentation may disadvantage Linux users.
Recommendations
- Provide explicit Linux (and macOS) instructions or links alongside Windows instructions for securing REST APIs and obtaining tokens.
- Use neutral or cross-platform documentation links (e.g., avoid hardcoding 'tabs=windows' in URLs) or clearly indicate how to switch to Linux/macOS tabs.
- Wherever platform-specific steps are referenced, include a note or table summarizing differences and parity between Windows and Linux environments.
- Audit linked documentation to ensure Linux users are not left without equivalent guidance.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias in the section on generating a development signature hash for the redirect URI. The Windows command is presented first, followed by the iOS (Unix-like) equivalent, but there is no explicit mention of Linux or macOS. The rest of the documentation is platform-agnostic, focusing on Android Studio and Java/Kotlin code, with no other Windows-specific tools or patterns.
Recommendations
- Explicitly mention Linux/macOS alongside iOS in the signature hash generation step, as the command is the same for all Unix-like systems.
- Label the command as 'For Linux/macOS' instead of 'For iOS', or use 'For Linux/macOS/iOS' to be inclusive.
- Consider presenting both Windows and Linux/macOS commands together, or in parallel tabs, to avoid implying Windows is the primary or default environment.
- Review other documentation pages for similar patterns and ensure parity in platform instructions.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/microsoft-graph-get-started.md
...es/active-directory-b2c/microsoft-graph-get-started.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not exhibit explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it exclusively describes GUI-based steps using the Azure portal and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell) for registering applications or granting permissions. This omission results in a lack of parity for Linux or cross-platform users who may prefer or require CLI-based automation.
Recommendations
- Add Azure CLI examples for all major steps (registering the application, granting permissions, assigning roles, creating client secrets) alongside the portal instructions.
- Explicitly mention that all operations can be performed via CLI and provide links to relevant Azure CLI documentation.
- If PowerShell examples are added, ensure equivalent Azure CLI (Bash-friendly) examples are also present and given equal prominence.
- Consider including a table or section comparing portal, Azure CLI, and PowerShell approaches for each task to support all user environments.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/enable-authentication-android-app.md
...ive-directory-b2c/enable-authentication-android-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides platform-specific instructions for generating a development signature hash, listing the Windows command first and labeling the next as 'For iOS' (though it is actually the Unix/Linux equivalent). No explicit Linux example is given, and the Windows command is prioritized, which may imply a Windows-first bias.
Recommendations
- Label the Unix command as 'For Linux/macOS' instead of 'For iOS', since the command is for the shell and applies to both Linux and macOS environments.
- Present both Windows and Linux/macOS commands together, or list Linux/macOS first or equally, to avoid implying Windows is the default or primary environment.
- Explicitly mention Linux as a supported development environment in the relevant sections.
- Consider providing a table or side-by-side code blocks for Windows and Linux/macOS commands for parity and clarity.
Active Directory B2C
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/manage-user-data.md
...main/articles/active-directory-b2c/manage-user-data.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, scripts, or tooling, but also does not mention or demonstrate how to perform the described operations (such as calling Microsoft Graph API) from any platform, including Windows or Linux. There is an implicit bias in that no cross-platform command-line or scripting examples (such as curl, bash, PowerShell, or CLI tools) are provided, which may leave Linux users without clear guidance.
Recommendations
- Add explicit examples for calling the Microsoft Graph API using cross-platform tools such as curl or HTTPie, which work on both Linux and Windows.
- If scripting examples are provided in the future, ensure both PowerShell (Windows) and bash (Linux/macOS) examples are included.
- Mention and link to platform-agnostic tools (e.g., Azure CLI, Microsoft Graph CLI) where possible.
- Clarify that the described API operations can be performed from any OS, and provide sample commands for both Windows and Linux environments.