Scan Details - Linux-first Docs for Azure

1644

Pages Scanned

30

Pages Flagged

1644

Changed Pages

1.8%

% Pages Flagged

Scan Information

Started At: 2025-09-13 00:00:06

Finished At: 2025-09-13 00:33:46

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI), REST API, Bicep, and ARM templates for configuration, without providing any command-line examples (such as Azure CLI, PowerShell, Bash, or scripting) that would be directly relevant to Linux users. There are no Linux-specific instructions or examples, and the documentation does not mention or demonstrate cross-platform command-line tools. The workflow assumes use of the Azure portal or ARM/Bicep templates, which are platform-agnostic in theory but are often associated with Windows-centric workflows. No PowerShell-specific bias is present, but the absence of Azure CLI or Bash examples is notable.

Recommendations:

Add Azure CLI examples for all configuration steps (e.g., creating loggers, enabling diagnostics), as Azure CLI is cross-platform and widely used on Linux.
Include Bash script snippets for REST API calls, demonstrating how to perform the same operations from a Linux shell.
Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide parity in instructions for each platform where relevant.
If referencing the Azure portal, clarify that it is accessible from any OS, but supplement with command-line alternatives for automation and scripting.
Where ARM/Bicep templates are shown, provide deployment instructions using Azure CLI (az deployment group create ...) rather than assuming portal usage.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides PowerShell-only examples for disabling certificate chain validation, with no equivalent CLI, Bash, or Linux-native instructions. The use of PowerShell cmdlets (New-AzApiManagementBackend, Set-AzApiManagementBackend) assumes a Windows environment or requires extra setup on Linux. There are no examples using Azure CLI, REST with curl, or other cross-platform tools.

Recommendations:

Add equivalent examples using Azure CLI (az apim), which is cross-platform and commonly used on Linux/macOS.
Provide REST API examples using curl or httpie to demonstrate how to perform the same actions without PowerShell.
Explicitly mention that PowerShell can be installed on Linux/macOS, or link to installation instructions if PowerShell is the only option.
Ensure that all code snippets are accompanied by both Windows/PowerShell and Linux/Bash/Azure CLI alternatives where possible.
Review the documentation for any other Windows-centric terminology or screenshots and provide Linux-agnostic alternatives.

Create pull request

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 or cross-platform alternatives (such as curl or HTTPie). No Linux-specific or cross-platform command-line examples are provided, and the only tool explicitly referenced is Windows-centric.

Recommendations:

Include examples using cross-platform tools such as curl or HTTPie for making HTTP requests.
When suggesting tools for testing, mention both PowerShell and common Linux/macOS tools (e.g., 'You can use any HTTP client such as curl, HTTPie, or Microsoft PowerShell').
Provide sample command-line invocations for both Windows (PowerShell) and Linux/macOS (bash/curl) environments.
Avoid mentioning Windows tools exclusively or first; present cross-platform options or alternate between platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page focuses exclusively on configuring Azure AD B2C authentication via the Azure Portal UI and does not provide any OS-specific command-line examples. However, it implicitly assumes the use of Azure Web Apps, which are often managed via Windows-centric tools and patterns. There are no explicit examples or instructions for Linux environments, CLI usage, or cross-platform automation (e.g., Azure CLI, Bash scripts). There is also no mention of Linux-specific considerations or parity in deployment or configuration steps.

Recommendations:

Add Azure CLI examples for all configuration steps, including app registration, secret creation, and authentication provider setup, to ensure Linux and cross-platform parity.
Include Bash shell command examples for retrieving and using tokens, in addition to any future PowerShell or Windows command-line examples.
Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant cross-platform tooling documentation.
If screenshots or UI steps are shown, clarify that the Azure Portal is web-based and OS-agnostic, and provide alternative instructions for headless or automated environments.
Highlight any OS-specific caveats or differences, if they exist, especially for developers deploying from Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on ASP.NET and .NET tooling (Visual Studio, Visual Studio Code, .NET SDK) without mentioning Linux-specific instructions or considerations. While Visual Studio Code and .NET Core are cross-platform, the documentation does not provide explicit Linux (or macOS) setup or run instructions, nor does it address common Linux-specific issues (such as file permissions, path separators, or HTTPS certificate setup). The example redirect URI uses a Windows-style localhost port, and there is no mention of Linux package managers or terminal commands beyond 'git clone'.

Recommendations:

Add explicit instructions for running the sample on Linux (e.g., using the dotnet CLI, installing .NET SDK via apt/yum/pacman, handling HTTPS development certificates).
Include Linux/macOS-specific notes for opening the project (e.g., using 'code .' in the terminal, or 'dotnet run' instead of relying on Visual Studio).
Mention any platform-specific prerequisites or troubleshooting tips (such as setting executable permissions, or dealing with case-sensitive file systems).
Provide example commands for both Windows and Linux environments where relevant.
Clarify that the instructions are cross-platform and highlight any differences users might encounter on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is heavily focused on ASP.NET Core and Visual Studio/Visual Studio Code workflows, which are most commonly associated with Windows development. While the .NET CLI commands are cross-platform, the only alternative package installation example uses Install-Package, which is a PowerShell/NuGet Package Manager Console command specific to Windows/Visual Studio. There are no explicit Linux or macOS instructions, terminal examples, or mentions of Linux-specific environments or tools. The documentation implicitly assumes a Windows development environment and omits guidance for Linux users.

Recommendations:

Ensure all command-line examples use the .NET CLI (dotnet) commands, which are cross-platform, and avoid Windows-specific commands like Install-Package unless also providing Linux/macOS equivalents.
Explicitly mention that the instructions work on Windows, Linux, and macOS, and provide any necessary notes for Linux/macOS users (e.g., file path separators, prerequisites, or environment setup).
Include a section or callout for Linux/macOS users, highlighting any differences in project setup, running, or debugging.
Where Visual Studio is referenced, also mention Visual Studio Code and command-line workflows as equally valid, and provide links to official .NET documentation for Linux/macOS development.
If screenshots or UI walkthroughs are included elsewhere, ensure parity by showing Linux/macOS environments as well as Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references the Azure portal web UI for configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). There is no mention of Linux-specific tools or workflows, nor are there any cross-platform command-line instructions. The implicit assumption is that users will interact with the Azure portal via a web browser, which is cross-platform, but there is a subtle 'windows_first' bias in the absence of CLI or automation examples that are popular in Linux environments.

Recommendations:

Add Azure CLI examples for all configuration steps, including app registration, secret creation, and identity provider setup.
Where relevant, provide both PowerShell and Bash (or Azure CLI) scripts to ensure parity for Linux and Windows users.
Explicitly mention that all portal steps can be performed from any OS with a supported browser, but highlight automation options for Linux users.
Include references to documentation for automating these tasks using cross-platform tools.
Ensure that any downloadable scripts or code samples are provided in both Windows and Linux-friendly formats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page lists a variety of code samples for integrating Azure AD B2C across multiple platforms and languages. However, in the desktop application section, only a Windows Desktop .NET (WPF) sample is provided, with no equivalent Linux or cross-platform desktop sample. Additionally, .NET samples are prominently featured and listed first in several sections, which may give the impression of a Windows-first approach.

Recommendations:

Add cross-platform desktop application samples (e.g., using .NET MAUI, Electron, or Qt) that run on Linux and macOS, not just Windows.
Explicitly note platform compatibility for each sample, and provide Linux/macOS instructions or alternatives where possible.
Balance the order of presentation so that non-Windows and cross-platform samples are not consistently listed after Windows/.NET samples.
Where .NET is used, clarify if the sample is Windows-only or cross-platform (e.g., .NET Core vs. .NET Framework).
Consider adding shell/bash scripts or Linux-specific setup instructions where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by mentioning Windows Hello as the primary example of biometric authentication, both in the introduction and in the scenario walkthrough. Windows Hello is referenced before any mention of biometric options on other platforms, and there are no explicit Linux or macOS examples or tool mentions. The documentation does not provide parity in describing how Linux users might enroll or use biometric authentication, nor does it mention Linux-compatible biometric solutions.

Recommendations:

Include explicit examples of biometric authentication on Linux (e.g., fingerprint readers using fprintd, or FaceID alternatives).
Mention macOS biometric options (such as Touch ID or Face ID) alongside Windows Hello.
Rephrase scenario walkthroughs to present platform options in a neutral order, or provide parallel examples for Windows, Linux, and macOS.
Add troubleshooting or setup notes for Linux and macOS users regarding biometric enrollment and compatibility.
Reference cross-platform biometric standards (such as FIDO2/WebAuthn) and how they are supported on different operating systems.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing the Azure Portal (a web-based GUI) and providing XML/PowerShell-style configuration snippets without mentioning or providing examples for Linux command-line tools or workflows. There are no references to Linux-specific tools, shell commands, or alternative approaches for Linux administrators. The instructions assume a GUI-based workflow, which is more common among Windows users, and do not address parity for Linux environments.

Recommendations:

Include CLI-based instructions using Azure CLI (az), which is cross-platform and commonly used on Linux.
Explicitly mention that the Azure Portal is accessible from any OS, including Linux, to clarify that the steps are not Windows-specific.
Provide examples of editing XML files using common Linux tools (e.g., nano, vim) and uploading them via CLI or REST API, not just through the portal.
If PowerShell is referenced, also provide Bash or shell script equivalents for Linux users.
Add a section or callout for Linux/macOS users, highlighting any differences or confirming that the process is OS-agnostic.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits subtle Windows bias by referencing SAML application registration with a link that includes '?tabs=windows', suggesting Windows-specific instructions or defaults. There are no explicit Linux or cross-platform examples or tabs mentioned, and no mention of Linux tools or equivalents. This may lead Linux users to feel secondary or unsupported.

Recommendations:

Ensure that all platform-specific instructions (such as for SAML apps) provide both Windows and Linux (and macOS, if relevant) tabs or examples.
Avoid defaulting to Windows tabs or instructions; instead, present a neutral or platform-agnostic default, or clearly offer platform selection.
Explicitly mention cross-platform tools or provide parity in examples for Linux environments where applicable.
Review linked pages (such as the SAML application guide) to verify that Linux instructions are present and as detailed as Windows instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively references the Azure portal (a web-based GUI) and Microsoft Entra ID for OAuth 2.0 configuration, with all step-by-step instructions and screenshots based on the Azure portal interface. There are no command-line examples (such as Azure CLI, PowerShell, Bash, or REST API), nor are there references to Linux-native tools or workflows. The documentation assumes use of the Azure portal, which is platform-agnostic but is often associated with Windows-centric workflows. No Linux-specific or cross-platform command-line instructions are provided.

Recommendations:

Add equivalent instructions using Azure CLI (az) commands for all steps involving app registration, permission assignment, and OAuth configuration. Azure CLI is cross-platform and works natively on Linux.
Provide REST API examples for automation scenarios, which are platform-neutral.
Include references or links to documentation for configuring OAuth 2.0 with non-Microsoft providers, or at least mention that the steps may differ for other providers.
Explicitly state that all steps can be performed from any OS via the Azure portal, and highlight any platform-specific considerations if they exist.
Where screenshots or UI navigation are shown, consider supplementing with command-line equivalents for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains cross-platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows path (%SystemDrive%\drivers\etc\hosts) is mentioned before the Linux/macOS path (/etc/hosts). Additionally, a related link points to a Windows 2000 Server DNS article, further emphasizing Windows-centric resources.

Recommendations:

When referencing file paths or system locations (such as the hosts file), list Linux/macOS and Windows paths together or alternate their order to avoid 'Windows first' bias.
Provide links to cross-platform or Linux/macOS-specific DNS configuration documentation, not just Windows resources.
Where possible, include examples or references for both Windows and Linux tools/utilities when discussing system configuration steps.
Audit related content and external links to ensure they are not disproportionately focused on Windows, especially when the topic is broadly applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a mild Windows bias by requiring Visual Studio Code (VS Code) to be installed on 'your computer' without specifying cross-platform compatibility or alternatives. While VS Code is available on Windows, Linux, and macOS, the documentation does not explicitly acknowledge Linux or macOS users, nor does it mention any Linux-specific setup or tools. No command-line or scripting examples are given, so there is no overt PowerShell or Windows command bias. However, the implicit assumption of a Windows environment is present.

Recommendations:

Explicitly state that Visual Studio Code is available on Windows, Linux, and macOS, and provide links or instructions for installing it on each platform.
If any steps require OS-specific actions (such as file paths, uploading files, or running scripts), provide equivalent instructions for Linux and macOS users.
Mention that the Azure portal and policy upload process are platform-agnostic, and clarify that all steps can be performed from any supported OS.
If referencing tools or editors, consider mentioning popular Linux alternatives or command-line options where applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation shows 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. No Linux-specific example is given, but the iOS command is compatible with Linux/macOS. There are no other Windows-specific tools, PowerShell scripts, or patterns elsewhere in the document.

Recommendations:

Present command-line examples for Windows and Linux/macOS side by side, or use neutral headings such as 'On Windows' and 'On Linux/macOS' instead of 'For Windows' and 'For iOS'.
Explicitly mention that the 'iOS' command works for Linux/macOS, or provide a separate 'For Linux/macOS' section.
Consider providing a table or tabbed interface for platform-specific commands to ensure parity and clarity.
Review other documentation pages linked from this one to ensure Linux users are not left out in related setup or troubleshooting steps.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, scripts, or tooling, but it also does not include any command-line or automation examples at all. As such, there is a lack of parity in that neither Windows (e.g., PowerShell) nor Linux (e.g., Bash/cURL) approaches are shown. However, the absence of Linux-specific examples or mentions could be considered a subtle bias, as many Azure AD B2C and Microsoft Graph API guides tend to default to Windows/PowerShell unless otherwise specified.

Recommendations:

Add explicit examples for both Windows (PowerShell) and Linux/macOS (Bash/cURL) for interacting with the Microsoft Graph API to delete or export user data.
Include sample scripts or command-line invocations for both platforms, demonstrating how to authenticate and call the relevant Graph API endpoints.
Ensure that any references to tools or workflows are cross-platform, or provide alternatives where necessary.
Clarify in the documentation that the API operations can be performed from any OS, and provide links to SDKs or tools for multiple platforms.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not exhibit overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it exclusively relies on the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, which is cross-platform and commonly used on Linux/macOS). There are no Linux-specific or cross-platform automation examples, which may disadvantage users who prefer or require non-GUI, scriptable workflows, especially on Linux.

Recommendations:

Add Azure CLI examples for all major steps (application registration, permission assignment, role assignment, client secret creation), as Azure CLI is cross-platform and widely used on Linux.
Where possible, provide REST API or Microsoft Graph API examples (e.g., using curl or HTTP requests) for automation scenarios.
Explicitly mention that all steps can be performed using command-line tools on Linux/macOS, not just via the Azure Portal.
Consider including a section or callout for 'Command-line (CLI) instructions' alongside the portal-based instructions to ensure parity for Linux and automation-focused users.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧