Scan Details - Linux-first Docs for Azure

838

Pages Scanned

96

Pages Flagged

838

Changed Pages

11.5%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

20:48:59 Scan started

Scan Information

Started At: 2025-07-13 20:48:59

Finished At: In Progress

Status: cancelled

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates some Windows bias, particularly in the instructions for generating GUIDs (recommending PowerShell's 'new-guid' command first) and in scripting examples (PowerShell script is presented before cURL). Windows/PowerShell tools and patterns are mentioned or shown before their Linux/Unix equivalents, and there is no explicit mention of Linux-native methods for certain tasks.

Recommendations:

When instructing users to generate a GUID, provide both PowerShell (Windows) and Linux/macOS (e.g., 'uuidgen' command) options side by side.
Present scripting examples (PowerShell and cURL) in parallel or clarify that cURL is cross-platform and may be preferred on Linux/macOS.
Avoid listing Windows/PowerShell tools or commands before cross-platform or Linux-native equivalents; instead, present them together or in a platform-neutral order.
Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary command-line alternatives.
Consider including bash or shell script examples for common automation tasks, not just PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows development, specifically using WPF and Visual Studio. It assumes the use of Windows-only technologies and tools, such as WPF, Visual Studio, and .NET desktop development, without mentioning or providing alternatives for Linux or cross-platform scenarios. There are no instructions or examples for Linux users, nor any mention of equivalent Linux tools or frameworks.

Recommendations:

Add a section or note clarifying that WPF is Windows-only, and suggest cross-platform alternatives (e.g., Avalonia, MAUI) for Linux or macOS users.
Provide guidance or links for setting up and running the sample on Linux using cross-platform .NET and compatible UI frameworks.
Include instructions for using cross-platform IDEs (e.g., VS Code, JetBrains Rider) and command-line tools (e.g., dotnet CLI) instead of only Visual Studio.
Explicitly state the platform limitations and, where possible, provide parity examples or references for Linux environments.
Consider providing a separate Linux-focused sample or documentation page for desktop authentication with Azure AD B2C.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for testing the REST API, referencing Microsoft PowerShell as the HTTP client, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The documentation does not mention or show how to perform the same steps on non-Windows platforms, and Windows tools are referenced before any cross-platform alternatives.

Recommendations:

Provide equivalent Linux/macOS command-line examples using curl or HTTPie for testing the REST API.
When referencing PowerShell, clarify that it is available cross-platform, or provide both Windows (PowerShell) and Linux/macOS (bash/curl) examples side by side.
Mention and demonstrate the use of cross-platform tools (e.g., curl, wget, HTTPie) for making HTTP requests.
Avoid referencing Microsoft-specific tools exclusively or first; instead, present cross-platform options or alternate between platforms in examples.
Add a note that all steps can be performed on Linux/macOS, and specify any platform-specific considerations.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation exclusively uses PowerShell scripts and tasks for deploying Azure AD B2C custom policies, with no mention or examples of Bash, shell, or cross-platform scripting alternatives. All automation and pipeline steps assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS. The instructions and examples are Windows-centric, potentially excluding or confusing users working in non-Windows environments.

Recommendations:

Provide equivalent Bash or shell script examples for deploying policies, suitable for Linux/macOS agents.
Explicitly mention that PowerShell Core (pwsh) is cross-platform and provide instructions for using it on Linux/macOS, or clarify if Windows PowerShell is required.
Add a section or notes on how to adapt the deployment process for Linux-based Azure Pipeline agents, including any prerequisites or differences.
Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API calls via curl) in examples, or at least mention them as alternatives.
Ensure that all steps, including script creation and pipeline task configuration, include Linux/macOS-compatible instructions and screenshots where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias by presenting command-line instructions and examples in a way that implicitly assumes a Windows environment. Specifically, the use of 'powershell' syntax in the 'Run your SPA application' step, and the lack of explicit Linux/macOS terminal instructions or parity, may disadvantage non-Windows users. There are no references to Windows-specific tools, but the command shell instructions and examples are not cross-platform neutral.

Recommendations:

Provide explicit Linux/macOS equivalents for all command-line instructions, especially for running Node.js applications (e.g., 'node index.js' instead of 'npm ./index.js').
Use cross-platform neutral terminology such as 'terminal' or 'command line' instead of 'command shell', and avoid referencing 'powershell' unless necessary.
Where code blocks are labeled as 'powershell', ensure that equivalent 'bash' or 'sh' code blocks are also provided, or use unlabeled code blocks for commands that are identical across platforms.
Add a note or section clarifying that the instructions apply to Windows, Linux, and macOS, and highlight any platform-specific differences.
Consider including a table or sidebar with common command-line differences for Windows vs. Linux/macOS for Node.js app development.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows environments by providing only PowerShell examples for scripting and automation, referencing the Microsoft Graph PowerShell module exclusively, and omitting equivalent Linux or cross-platform command-line instructions. There are no CLI, Bash, or REST API examples tailored for Linux users, and no mention of how to perform these tasks outside of the Azure portal or PowerShell context.

Recommendations:

Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users, especially for tasks currently demonstrated with PowerShell.
Include REST API examples with curl commands to show how to interact with Microsoft Graph from any platform.
Mention cross-platform tools (such as Azure CLI or Microsoft Graph CLI) alongside PowerShell, and clarify that PowerShell Core is available cross-platform if relevant.
Reorder sections or add notes to ensure Linux/macOS options are presented equally and not as an afterthought.
Explicitly state when a step or tool is Windows-specific, and offer alternatives for other operating systems.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (e.g., Server Manager, AD FS Management), using only GUI-based instructions specific to Windows Server, and omitting any Linux or cross-platform alternatives for AD FS setup or management. There are no PowerShell or command-line examples, but all setup steps assume a Windows Server environment and do not mention or provide guidance for Linux-based AD FS alternatives or management approaches.

Recommendations:

Provide equivalent command-line (PowerShell and, where possible, cross-platform CLI) instructions for AD FS configuration, so that users can automate or script the process.
Acknowledge that AD FS is a Windows Server technology, but mention and link to any open source or cross-platform alternatives for federated identity (e.g., Keycloak, IdentityServer) and how they could be integrated with Azure AD B2C.
If possible, include a note or section for Linux users, clarifying that AD FS is not available on Linux, and suggest supported alternatives for similar scenarios.
Where GUI steps are described, offer PowerShell or REST API equivalents to improve automation and accessibility for non-Windows environments.
Reorder or supplement instructions to clarify platform dependencies early in the prerequisites section.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (Server Manager, AD FS Management snap-in, Event Viewer), providing only PowerShell command examples for configuration, and omitting any mention of Linux or cross-platform alternatives for AD FS management or troubleshooting. All step-by-step instructions assume a Windows environment, with no guidance for Linux administrators.

Recommendations:

Provide equivalent instructions or notes for environments where AD FS is accessed remotely or managed via non-Windows systems (e.g., via REST APIs, if available, or using cross-platform tools).
Include references to any available cross-platform AD FS management tools or clarify that AD FS is a Windows-only technology, but highlight how Linux administrators can interact with it (e.g., via browser-based management, remote PowerShell from Linux, or REST endpoints).
Where PowerShell is used, mention if and how PowerShell Core (pwsh) on Linux/macOS can be used, or provide alternative command-line examples if possible.
For certificate creation and management, include Linux-based commands (e.g., using OpenSSL) alongside Windows-centric instructions.
Explicitly state the Windows-only nature of certain steps, and provide guidance for mixed-environment teams (e.g., how a Linux admin can coordinate with a Windows admin for AD FS configuration).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias, particularly in the 'How-to guide' sections for generating cryptographic keys and certificates. All code examples for key and certificate generation use PowerShell and reference Windows-specific tools (e.g., New-SelfSignedCertificate). There are no equivalent examples or instructions for performing these tasks on Linux or macOS, and Windows tooling is mentioned exclusively and first. This may hinder Linux/macOS users from following the guide without additional research.

Recommendations:

Provide equivalent command-line examples for Linux (e.g., using openssl for key and certificate generation).
Explicitly mention cross-platform alternatives (e.g., bash scripts, openssl, or other widely available tools) alongside PowerShell/Windows examples.
Structure instructions so that Windows and Linux/macOS approaches are presented in parallel, or at least mention non-Windows options before or alongside Windows-specific tools.
Link to external resources or official documentation for Linux/macOS users on generating keys and certificates.
Clarify in each step if a tool or command is Windows-specific, and suggest alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing IIS (a Windows-only web server) as the example application for testing, and providing a link to IIS setup instructions. There are no equivalent examples or guidance for Linux-based web applications or servers (such as Apache or Nginx). The documentation does not mention or provide steps for Linux environments, nor does it reference Linux tools or patterns, which may limit accessibility for users deploying on non-Windows platforms.

Recommendations:

Provide parallel examples for Linux-based web applications (e.g., Apache, Nginx) alongside IIS.
Include setup instructions or references for deploying and testing with a Linux web server.
Mention Linux as a supported environment where applicable, and clarify any platform-specific steps.
Ensure that all prerequisite and configuration steps are platform-agnostic or have clear alternatives for both Windows and Linux users.
Reference Linux tools and commands where relevant, not just Windows-specific technologies.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias, primarily in the section on creating self-signed certificates, where only a PowerShell-based approach is referenced (via an include), and no Linux/macOS alternatives (such as OpenSSL) are mentioned. The rest of the documentation is largely platform-neutral, focusing on Azure Portal UI and XML configuration, but the lack of cross-platform command-line examples for certificate creation may disadvantage Linux/macOS users.

Recommendations:

Add explicit instructions or examples for creating self-signed certificates on Linux/macOS using OpenSSL, alongside the existing PowerShell/Windows approach.
Wherever PowerShell or Windows-specific tools are referenced, provide equivalent bash/OpenSSL or cross-platform alternatives.
In sections that reference uploading or generating certificates, clarify that certificates can be created on any OS and provide links or steps for common Linux/macOS workflows.
Review all included snippets (such as the referenced PowerShell module include) to ensure Linux parity or add a note directing users to alternative methods if only Windows is covered.
Consider a short table or callout summarizing certificate creation options for Windows (PowerShell), Linux (OpenSSL), and macOS (OpenSSL/Keychain), with links to official documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only a PowerShell script for programmatic access to audit logs, with no equivalent example for Linux or cross-platform environments (such as Bash/cURL or Python). The script assumes use of PowerShell and Windows-centric tooling, and the Azure Cloud Shell reference implicitly favors PowerShell. There is no mention of Linux-native tools or cross-platform scripting approaches, nor are Linux examples provided alongside the Windows/PowerShell example.

Recommendations:

Provide a Bash/cURL example for accessing the Microsoft Graph API to retrieve audit logs, suitable for Linux and macOS users.
Include a Python script example, which is cross-platform and widely used for automation.
Explicitly mention that the API can be accessed from any OS, and link to relevant SDKs or CLI tools (e.g., Microsoft Graph CLI, Azure CLI) that work on Linux.
When presenting scripts, offer both Windows (PowerShell) and Linux (Bash/cURL or Python) versions side by side.
Avoid language that implies PowerShell is the only or primary way to automate these tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific tools (Git Bash from Git for Windows), providing troubleshooting steps that rely on Visual Studio (a Windows-centric IDE), and omitting explicit Linux/macOS examples or alternatives. The only command-line examples are generic git commands, but the only tool mentioned by name is Git for Windows, and the only workaround for password encoding uses Visual Studio's Immediate Window, which is not available on Linux/macOS. No Linux or cross-platform alternatives are suggested for these steps.

Recommendations:

Explicitly mention and provide examples for Linux and macOS users, such as using the built-in terminal or common shells (bash, zsh) for git commands.
Replace or supplement the Visual Studio Immediate Window password encoding step with a cross-platform alternative, such as using Python, Node.js, or command-line tools (e.g., `python3 -c 'import urllib.parse; print(urllib.parse.quote("password"))'`).
List cross-platform Git tools (e.g., native git, GitHub CLI, etc.) and avoid suggesting only Windows-specific downloads.
Where screenshots or UI steps are shown, clarify that the process is the same across platforms or note any differences.
Add a section or callout for Linux/macOS users to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI-based alternative to the Azure Portal for uploading a CA certificate. There are no examples or mentions of equivalent Linux-friendly tools (such as Azure CLI or REST API usage) for this operation. The documentation implicitly assumes a Windows environment by referencing PowerShell exclusively, and does not provide parity for Linux or cross-platform users.

Recommendations:

Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include REST API examples (with curl or similar tools) for certificate management tasks, allowing users on any OS to automate these operations.
When mentioning PowerShell, also mention and provide examples for other platforms/tools in parallel, rather than exclusively or first.
Explicitly state that the PowerShell command is one option, and link to documentation for other methods (CLI, REST API) where available.
Review all command-line instructions to ensure Linux users are not excluded or required to use Windows-specific tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure PowerShell examples for command-line logger creation, with no equivalent Azure CLI, Bash, or Linux-native scripting examples. The PowerShell example is presented as the only imperative command-line method, and there is no mention of cross-platform tools or guidance for Linux/macOS users. This may hinder accessibility for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command-line snippets, especially for logger creation and management.
Explicitly mention that Azure CLI and PowerShell are both supported, and clarify cross-platform compatibility.
Where PowerShell is used, provide Bash or shell script alternatives for Linux/macOS users.
Review the order of example presentation to avoid always listing Windows/PowerShell first; consider parallel tabbed examples for PowerShell and CLI.
Include a note in the prerequisites or relevant sections about cross-platform tooling and links to Azure CLI documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows and Microsoft-centric tools and workflows. All examples and instructions are given exclusively through the Azure portal UI, which is typically accessed via a web browser but is deeply integrated with Microsoft Entra ID (formerly Azure AD) and does not mention or provide alternatives for Linux-based workflows, CLI tools, or non-Microsoft OAuth providers. There are no references to Linux command-line tools, cross-platform scripting, or open-source alternatives. The documentation assumes the use of Microsoft Entra ID and the Azure portal, both of which are most familiar to Windows users.

Recommendations:

Provide equivalent instructions using Azure CLI and/or PowerShell, and ensure Azure CLI examples are included (as it is cross-platform and widely used on Linux).
Include examples or references for configuring OAuth 2.0 with non-Microsoft providers (such as Okta, Auth0, or open-source solutions like Keycloak), and show how to obtain endpoints and credentials from those systems.
Add a section or callouts for Linux/macOS users, clarifying that all steps can be performed from any OS via the Azure portal, and explicitly mention any OS-specific prerequisites or differences.
Where possible, include curl or httpie command-line examples for API calls, token requests, or validation steps, to demonstrate parity for developers working in Linux environments.
Reference and link to documentation for cross-platform tools (e.g., Azure CLI, REST API) wherever the Azure portal is mentioned, to ensure users on all platforms have clear guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for command-line operations, without providing equivalent examples for Linux users (such as Azure CLI or REST API). No Linux or cross-platform command-line tools are mentioned, and the only automation examples are Windows-specific.

Recommendations:

Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include REST API examples where appropriate, since these are platform-agnostic.
When mentioning command-line tools, list Azure CLI and REST API before or alongside PowerShell to avoid implying Windows is the primary or only supported environment.
Add a note clarifying that all operations can be performed using Azure CLI or REST API, not just PowerShell.
Consider including bash shell script snippets for common tasks, to further support Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for creating custom roles, referencing Azure PowerShell before Azure CLI in tool lists, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux/macOS users. This may make it less accessible for users on non-Windows platforms.

Recommendations:

Add equivalent Azure CLI examples alongside PowerShell code blocks for all role management tasks.
When listing tools (Azure PowerShell, Azure CLI, REST API), alternate the order or mention Azure CLI first in some instances to avoid a 'Windows-first' impression.
Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
Consider including Bash script examples or cross-platform instructions where possible.
Review and update the 'ms.custom' metadata to reflect cross-platform parity, not just Azure PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, mentioning PowerShell before CLI, and omitting explicit Linux or cross-platform command-line examples. There is no mention of Linux-specific tools or guidance, and the examples and instructions assume a Windows-centric workflow.

Recommendations:

Ensure that Azure CLI examples are provided before or alongside Azure PowerShell examples, as CLI is cross-platform.
Explicitly mention that Azure CLI and Resource Manager templates are fully supported on Linux, macOS, and Windows.
Add Linux/macOS-specific notes or examples where relevant, especially for command-line operations.
Avoid listing PowerShell before CLI unless there is a technical reason; consider alternating order or grouping by platform.
Include screenshots or instructions from non-Windows environments (e.g., Azure CLI in a Linux terminal) to reinforce cross-platform parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias, particularly in its use of Azure PowerShell for all command-line examples and the exclusive reference to the Azure Portal (a web UI that is most familiar to Windows users). There are no equivalent examples using cross-platform tools such as Bash, curl, or Azure CLI, which are more common in Linux and macOS environments. The documentation does not mention or provide Linux-native workflows, and the only scripting examples are in PowerShell, a Windows-centric shell (despite its cross-platform availability, it is still less common on Linux).

Recommendations:

Provide equivalent examples using Bash and curl for token generation and API calls.
Include Azure CLI commands for relevant operations, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that PowerShell examples can be run on Linux/macOS, or provide installation instructions for PowerShell Core if required.
Where possible, use generic HTTP tools (e.g., curl, httpie) for API calls to demonstrate platform-agnostic workflows.
Balance the order of examples: present Linux/cross-platform examples before or alongside Windows/PowerShell examples.
Reference Linux/macOS environments in prerequisites and instructions, not just Windows/Portal-centric workflows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exclusively references Windows PowerShell cmdlets and provides only PowerShell-based examples for managing Azure API Management via Azure Automation. There is no mention of Linux-compatible tools, Bash, Azure CLI, or cross-platform scripting options. The focus on PowerShell and absence of Linux or cross-platform alternatives indicates a strong Windows bias.

Recommendations:

Include equivalent examples using Azure CLI, which is cross-platform and widely used on Linux.
Provide Bash script samples for managing Azure API Management via Azure Automation.
Mention and link to documentation for using Azure Automation with Python or other cross-platform scripting languages.
Clearly state that Azure Automation supports non-Windows runbooks and provide guidance for Linux users.
Ensure that references to PowerShell are balanced with references to other tools and languages where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is heavily oriented toward the Azure Portal and Power Platform GUIs, which are web-based and cross-platform, but it implicitly assumes a Windows-centric workflow by referencing Power Platform and Power Apps/Automate (which are most commonly used in Windows environments). There are no CLI, PowerShell, or Linux shell examples, nor is there mention of using Azure CLI or other cross-platform tools. Troubleshooting recommendations mention 'developer tools in your browser' and 'Application Insights', but do not provide parity for Linux command-line users or scripting approaches.

Recommendations:

Add Azure CLI and/or Azure PowerShell examples for configuring CORS policies, with explicit mention of cross-platform compatibility.
Include Linux shell (bash) command examples for relevant API calls or configuration steps.
Mention and provide examples for using cross-platform tools (e.g., Azure CLI) before or alongside GUI instructions.
Clarify that the steps can be performed from any OS, and provide links to documentation for Linux and macOS users.
If possible, provide automation scripts (e.g., bash, PowerShell Core) for bulk or repeatable CORS policy configuration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples for importing OpenAPI specifications using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric, though now cross-platform) and the explicit PowerShell example may indicate a Windows bias. The order of presentation (Portal, CLI, then PowerShell) is acceptable, but the documentation does not provide any Linux- or bash-specific guidance, troubleshooting, or examples beyond the CLI, nor does it mention Linux-specific considerations or tools. There are no missing Linux examples per se, but the presence of PowerShell-specific instructions and the lack of any Linux shell or scripting context may make the documentation feel more Windows-oriented.

Recommendations:

Explicitly state that Azure CLI commands are cross-platform and provide any Linux/macOS-specific notes if relevant (e.g., environment variable syntax differences).
Consider adding bash or shell script examples for Linux users, especially for scripting scenarios.
If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide equivalent bash examples where possible.
Mention any Linux-specific prerequisites or troubleshooting steps, if applicable.
Ensure parity in troubleshooting and advanced usage sections for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but it demonstrates a Windows bias by giving equal prominence to PowerShell (a Windows-centric tool), listing it immediately after CLI, and including detailed PowerShell setup instructions. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary automation method alongside CLI, despite CLI being more cross-platform. The prerequisites and examples do not mention or demonstrate Linux-native tools or workflows.

Recommendations:

Add explicit Bash or shell script examples for Linux users, especially for common automation scenarios.
Clarify that Azure CLI commands are fully cross-platform and can be run on Linux, macOS, and Windows.
De-emphasize PowerShell as a primary automation tool by listing Azure CLI first and PowerShell second, or by grouping PowerShell as an alternative for Windows users.
Include notes or sections on how to install and use Azure CLI on Linux, and link to Linux-specific setup guides.
If PowerShell is included, mention that PowerShell Core is available cross-platform, but provide native Bash alternatives where possible.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. It references Windows-specific tools and scenarios (such as KMS activation and Windows Update/Defender endpoints) without mentioning Linux equivalents or clarifying their relevance for non-Windows environments. Additionally, some linked content (e.g., VPN Gateway connections via PowerShell) suggests a Windows-first approach. There are no Linux-specific examples or guidance, and the documentation does not address how requirements differ for Linux-based deployments.

Recommendations:

Where Windows-specific endpoints or ports are mentioned (e.g., KMS activation, Windows Update, Windows Defender), clarify that these are only required for Windows VMs and note that Linux VMs do not require these settings.
Add a section or notes on Linux VM requirements, explicitly stating if any ports or endpoints are needed for Linux (e.g., for package updates or diagnostics), or confirm that no special configuration is needed.
When referencing tools or scripts (such as PowerShell), provide equivalent instructions or links for Linux environments (e.g., Azure CLI, Bash scripts).
Review related links and ensure parity by including Linux-focused or cross-platform documentation where available.
Consider adding a table or callout summarizing differences in network requirements between Windows and Linux VM scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a strong Windows bias by focusing exclusively on migration scenarios and tools for ASP.NET web apps running on Windows/IIS servers. All migration tools and examples are tailored for Windows environments, with repeated references to IIS, PowerShell scripts, and Windows-specific migration assistants. There is no mention of Linux-based .NET hosting environments, nor are there any Linux migration tools, examples, or guidance provided.

Recommendations:

Include migration scenarios and tools for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
Provide Linux-specific migration guidance and examples, such as using Bash scripts or Linux-native tools.
Mention and link to any available cross-platform or Linux-compatible migration assistants or scripts.
Balance the documentation by presenting both Windows and Linux migration paths, or clarify if only Windows is supported and provide alternatives for Linux users.
Add explicit notes about the current lack of Linux support (if applicable) and direct users to relevant resources for Linux-based .NET app migration.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, with more detail and GUI options than for Linux. PowerShell commands are used for connectivity testing, and some troubleshooting steps and GUI tools are only available for Windows. Linux instructions are present but sometimes less detailed, and Linux users are directed to CLI-only workflows, with some missing parity in troubleshooting examples.

Recommendations:

Present Linux and Windows instructions in parallel or in a more balanced order, rather than always listing Windows first.
Provide Linux equivalents for all troubleshooting steps, such as using 'nc' (netcat) or 'curl' for connectivity tests instead of only PowerShell's 'Test-NetConnection'.
Expand Linux installation and usage instructions to match the detail and clarity of Windows sections, including more screenshots or terminal outputs where appropriate.
Where GUI tools are only available on Windows, explicitly state this early and offer alternative Linux workflows or tools, possibly with example scripts.
Ensure all command-line examples (e.g., for testing connectivity, DNS resolution) are provided for both Windows (PowerShell/CMD) and Linux (bash), ideally side-by-side.
In troubleshooting sections, include Linux-native commands (e.g., 'nslookup', 'dig', 'nc', 'telnet') alongside Windows commands.
Review the order of presentation so that Linux users do not feel like an afterthought; consider alternating which OS is presented first in each section.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows using iisnode. All configuration examples, troubleshooting steps, and tool references are Windows-centric (e.g., node.exe, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell, IIS, and DLLs). There are no Linux or cross-platform equivalents provided, and Linux troubleshooting or deployment patterns are not mentioned.

Recommendations:

Add equivalent sections or links for Node.js on Azure App Service for Linux, including configuration and troubleshooting steps.
Provide Linux-based examples (e.g., using PM2, systemd, or NGINX instead of IIS/iisnode) alongside or before Windows examples.
Include Linux-specific file paths, error log locations, and diagnostic tools (such as journalctl, systemctl, or Linux shell commands).
Reference cross-platform Node.js debugging and profiling tools, and clarify which steps are Windows-only.
Clearly label Windows-specific content and provide navigation or pivots to Linux content where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides a server-level authorization example exclusively for Windows apps using IIS and web.config, with no equivalent example or guidance for Linux-based App Service apps. The section is labeled 'Windows apps only', and Linux users are told that 'Linux apps don't use IIS and can't be configured through web.config', but no alternative is offered. Additionally, the use of Kudu (which is available on both platforms) is described in the context of editing web.config, reinforcing a Windows-centric approach. There are no PowerShell-specific examples, but the overall pattern prioritizes Windows tooling and omits Linux parity.

Recommendations:

Add equivalent Linux guidance: Provide an example of how to implement server-level authorization for Linux-based App Service apps, such as using middleware in common frameworks (e.g., Node.js, Python, .NET Core) or via .htaccess for PHP.
Clarify cross-platform tooling: When mentioning tools like Kudu, clarify their availability and usage on both Windows and Linux App Service plans.
Balance examples: Where platform-specific configuration is discussed, ensure both Windows and Linux approaches are presented side by side, or clearly direct Linux users to appropriate resources.
Explicitly state limitations: If certain features are not available on Linux, explain why and suggest best practices or workarounds for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation provides a code example for generating the Apple client secret JWT using C# and the Microsoft.IdentityModel.Tokens NuGet package, which is primarily a Windows/.NET ecosystem tool. There are no equivalent examples or guidance for Linux users (e.g., using OpenSSL, Python, or Node.js). The documentation also references application settings and configuration in a way that assumes familiarity with Azure App Service patterns, which are more commonly managed via Windows-centric tooling. No Linux command-line or cross-platform code samples are provided.

Recommendations:

Add examples for generating the client secret JWT using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
Explicitly mention that the C# example is one of several possible approaches, and provide links or code snippets for Linux/macOS users.
Include command-line examples for managing application settings using Azure CLI (which is cross-platform), not just through the Azure portal.
Review the documentation to ensure that any references to tooling or libraries are balanced with Linux-friendly or cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily by recommending Azure Storage Explorer (a GUI tool with a Windows-first experience) for uploading files and generating SAS tokens, and by referencing instructions with a '?tabs=windows' parameter. There are no explicit Linux or cross-platform CLI alternatives provided for these steps, and no mention of Linux-native tools or workflows for managing storage or SAS tokens. All command-line examples use Azure CLI, which is cross-platform, but the critical file upload and SAS generation steps are described only via a Windows-centric GUI tool.

Recommendations:

Provide equivalent instructions for uploading files and generating SAS tokens using Azure CLI or AzCopy, both of which are cross-platform.
Avoid linking to documentation with '?tabs=windows' unless also providing Linux/macOS tabs or alternatives.
Mention that Azure Storage Explorer is available on Linux and macOS, or clarify its cross-platform support if referenced.
Include explicit Linux/macOS command-line examples for all steps currently described only via GUI or Windows-centric tools.
Consider reordering or parallelizing instructions so that CLI/cross-platform approaches are presented before or alongside Windows GUI methods.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. All runtime version examples reference Windows file paths and tools (Kudu CMD/PowerShell), with no mention of Linux equivalents or how to perform similar tasks in a Linux App Service environment. Visual Studio (a Windows-centric tool) is referenced as the primary publishing method, and there are no Linux shell or cross-platform examples for key tasks.

Recommendations:

Add equivalent instructions and examples for Linux-based App Service plans, including how to check .NET runtime versions and access environment variables in Linux containers.
Provide Linux shell (bash) commands where CMD/PowerShell commands are shown, or clarify when steps are Windows-only.
Mention and demonstrate cross-platform deployment tools (such as Azure CLI, GitHub Actions, or VS Code) alongside Visual Studio.
Clearly indicate which instructions apply only to Windows App Service plans and provide links or sections for Linux-specific guidance.
Include examples of accessing diagnostic logs and configuring app settings in Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Windows examples and terminology (such as IISNode, web.config, and PowerShell) are often presented first or exclusively, while Linux equivalents are sometimes less detailed or appear later. Some troubleshooting and configuration sections focus on Windows-specific tools or patterns (e.g., web.config, IISNode) without always providing Linux alternatives or parity in explanation. The Application Insights instrumentation section references PowerShell for automation but does not mention Bash or Linux CLI alternatives.

Recommendations:

Ensure that for every Windows-specific example (such as web.config, IISNode, or PowerShell instructions), a Linux equivalent (e.g., nginx config, PM2, Bash/CLI instructions) is provided with equal prominence and detail.
Alternate the order of Windows and Linux pivots or present both platforms side-by-side to avoid the perception of Windows-first bias.
Where PowerShell is mentioned for automation (e.g., enabling Application Insights), provide Bash or Azure CLI examples for Linux users.
Expand troubleshooting sections to include Linux-specific issues and solutions, not just Windows (e.g., what to do if the app fails to start due to missing startup commands or permissions in Linux containers).
When referencing tools like IISNode or web.config, clarify that these are Windows-only and provide explicit Linux alternatives (such as PM2 configuration or startup command guidance).
Review all sections for parity in depth and clarity between Windows and Linux instructions, especially in advanced configuration and debugging scenarios.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally provides parity between Windows and Linux by using platform pivots for most configuration tasks. However, there are notable signs of Windows bias: Windows instructions and tools (such as KuduScript and references to Windows paths) are often presented first, and some deployment automation examples (Composer, Bower, Gulp, Grunt) are only detailed for Windows, with no equivalent Linux scripting guidance. Windows-specific tools and patterns (e.g., Kudu, .dll extensions, Windows directory structures) are referenced more explicitly, while Linux alternatives are less detailed or missing.

Recommendations:

Provide Linux-specific examples for Composer, Bower, Gulp, and Grunt deployment automation, similar to the detailed Windows/KuduScript instructions.
Ensure that Linux instructions are presented with equal prominence and detail as Windows, especially for common developer workflows.
Avoid referencing Windows tools (like KuduScript) without mentioning or linking to Linux equivalents or alternatives.
When showing directory paths or file extensions, always provide both Windows and Linux formats side by side.
Consider alternating the order of Windows and Linux pivots or providing a neutral introduction before platform-specific sections.
Where a tool or workflow is only available on Windows, explicitly state this and suggest Linux alternatives if possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias in its automation section by providing a PowerShell script example but omitting equivalent Linux/bash scripting examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, while the Azure CLI is merely linked. There are no explicit Linux or cross-platform shell examples, and PowerShell is highlighted first and more prominently. Additionally, there are no references to Linux-specific tools or workflows elsewhere in the document.

Recommendations:

Provide inline Azure CLI/bash examples alongside PowerShell scripts in the automation section, ensuring both are equally visible.
Explicitly mention that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample bash scripts for Linux users.
Review the ordering of automation examples to avoid always listing PowerShell first; consider alternating or listing CLI/bash first where appropriate.
Add references or links to Linux-specific workflows or troubleshooting where relevant, such as certificate management or file paths.
Ensure screenshots and walkthroughs do not assume a Windows environment unless necessary, and clarify when steps are platform-agnostic.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it provides some cross-platform guidance (e.g., OpenSSL commands for certificate export), it references Windows-specific tools (IIS, Certreq.exe) without equivalent Linux alternatives, lists Azure PowerShell examples alongside Azure CLI but does not provide Bash or Linux-native scripting examples, and refers to Windows-specific scenarios in FAQs. Linux tools and workflows are either missing or mentioned after Windows options.

Recommendations:

When referencing Windows tools like IIS or Certreq.exe for certificate export, also provide equivalent Linux commands or tools (e.g., OpenSSL, certbot, or native Linux certificate management instructions).
Include Linux/Bash scripting examples for automation tasks, not just Azure CLI and PowerShell.
In FAQs and scenario explanations, clarify Linux support and provide Linux-specific guidance where features differ (e.g., outbound client certificate support in Linux containers).
Ensure that cross-platform tools (like OpenSSL) are presented as primary options, and avoid implying Windows tools are the default or preferred method.
Where PowerShell is used, provide Bash or shell script equivalents for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides detailed instructions and code samples for Azure PowerShell, which is primarily a Windows-centric tool, alongside Azure CLI. The PowerShell section is more elaborate, with step-by-step parameter preparation and resource manipulation, while the CLI section is brief. There are no Linux shell or Bash-specific examples, and the PowerShell approach is presented after the CLI but with more depth and context, indicating a bias toward Windows tooling and patterns.

Recommendations:

Add equivalent Bash or Linux shell examples for all CLI commands, including parameter preparation and validation steps.
Ensure that CLI and PowerShell sections are equally detailed, or provide parity in explanations and troubleshooting.
Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
If possible, provide examples using native Linux tools (such as curl or jq) for related tasks, or clarify when PowerShell is not required.
Consider reordering sections so that cross-platform tools (CLI) are featured before or with equal prominence to Windows-specific tools (PowerShell).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias in several ways: deployment examples and templates are primarily focused on ASP.NET (a Windows-centric technology), and the only explicit agent pool example for Web Deploy uses 'windows-latest'. The FAQ and troubleshooting sections reinforce that Web Deploy is only supported on Windows agents, without offering Linux alternatives or workarounds. There are no PowerShell scripts, but the overall pattern and tool selection (Web Deploy, IIS references) are Windows-centric. Linux deployment scenarios are not given equal prominence or detailed examples.

Recommendations:

Provide parallel examples for Linux-based deployments, especially for non-.NET stacks (Node.js, Python, Java).
Explicitly mention and demonstrate how to use Linux agents for all supported deployment types, including any limitations.
Where a feature is Windows-only (e.g., Web Deploy), offer alternative Linux-compatible deployment methods and document them with examples.
Balance the initial examples and templates to include at least one Linux-first scenario (e.g., Node.js on Linux App Service).
Clarify in the prerequisites and FAQ which features are cross-platform and which are Windows-specific, and link to Linux guidance where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While it provides Azure CLI and PowerShell instructions (which are cross-platform), it consistently lists PowerShell after CLI and includes a PowerShell-specific example. In the FTP client recommendations, Windows-centric tools (Visual Studio, WinSCP) are mentioned first, with only Cyberduck as a cross-platform option. There are no explicit Linux command-line FTP client examples (such as lftp, ncftp, or the standard ftp/sftp commands), nor are Linux desktop tools (like FileZilla or Nautilus) mentioned. No Linux shell (bash) scripting examples are provided for automation, and troubleshooting references (e.g., WinSCP documentation) are Windows-focused.

Recommendations:

Include Linux-native FTP/S client examples (e.g., lftp, ncftp, FileZilla) alongside or before Windows tools.
Add sample Linux shell (bash) commands for connecting and uploading via FTP/S.
When listing tools, alternate or balance the order (e.g., mention FileZilla and Cyberduck before WinSCP and Visual Studio).
Provide troubleshooting links or examples relevant to Linux users (e.g., command-line FTP troubleshooting, FileZilla documentation).
Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Consider including a section or callout specifically for Linux/macOS users, highlighting any OS-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by referencing Windows-specific UI patterns (e.g., 'Right click', folder navigation), and by omitting any explicit Linux or cross-platform command-line instructions for common developer tasks (such as file creation, package installation, or database access). Tools like Azure Data Studio and SQL query editors are mentioned generically, but no Linux-specific alternatives or CLI-based workflows are provided. There are no PowerShell-specific commands, but the overall workflow assumes a GUI and Windows-centric development environment.

Recommendations:

Provide equivalent Linux/macOS instructions for tasks such as creating files (e.g., using 'touch' or 'nano' in the terminal) and installing packages (e.g., using 'dotnet add package' CLI).
Include command-line examples for database access and management (e.g., using Azure CLI, sqlcmd, or Data Studio on Linux).
Avoid UI instructions that are Windows-specific (such as 'Right click') or supplement them with cross-platform alternatives.
Explicitly mention that all steps can be performed on Linux and macOS, and provide any necessary prerequisites or caveats.
Where GUI tools are referenced, note their cross-platform availability or suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary method alongside Azure CLI and portal, with detailed PowerShell-specific instructions and terminology. There are several references to 'local PowerShell terminal' and Windows-specific tools (e.g., Git Credential Manager dialog, MSBuild, node-gyp errors referencing Windows). There is a lack of explicit Linux/macOS terminal or shell examples, and troubleshooting sections reference Windows-specific errors and build tools before mentioning cross-platform equivalents.

Recommendations:

Add explicit Linux/macOS terminal instructions and examples, especially where PowerShell is referenced (e.g., 'In a local terminal' instead of 'In a local PowerShell terminal').
Include Bash or shell command alternatives for PowerShell cmdlets, or clarify which commands are cross-platform.
When mentioning tools like Git Credential Manager or MSBuild, also mention their Linux/macOS equivalents or note their cross-platform availability.
In troubleshooting, provide error messages and solutions relevant to Linux/macOS environments (e.g., native module build errors on Linux, authentication dialogs on macOS).
Ensure that CLI examples are presented before or alongside PowerShell, and avoid assuming Windows as the default environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows-style path separators in examples, and omitting explicit Linux/Bash command examples or Linux-specific instructions. The focus is on Windows deployment patterns and tools, with minimal mention of Linux environments beyond brief parenthetical notes.

Recommendations:

Provide Linux-specific examples alongside Windows ones, including file paths (e.g., /home/site/wwwroot) and deployment instructions.
Use platform-agnostic path notation or show both Windows and Linux paths in all relevant sections.
Include Bash or Linux shell command examples where Azure CLI is used, and clarify any differences in behavior or requirements between Windows and Linux App Service environments.
Explicitly mention Linux deployment nuances, such as directory permissions or differences in mounting ZIP packages.
Ensure troubleshooting and WebJob deployment sections address both Windows and Linux scenarios equally.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate generation and management, referencing Windows-specific certificate stores (Cert:\LocalMachine\Root), and explicitly stating that private client certificates are only supported from custom code in Windows code apps. There are no equivalent Linux or cross-platform instructions or examples, and Linux scenarios are not addressed.

Recommendations:

Provide equivalent Linux/bash examples for certificate generation (e.g., using openssl) and management.
Clarify the support matrix for private client certificates on Linux and other platforms, and offer workarounds or alternatives if possible.
Include instructions for verifying certificate installation on Linux (e.g., using the bash shell in Kudu or relevant Linux commands).
Avoid referencing only Windows certificate stores; mention Linux trust store locations and how to interact with them.
Structure examples so that both Windows and Linux users can follow along, ideally presenting both side-by-side or in a platform-agnostic way where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows some Windows bias, especially in the .NET and Python sections. Windows tools (Visual Studio, Azure PowerShell) are listed before cross-platform or Linux-native tools, and in some cases, Linux-specific examples are less prominent or missing. The .NET stack emphasizes Windows-centric development environments and tools, while Linux parity is stronger in Java, Node.js, and PHP sections.

Recommendations:

Ensure that for each stack, Linux-native tools (e.g., Azure CLI, VS Code, Bash) are listed before or alongside Windows tools (e.g., Visual Studio, PowerShell).
Provide explicit Linux examples and tabs for all quickstarts and tutorials, especially for .NET and Python stacks.
Avoid listing Windows-only tools (like Visual Studio or PowerShell) as the default or first option; instead, present cross-platform tools first.
Where possible, add parity in deployment and configuration instructions for both Windows and Linux environments.
Review the use of 'Windows' in tab names and links to ensure Linux options are equally visible and accessible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft-centric authentication libraries (MSAL, Microsoft.Identity.Web) and ASP.NET Core, which are most commonly associated with Windows development environments. There is repeated mention of Visual Studio and IDE integration, but no mention of Linux development tools, frameworks, or parity in local development scenarios. No Linux-specific examples, tools, or workflows are provided, and the documentation implicitly assumes a Windows/Visual Studio/ASP.NET Core context for advanced scenarios.

Recommendations:

Include examples and guidance for Linux-based development environments, such as using VS Code, JetBrains Rider, or command-line workflows.
Highlight cross-platform compatibility of authentication libraries and provide explicit instructions for Linux and macOS users.
Mention and link to documentation for configuring authentication in popular Linux web frameworks (e.g., Node.js/Express, Python/Flask or Django, Java/Spring Boot) when discussing code-based solutions.
Clarify that App Service authentication features are available regardless of the underlying OS and provide parity tables or notes where features differ.
Add local development setup instructions for Linux (and macOS) environments, including how to achieve single sign-on or local testing without Visual Studio.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell instructions and tooling first, referencing Visual Studio (a Windows-centric IDE) for initial setup, and relying on PowerShell modules for key steps. While an Azure CLI example is provided, the PowerShell approach is given primary placement, and there is no explicit mention of Linux or cross-platform development environments.

Recommendations:

Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
Include explicit notes or sections for Linux/macOS users, such as how to perform steps in Bash or with other common Linux tools.
Avoid assuming Visual Studio as the default development environment; mention alternatives like VS Code or command-line deployment.
Where PowerShell is used, clarify if it is supported on Linux/macOS (PowerShell Core), and provide equivalent Bash or shell commands if possible.
Add a brief section or callout confirming that all steps are supported on Linux and macOS, and link to any relevant platform-specific guidance.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page 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). There are no command-line examples provided, and the only tool referenced is Windows-centric. This may make Linux or macOS users feel unsupported or require them to infer how to perform the same actions on their platforms.

Recommendations:

When suggesting HTTP clients for testing, include cross-platform tools such as curl or HTTPie alongside PowerShell.
Provide explicit command-line examples using curl for making the POST request to obtain an access token.
If referencing PowerShell, clarify that it is available cross-platform, or provide both Windows and Linux/macOS instructions/examples.
Ensure that any tool recommendations or examples are inclusive of all major operating systems, not just Windows.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is generally platform-neutral, focusing on HTTP requests and OAuth 2.0 protocol details. However, there is a subtle Windows bias where Microsoft PowerShell is mentioned as an example HTTP client for testing POST requests, with no mention of Linux or cross-platform alternatives. Additionally, the only specific tool mentioned for making HTTP requests is PowerShell, which is primarily associated with Windows, and it is mentioned before any Linux or cross-platform equivalents.

Recommendations:

When suggesting HTTP clients for testing, mention cross-platform and Linux tools such as curl, HTTPie, or Postman alongside or before PowerShell.
Provide example commands using curl or HTTPie to demonstrate how to perform the HTTP requests on Linux and macOS systems.
Explicitly state that any HTTP client can be used, and provide at least one example for both Windows (PowerShell) and Linux/macOS (curl).
Avoid implying that PowerShell is the default or only tool for these tasks, and ensure parity in tool recommendations across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally provides cross-platform instructions, with separate command examples for Linux, macOS, and Windows. However, there is evidence of subtle Windows bias: (1) The instruction to extract the sample to a folder with a path length of 260 or fewer characters references a Windows-specific limitation without clarifying that this is not relevant on Linux/macOS; (2) The Windows command examples use 'py' instead of 'python', which is a Windows launcher, and this is presented after Linux/macOS, but the path length warning is not platform-scoped.

Recommendations:

Clarify that the 260-character path length limitation applies only to Windows, and is not relevant for Linux/macOS users.
Consider providing a brief note about the 'py' launcher being specific to Windows, and that 'python' is the standard command on Linux/macOS.
Where platform-specific limitations or tools are mentioned, explicitly scope them to the relevant OS to avoid confusion.
Continue to provide parity in command examples for all major platforms, and ensure that any warnings or notes are clearly attributed to the appropriate OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio (a Windows-centric IDE) before Visual Studio Code, and by using a sample configuration (e.g., redirect URI to https://localhost:44316) that aligns with default Windows/IIS Express ports. There are no explicit Linux or cross-platform instructions, nor are there terminal or deployment examples for Linux environments. The documentation does not mention Linux-specific tools, commands, or troubleshooting steps, and does not address potential differences in file paths or environment setup for Linux users.

Recommendations:

Explicitly mention Linux and macOS as supported platforms in the prerequisites, and provide guidance for installing .NET SDK and running ASP.NET Core apps on those systems.
Include Linux/macOS-specific instructions for extracting the sample, running the app (e.g., using the dotnet CLI), and troubleshooting common issues (such as port conflicts or permissions).
Provide examples of configuring the redirect URI for common Linux development environments (e.g., using ports commonly available on Linux, or referencing Kestrel rather than IIS Express).
Add notes about differences in file paths, environment variables, and permissions between Windows and Linux/macOS.
Where Visual Studio is mentioned, clarify that Visual Studio Code and the dotnet CLI are fully supported on Linux/macOS, and provide parity in example steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a subtle Windows bias by referencing Visual Studio as the primary IDE and not providing explicit Linux instructions or examples for running the sample application. While Visual Studio Code is mentioned (which is cross-platform), there are no Linux-specific setup or troubleshooting notes, and the workflow assumes a Windows-like environment (e.g., path length limitations, default use of localhost ports, and Visual Studio usage). There are no PowerShell or Windows command-line examples, but the absence of Linux-specific guidance or parity in tooling is notable.

Recommendations:

Explicitly mention Linux as a supported development environment in the prerequisites.
Provide Linux-specific instructions for installing .NET SDK, running the sample app, and handling common issues (such as port binding or file permissions).
Include example commands for running the application from the terminal (e.g., using `dotnet run`) in addition to or instead of relying on Visual Studio/VS Code UI.
Clarify any platform-specific considerations (such as path length limits, which may differ on Linux).
If screenshots are included, provide examples from both Windows and Linux environments where relevant.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on ASP.NET Core and C# code, which are most commonly associated with Windows development environments. There are no examples or instructions for Linux or cross-platform development environments, nor are there mentions of Linux-specific tools or deployment patterns. The documentation assumes the use of Visual Studio project structures and .NET conventions, which may not be as familiar or accessible to Linux-first developers.

Recommendations:

Add explicit notes or sections on how to perform the same configuration and development steps on Linux, including using .NET Core/ASP.NET Core on Linux.
Provide command-line examples (e.g., using dotnet CLI) for project setup, configuration, and running the application, which are platform-agnostic.
Mention and link to cross-platform development tools (such as VS Code, JetBrains Rider, or the dotnet CLI) alongside or instead of Windows-centric tools.
Clarify that the instructions and code samples are applicable on both Windows and Linux, and highlight any platform-specific considerations.
Include troubleshooting tips or environment setup instructions for Linux users, such as installing the .NET SDK on Ubuntu or other distributions.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation is largely platform-neutral, focusing on XML configuration and SAML protocol details. However, in the 'Debug SAML protocol' section, the recommended tools for debugging SAML flows include browser extensions for Chrome and Firefox, but the only OS-specific developer tools mentioned are 'Microsoft Edge or Internet Explorer developer tools', with a link to a Microsoft blog. There is no mention of Linux-native tools or command-line utilities for SAML debugging, and the order of mention puts Microsoft/Windows tools last but still includes them exclusively as the only OS-specific developer tool. No PowerShell or Windows command-line examples are present, but the lack of Linux-specific tool recommendations is a subtle form of Windows bias.

Recommendations:

Add recommendations for Linux-native SAML debugging tools, such as 'SAMLtool' (https://www.samltool.com/) or command-line utilities like 'curl' and 'xmlsec1' for inspecting and signing SAML messages.
Mention that browser-based tools (Chrome/Firefox extensions) are cross-platform and highlight this fact for Linux and macOS users.
If referencing developer tools, include instructions or links for using browser developer tools on Linux and macOS, not just Microsoft Edge/IE.
Consider including a note that all XML configuration steps are OS-agnostic and can be performed on any platform.
If any scripts or automation are added in the future, provide both Windows (PowerShell) and Linux (bash/shell) examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by referencing Visual Studio Code and its Azure Functions extension as the primary development environment, and by using terminology like 'command prompt' and 'Visual Studio Marketplace'. There are no explicit Linux or cross-platform CLI examples, nor are alternative Linux development tools or workflows mentioned. The instructions for running and deploying the API assume a Windows-centric workflow, with no mention of Linux-specific steps or considerations.

Recommendations:

Include explicit instructions for Linux users, such as using the terminal and cross-platform CLI tools (e.g., Azure CLI, Bash).
Mention and provide examples for deploying Azure Functions using the Azure CLI or from a Linux environment.
Reference cross-platform editors (such as VS Code) in a way that highlights their availability on Linux, and avoid assuming Visual Studio Code is used in a Windows context.
Replace or supplement references to 'command prompt' with 'terminal' or 'shell', and clarify that all steps work on both Windows and Linux.
Add notes or sections for Linux/macOS users, especially for environment variable management and local development.
Ensure screenshots and terminology are not Windows-specific where possible, or provide Linux equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, the PowerShell examples are labeled as 'Formatted for PowerShell' and are given equal prominence to the Bash examples, despite Bash being the default shell on Linux and macOS. Additionally, variable assignment in PowerShell is shown even when the Bash example is already present, which may not be necessary. There is no explicit mention of Linux or macOS, and the documentation does not clarify that Bash examples are suitable for those platforms, potentially leading to a subtle Windows/PowerShell bias.

Recommendations:

Clearly indicate that Bash examples are intended for Linux/macOS and PowerShell examples are for Windows.
List Bash (Linux/macOS) examples first, as Azure CLI is cross-platform and Bash is the default on non-Windows systems.
Add a short note explaining which shell to use on each OS.
If both examples are provided, ensure parity in explanation and avoid implying PowerShell is the primary or default environment.
Consider adding a tabbed interface or clearer separation for Bash and PowerShell to avoid confusion.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively uses the Azure portal (web UI) for configuration steps, which is platform-agnostic but often associated with Windows-centric workflows. There are no command-line examples (such as Azure CLI or PowerShell), but the absence of Linux-specific or cross-platform CLI instructions (e.g., bash scripts, az CLI commands) means Linux users do not see parity or guidance for non-GUI environments.

Recommendations:

Add equivalent step-by-step instructions using the Azure CLI (az) for enabling managed identities and assigning roles, which work across Windows, Linux, and macOS.
Include bash shell examples for secret management and role assignment.
Explicitly mention that the portal steps are platform-independent, but provide links or sections for CLI-based workflows.
Ensure that any future examples or scripts are provided in both PowerShell and bash where applicable.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively references Visual Studio Code and its Azure API Center extension, both of which are cross-platform, but does not mention or provide examples for Linux-specific tools, editors, or workflows. There is no explicit mention of Linux or macOS environments, nor are alternative command-line or editor options discussed.

Recommendations:

Explicitly state that Visual Studio Code and the Azure API Center extension are available on Windows, Linux, and macOS.
Include examples or notes for installing and using the extension on Linux (e.g., using apt, snap, or rpm for VS Code installation).
Mention alternative editors or CLI tools, if available, for users who may not use Visual Studio Code.
Provide links or references to Linux/macOS-specific setup guides, if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is featured immediately after. There is no explicit mention of Linux or Bash shell usage, nor are there any Linux-specific considerations or examples. The documentation assumes parity between CLI and PowerShell, but the presence of PowerShell and lack of Linux/Bash examples may subtly bias toward Windows users.

Recommendations:

Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and can be run in Bash or other shells.
Add a Bash-specific example or note for Linux/macOS users, clarifying any differences in file paths or environment setup.
If referencing PowerShell, clarify that PowerShell Core is available cross-platform, or provide a link to installation instructions for non-Windows systems.
Consider listing Azure CLI (which is cross-platform) before PowerShell, or making it the default example, to reduce Windows-first perception.
Add a short section or callout for Linux/macOS users to ensure inclusivity.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation exclusively uses Azure Portal, Logic Apps, and Microsoft Teams for workflow automation, all of which are Microsoft-centric tools. There are no examples or mentions of Linux-native tools, CLI-based automation, or cross-platform notification systems (e.g., Slack, email, or open-source alternatives). The workflow assumes use of the Azure Portal GUI and Microsoft Teams, which are more common in Windows/Microsoft environments, and does not provide parity for Linux-first or open-source workflows.

Recommendations:

Provide alternative examples using Azure CLI or Azure PowerShell (which are cross-platform) for steps currently described only in the Azure Portal.
Include guidance for integrating with non-Microsoft notification systems, such as Slack, email (SMTP), or open-source chat tools, to broaden applicability beyond Microsoft Teams.
Offer sample workflows using open-source automation tools (e.g., GitHub Actions, Jenkins, or shell scripts) that can be run on Linux systems.
Explicitly mention that Logic Apps and Teams are not required, and provide links or examples for Linux-friendly or platform-agnostic alternatives.
Add a section on how to perform similar automation using REST APIs and scripting (e.g., Bash, Python) for users who prefer or require Linux-native solutions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with variable setup and multiple authentication scenarios. Azure CLI (Bash) examples are provided, but only after PowerShell, and the documentation's structure and depth favor Windows/PowerShell workflows. There are no Linux-specific tools or patterns, but parity is mostly maintained through Azure CLI and REST examples.

Recommendations:

Present CLI (Bash) examples before or alongside PowerShell examples to avoid the impression of Windows-first workflows.
Ensure that all authentication and configuration scenarios shown in PowerShell are equally covered in CLI/Bash examples.
Explicitly mention Linux/macOS compatibility for CLI/Bash examples to reassure non-Windows users.
Where possible, provide cross-platform scripting tips or highlight any differences in behavior between platforms.
Consider including a short section on using these tools from Linux/macOS environments, especially for variable setup and authentication.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates mild Windows bias, most notably in the DNS configuration section where the hosts file path for Windows is listed first and the reference to the hosts file uses a Windows-style environment variable (%SystemDrive%). Additionally, the only external link for creating a DNS record points to a legacy Windows Server documentation page, with no equivalent Linux guidance or links. However, Linux and macOS hosts file paths are mentioned, and no PowerShell-specific or Windows-only command-line examples are present.

Recommendations:

When referencing file paths (such as the hosts file), alternate the order or list Linux/macOS first in some instances to avoid always privileging Windows.
Provide external documentation links for both Windows and Linux (e.g., link to official Linux documentation for editing /etc/hosts, not just Windows Server).
Where environment variables are used (e.g., %SystemDrive%), also show the Linux equivalent or use neutral language.
If referencing tools or procedures that are OS-specific, ensure parity by including Linux/macOS equivalents or noting differences.
Consider adding CLI-based configuration examples (e.g., using Azure CLI or ARM templates) that are cross-platform, and avoid assuming the reader is using the Azure Portal on Windows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by referencing only ASP.NET Core and Visual Studio Code for creating and publishing example web APIs, both of which are traditionally associated with Windows development environments. There are no explicit Linux or cross-platform examples or mentions of Linux-specific tools or workflows. The documentation does not provide command-line or shell examples (e.g., Bash, CLI), nor does it mention Linux distributions or tools, focusing instead on GUI-based workflows that are more familiar to Windows users.

Recommendations:

Add explicit examples and links for creating and publishing web APIs using Linux-based tools and environments, such as using the Azure CLI or deploying from a Linux terminal.
Include references to cross-platform frameworks and editors (e.g., Node.js, Python Flask, Java Spring Boot) and show how to publish these to Azure App Service from Linux.
Provide step-by-step instructions or links for deploying APIs from Linux and macOS, not just Windows-centric tools like Visual Studio Code.
Mention that Visual Studio Code is cross-platform, and provide Linux/macOS installation instructions or alternatives.
Where possible, include screenshots or terminal commands from Linux environments to demonstrate parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a bias towards Windows by referencing only the Azure Portal (a web GUI) and providing a link to a PowerShell-based guide for enabling DDoS IP Protection. There are no CLI or Linux-native command examples (such as Azure CLI or Bash scripts), and the only automation example referenced is PowerShell, which is primarily associated with Windows environments.

Recommendations:

Provide equivalent Azure CLI (az) command examples for enabling DDoS Protection on both VNets and public IP addresses, as Azure CLI is cross-platform and widely used on Linux.
Include Bash script examples where automation is discussed, to ensure Linux users have parity.
When linking to automation guides, offer both PowerShell and Azure CLI documentation links.
Explicitly mention that the Azure Portal is accessible from any OS, but supplement with command-line instructions for users who prefer or require non-GUI workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes using the Azure Portal for deployment, but when mentioning command-line alternatives, it lists Azure PowerShell before Azure CLI and does not provide any explicit Linux or cross-platform command-line examples. There are no bash or Linux-specific instructions, and the only command-line tools mentioned are Azure PowerShell and Azure CLI, with PowerShell listed first. No Linux tools or screenshots are provided.

Recommendations:

When listing command-line deployment options, mention Azure CLI before or alongside Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
Provide explicit examples for deploying the ARM template using Azure CLI (bash) and, if possible, PowerShell, to ensure parity.
Include screenshots or terminal snippets that demonstrate Linux or cross-platform usage, not just Azure Portal UI.
Add a section or callout highlighting that Azure CLI works on Linux, macOS, and Windows, and provide installation links for each.
Ensure that any referenced documentation (such as 'Deploy templates') includes Linux/bash examples, or link directly to sections that do.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific tools (PowerShell) for backend management, without mentioning Linux or cross-platform alternatives. There are no Linux-specific examples or CLI instructions, and the only tool explicitly named is PowerShell.

Recommendations:

Include Azure CLI examples for managing backend entities, as Azure CLI is cross-platform and widely used on Linux.
Mention that backend management can also be performed using Azure CLI or REST API, not just PowerShell.
If scripting examples are provided, offer both PowerShell and Bash/Azure CLI equivalents.
Review all tool references to ensure Linux users are not excluded or made to feel like a secondary audience.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for programmatic management of access restrictions, but PowerShell is featured equally or more prominently in advanced scenarios and code samples. In multi-source rules and Azure Front Door restriction examples, only PowerShell is shown, with no equivalent Bash or Linux-native scripting. While Azure CLI (cross-platform) is present, PowerShell is often shown first or exclusively in some advanced sections, which may signal a Windows-centric approach. There are no explicit references to Windows-only tools, but the lack of Bash or Linux shell examples in advanced scenarios and the prominence of PowerShell may disadvantage Linux users.

Recommendations:

For every PowerShell example, provide an equivalent Azure CLI (bash/shell) example, especially in advanced scenarios such as multi-source rules and Azure Front Door restrictions.
In tabbed code sections, alternate the order of Azure CLI and PowerShell examples, or default to Azure CLI first, as it is cross-platform.
Add explicit Bash/shell script examples where scripting is shown, not just Azure CLI one-liners, to demonstrate Linux-native automation.
Review all advanced scenario sections to ensure Linux users are not required to translate PowerShell logic themselves.
Consider adding a short note at the start clarifying that all features are available equally on Linux and Windows, and that both Azure CLI and PowerShell are supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuration steps, but consistently lists PowerShell examples after CLI and does not provide any Linux shell-specific (e.g., Bash) examples or mention Linux-native tools. The use of PowerShell is prominent, and there is no explicit parity for Linux shell scripting or guidance for Linux users beyond the CLI. There is also a lack of explicit mention of Linux-specific considerations outside of a brief note regarding outbound networking for Linux apps.

Recommendations:

Provide explicit Bash shell examples alongside Azure CLI and PowerShell, especially for scripting scenarios.
Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
When presenting command-line examples, alternate the order (e.g., sometimes show Bash/CLI first, sometimes PowerShell) or group them together to avoid a perceived Windows-first bias.
Include notes or sections that address any Linux-specific behaviors or troubleshooting steps, especially for common scenarios like file system mounting or networking.
Where PowerShell is used for advanced scripting (e.g., using Invoke-AzRestMethod), provide equivalent Bash/cURL examples if possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows-first bias by referencing the Windows deployment path (C:\home\site\wwwroot) before mentioning the Linux equivalent, and by providing more detailed guidance for Windows paths. Linux-specific instructions are only briefly mentioned and lack example commands or context. No Linux shell or tooling examples are provided, and the Linux path format is only described in a note, not in the main instructional flow.

Recommendations:

Present Linux and Windows paths together in all relevant steps, not just in notes. For example, specify both 'C:\home\site\wwwroot\auth.json' (Windows) and '/home/site/wwwroot/auth.json' (Linux) when describing file locations.
Include explicit Linux examples and commands (e.g., using bash or Linux file paths) alongside Windows examples.
Avoid assuming the reader is on Windows by default; structure instructions to address both platforms equally.
Where platform differences exist (such as relative vs. absolute paths), provide clear, parallel examples for both Windows and Linux.
Consider adding a table or section summarizing platform-specific differences for quick reference.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a detailed C# example for decoding user claims, which is specific to .NET (commonly associated with Windows environments), and offers only brief mentions of PHP and Java without code samples. There are no Linux/Unix shell or cross-platform code examples (e.g., Python, Node.js), nor are there instructions for accessing headers in a Linux-native way. The focus on .NET and lack of parity in examples for other platforms indicates a Windows/.NET-first bias.

Recommendations:

Add code examples for popular Linux-friendly languages such as Python (Flask/Django), Node.js (Express), and Bash to demonstrate how to access and decode the X-MS-CLIENT-PRINCIPAL header.
Provide step-by-step instructions or code snippets for accessing request headers in Linux-native environments, such as Apache or Nginx configurations.
Ensure that framework-specific alternatives include equal detail and code samples for non-Windows platforms, not just .NET.
Reorder or balance the presentation so that Windows/.NET examples are not always first, or group examples by language without implied priority.
Explicitly mention that the process is cross-platform and provide links or references to Linux/Unix-specific documentation where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally provides parity between Linux and Windows examples, but there are subtle signs of Windows bias. In some sections, Windows-specific tools (like the Kudu console) are mentioned for Windows, while Linux uses SSH, and in the Application Insights section, the Windows example includes an extra setting (XDT_MicrosoftApplicationInsights_Java=1) not explained for Linux. Additionally, in the Azure CLI section for Application Insights, the instructions for setting app settings show the Linux tab before Windows, but the overall structure and some notes (like retrieving locations) do not clarify OS differences. The documentation does not provide PowerShell-specific examples or exclusively Windows tools, but the mention of Kudu (a Windows-centric tool) and the extra Windows-specific setting indicate a mild Windows bias.

Recommendations:

Provide equivalent explanations for OS-specific settings, such as clarifying the purpose of 'XDT_MicrosoftApplicationInsights_Java=1' for Windows and whether a Linux equivalent is needed.
Where a Windows-specific tool (like Kudu) is mentioned, suggest a Linux equivalent or clarify if SSH is the recommended approach.
Ensure that any extra steps or settings for one OS are clearly explained and, if not needed on the other OS, state so explicitly.
Continue to present Linux and Windows instructions side-by-side, and avoid assuming familiarity with Windows tools or patterns.
If possible, provide parity in tooling recommendations (e.g., mention cross-platform tools where available).

Create pull request

Bias Types:

⚠️ linux_first

⚠️ missing_windows_example

Summary:

The documentation page demonstrates a Linux-first bias in the section on Java key store usage, providing detailed instructions and examples specifically for Linux environments, while omitting equivalent instructions or examples for Windows-based App Service environments. There are no PowerShell or Windows tool references, but Linux paths, commands, and behaviors are described exclusively.

Recommendations:

Add a section describing how Java key stores and certificate management work on Windows-based App Service, including default locations, behaviors, and any differences from Linux.
Provide Windows-specific examples for initializing and loading the Java key store, including file paths and environment variables relevant to Windows.
Mention how to interact with the Java Key Tool on Windows App Service (e.g., via Kudu console or other supported methods), and reference the appropriate documentation.
Ensure parity in troubleshooting and manual certificate management instructions for both Linux and Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides command-line export instructions for Azure CLI and Azure PowerShell, with PowerShell given its own section and a dedicated FAQ entry. There are no explicit Linux-specific examples or mentions of Linux tools (such as OpenSSL), and the order of examples places Azure CLI before PowerShell, but both are included. The FAQ references PowerShell specifically, and there are no Linux troubleshooting notes or parity checks. The documentation assumes familiarity with Azure CLI and PowerShell, which are both cross-platform but often more familiar to Windows users, and does not mention Linux-native certificate management patterns.

Recommendations:

Add explicit Linux-native examples, such as using OpenSSL to handle .pfx files after export.
Include troubleshooting notes for Linux users (e.g., file permissions, installing Azure CLI on Linux).
In the FAQ, include references to both PowerShell and CLI, and add Linux-specific troubleshooting tips.
Clarify that Azure CLI and PowerShell are cross-platform, and provide links to installation instructions for Linux.
Consider providing a 'Linux' tab or section for certificate export and management, showing common Linux workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides command-line examples using Azure CLI and Azure PowerShell, but does not include any explicit Linux- or macOS-specific shell examples (e.g., Bash, zsh). While Azure CLI is cross-platform, there are no examples showing usage in a Linux shell environment, and PowerShell is mentioned as an alternative but is traditionally associated with Windows. Additionally, the documentation does not mention or demonstrate Linux-native tools (such as curl, scp, or sftp) for interacting with FTP/S or Git endpoints, nor does it provide Linux-specific guidance for credential usage. The only Linux-specific note is a brief mention of Bash variable interpolation, but no example is provided.

Recommendations:

Add explicit Bash or Linux shell examples for all command-line operations, especially for credential management and Git/FTP/S usage.
Include examples using Linux-native tools (e.g., curl, sftp, scp) for interacting with deployment endpoints.
When listing command-line options, present Azure CLI (cross-platform) and Bash/Linux shell examples before or alongside PowerShell.
Provide guidance or troubleshooting tips specific to Linux environments, such as file permission issues or credential storage.
Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample terminal outputs from a Linux shell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is present and detailed, which may indicate a slight Windows bias. However, the Azure CLI tab is listed first, and all Terraform commands are platform-agnostic. There are no Linux-specific examples or explicit mentions of Linux tools, but the CLI examples are compatible with Linux/macOS. There are no exclusive Windows tools or patterns, but the inclusion of PowerShell as a primary verification method can be seen as a Windows-centric approach.

Recommendations:

Add explicit mention that Azure CLI commands work on Linux, macOS, and Windows, to reassure non-Windows users.
Consider including a Bash shell example or tab, especially for common verification steps, to demonstrate parity with Linux environments.
Clarify that PowerShell is optional and that all steps can be completed using the cross-platform Azure CLI.
If possible, provide troubleshooting or environment setup notes for Linux/macOS users, especially for file creation and environment variable handling.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation provides deployment examples for multiple platforms, with most using Ubuntu runners and Linux-native tooling. However, the ASP.NET (not Core) example is Windows-specific, using 'windows-latest' runners and Windows-only tools such as NuGet and MSBuild. This is the only example that is Windows-specific, and it appears before the Java, Node.js, and Python examples, which use Linux runners. There is no Linux/Mono alternative provided for ASP.NET, and Windows tools are required for that workflow.

Recommendations:

Add a Linux/Mono-based example for ASP.NET if feasible, or clarify that classic ASP.NET requires Windows runners due to tooling constraints.
Explicitly state in the ASP.NET section why a Windows runner is required, to help users understand the platform limitation.
Consider reordering the sections so that Linux-first or cross-platform frameworks (e.g., .NET Core, Java, Node.js, Python) appear before Windows-only frameworks, to avoid the impression of Windows preference.
Where possible, mention Linux equivalents or alternatives for Windows tools, or provide guidance for users on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a graphical interface that is typical of Windows environments, without mentioning or providing alternatives for Linux users or command-line methods. There are no examples or guidance for restarting the web app via Linux tools or CLI.

Recommendations:

Include instructions for restarting the web app using the Azure CLI, which is cross-platform.
Provide examples for both GUI (portal) and command-line methods, clearly labeling each.
Explicitly mention that the instructions apply to the Azure Portal, which is platform-agnostic, or clarify if the steps are specific to Windows environments.
Add Linux-specific or general CLI instructions to ensure parity for users on all platforms.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Azure Tools for VS Code extension without clarifying platform compatibility or providing Linux-specific guidance. It implicitly assumes a Windows environment by referencing VS Code extensions commonly associated with Windows workflows, and does not mention Linux installation or usage.

Recommendations:

Explicitly state that the Azure Tools for VS Code extension is available on all platforms, including Linux.
Provide instructions or screenshots for installing and accessing the Azure Tools extension on Linux.
Mention any platform-specific considerations or differences in the user interface for Linux users.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation describes using a right-click context menu to delete a resource group, which is a pattern typical of Windows GUI tools. There is no mention of equivalent actions for Linux users, such as command-line instructions or alternative interfaces.

Recommendations:

Include instructions for deleting a resource group using cross-platform tools such as the Azure CLI.
Provide examples for both GUI (Windows) and command-line (Linux/macOS) workflows.
Clarify which tool or interface is being referenced (e.g., Azure Portal, Visual Studio, etc.), and mention alternatives accessible from Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references the Azure Tools for VS Code extension, which is commonly used in Windows environments, and does not provide alternative instructions or examples for Linux users or command-line approaches. There is no mention of Linux-specific tools or methods.

Recommendations:

Include instructions for enabling streaming logs using the Azure CLI, which is cross-platform.
Mention how to access streaming logs from the Azure Portal, which is OS-agnostic.
Clarify that the VS Code extension is available on Linux and macOS, or provide alternative tools if not.
Add explicit Linux/macOS command-line examples to ensure parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation references the VS Code Output window, which is a cross-platform tool, but does not mention or provide examples for accessing logs via terminal or command-line tools commonly used on Linux. There is no mention of Linux-specific workflows or alternatives, and the guidance assumes the use of a graphical interface, which may not be preferred or available on all Linux systems.

Recommendations:

Include instructions or examples for viewing logs using terminal-based tools (e.g., tail, less, cat) for Linux users.
Clarify that the VS Code Output window is available on all platforms, or provide alternative methods for users who may not use VS Code.
Add a section or note addressing how to access logs outside of VS Code, particularly for users working in headless or server environments common on Linux.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation assumes the presence of Windows-specific tools (such as 'ODBC Driver 18 for SQL Server') and does not mention Linux compatibility or alternatives. There are no explicit Linux-specific instructions or troubleshooting notes, and the documentation does not clarify cross-platform support for the drivers or environment variables.

Recommendations:

Explicitly state whether the required drivers (e.g., ODBC Driver 18 for SQL Server) are available on Linux and provide installation instructions for Linux distributions.
Include notes or troubleshooting tips for common Linux issues (such as driver installation, environment variable configuration, or authentication differences).
Where possible, provide both Windows and Linux installation commands for dependencies.
Clarify that the code samples are cross-platform (if they are), or specify any platform-specific requirements.
Mention any Linux-specific tools or patterns that may be relevant for connecting to Azure SQL Database.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation uses UI navigation instructions that are generic but implicitly assume a Windows-style interface (e.g., 'menu on the left', 'top menu bar'), and does not provide any Linux-specific guidance or terminal-based alternatives. There are no examples or instructions for performing these actions via CLI, which is more common in Linux environments.

Recommendations:

Add equivalent instructions for performing these actions using the Azure CLI or other cross-platform tools.
Explicitly mention that the UI steps apply to all platforms, or clarify any platform-specific differences.
Provide screenshots or examples from both Windows and Linux environments if the UI differs.
Include a note or section for Linux users, especially if there are known differences or preferred workflows.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides instructions that are tailored to the Azure App Service interface, which is primarily oriented around Windows-based workflows. There is no mention of Linux-specific options or considerations, nor are there any examples or notes for users deploying on Linux-based App Service environments.

Recommendations:

Add a section or note specifying whether the instructions apply to both Windows and Linux App Service plans.
If there are differences for Linux-based App Service (such as logging configuration or file system access), provide parallel instructions or links to Linux-specific documentation.
Include examples or screenshots for both Windows and Linux environments, if the UI or options differ.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation refers to setting up a Git remote but does not provide any platform-specific instructions or examples. There is an implicit bias as it omits Linux/macOS command-line examples or guidance, which are often necessary for cross-platform parity. The phrasing and lack of explicit Linux instructions may lead users to assume a Windows-centric workflow.

Recommendations:

Add explicit Linux/macOS command-line examples for setting up a Git remote (e.g., using 'git remote add origin <Git Clone Uri>').
Include both Windows (Command Prompt/PowerShell) and Linux/macOS (bash) command examples side by side where relevant.
Clarify that the instructions apply to all platforms, or specify any platform-specific steps if needed.
Ensure future documentation consistently provides parity between Windows and Linux/macOS workflows.

Create pull request

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.

Create pull request

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.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation generally uses cross-platform tools (Git, Node.js, Azure CLI) and generic shell commands, but in Step 6 it explicitly lists 'Windows Command Prompt, PowerShell, or other command shell' as options for running Azure CLI, mentioning Windows shells first and not providing Linux/macOS-specific terminal guidance or examples. No Linux- or macOS-specific instructions or screenshots are provided, and the phrase order subtly prioritizes Windows environments.

Recommendations:

When referencing command shells, list platforms in a neutral or rotating order, e.g., 'Open a terminal (such as Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)'.
Explicitly state that all commands work on Windows, Linux, and macOS, and provide platform-agnostic instructions.
Where relevant, add notes or examples for Linux/macOS users (e.g., how to open a terminal, or differences in environment variable syntax).
Consider including screenshots or terminal prompts from multiple platforms to reinforce cross-platform support.
Avoid phrases that implicitly prioritize Windows (such as always listing Windows shells first).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation lists Windows-centric tools (Azure CLI, Azure PowerShell, Azure portal) in the prerequisites, with PowerShell mentioned before the Azure portal and no explicit mention of Linux-native tools or workflows. However, the main deployment steps use kubectl commands, which are cross-platform and standard for Kubernetes. There are no PowerShell-specific scripts or Windows-only tools in the main instructions, but the ordering and lack of explicit Linux parity in the prerequisites suggest a mild 'windows_first' bias.

Recommendations:

When listing ways to create an Azure Kubernetes cluster, mention Linux-native tools (such as Azure CLI) first, or clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Include explicit notes or examples for Linux/macOS users, such as using bash/zsh terminals, where relevant.
If referencing Azure PowerShell, balance with a note about Bash/CLI usage on Linux.
Consider adding a section or callout confirming that all kubectl commands and YAML deployment steps are fully supported and tested on Linux and macOS, not just Windows.
Where possible, avoid implying that the Azure portal or PowerShell are the default or preferred options.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on managing App Service plans through the Azure Portal UI and does not provide any command-line examples. There is no mention or example of using Windows-specific tools (such as PowerShell), but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or Linux-specific instructions are given. The only references to operating systems are in dropdowns or as prerequisites, not in actionable steps. This results in a bias of omission, where Linux users (and command-line users in general) are not served.

Recommendations:

Add Azure CLI examples for all major operations (create, move, scale, delete App Service plans), as the Azure CLI is cross-platform and widely used on Linux.
Where relevant, include Bash script snippets for common tasks.
Explicitly mention both Windows and Linux environments when discussing OS selection or constraints.
If PowerShell or Windows tools are ever referenced, ensure equivalent Bash/Azure CLI examples are provided alongside.
Consider a table or section comparing portal, CLI, and ARM template approaches for each operation.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for entering a new setting using a generic 'dialog', but does not specify or provide examples for Linux environments, command-line interfaces, or cross-platform tools. There is no mention of how to accomplish the same task outside of a GUI, which may not be available or preferred on Linux systems.

Recommendations:

Add command-line examples for setting the environment variable using Bash (e.g., export SCM_DO_BUILD_DURING_DEPLOYMENT=true) for Linux users.
Clarify whether the 'dialog' refers to a Windows-specific tool or a cross-platform interface, and provide alternatives if it is not cross-platform.
Include instructions for setting the variable in configuration files or deployment scripts commonly used on Linux.
Ensure that both GUI and CLI methods are documented, with equal prominence for Windows and Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or commands, but it implicitly assumes a generic workflow without mentioning Linux or cross-platform considerations. There are no explicit Windows or PowerShell commands, but the lack of Linux-specific guidance or parity examples (such as Linux terminal commands or credential management tips) may leave Linux users without clear instructions.

Recommendations:

Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash) environments for cloning and pushing to the Git repository.
Mention any platform-specific differences in credential usage or storage, such as how to handle passwords securely on Linux.
Include screenshots or terminal snippets from both Windows and Linux to ensure parity.
Clarify that the instructions are cross-platform, or specify any steps that differ between operating systems.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions using a generic dialog interface without specifying any platform-specific tools or commands. However, it does not provide any examples or guidance for setting the variable via Linux command line or configuration files, which may be relevant for cross-platform users.

Recommendations:

Add examples for setting the SCM_DO_BUILD_DURING_DEPLOYMENT variable using Linux shell commands (e.g., export, or via configuration files).
Include parity examples for both Windows (e.g., PowerShell, CMD) and Linux (e.g., Bash) environments.
Clarify whether the dialog is available on all platforms or provide alternative instructions for Linux users.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of Linux or cross-platform command-line workflows. There are no explicit Windows tools or PowerShell commands, but the absence of Linux-specific guidance may disadvantage Linux users.

Recommendations:

Add explicit instructions or examples for both Windows and Linux users on how to use the credentials to push code (e.g., using Git from the command line on both platforms).
Mention common tools for both environments, such as Git Bash for Windows and standard terminal for Linux.
Clarify that the process is platform-agnostic if that is the case, or provide any platform-specific caveats if needed.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides navigation instructions that are platform-neutral, but it does not mention or provide any examples or guidance for Linux users, such as command-line alternatives or Linux-specific tools. This omission may leave Linux users without clear instructions if they are not using the portal UI.

Recommendations:

Add equivalent instructions for Linux users, such as using the Azure CLI or relevant Linux command-line tools to achieve the same configuration changes.
Explicitly mention if the instructions apply equally to both Windows and Linux App Service plans, or clarify any differences.
Provide links to Linux-specific documentation or examples where appropriate.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides instructions for opening an SSH session via the Azure portal's browser-based interface, but does not mention or provide examples for connecting via native SSH clients, which are commonly used on Linux and macOS. There is no reference to platform-specific tools, but the lack of CLI-based instructions may disadvantage Linux users who prefer or require terminal access.

Recommendations:

Add instructions for connecting to the App Service container using a native SSH client (e.g., via the terminal on Linux/macOS or PowerShell/CMD on Windows).
Include example SSH command lines, such as: `ssh <user>@<app-name>.scm.azurewebsites.net`.
Clarify any platform-specific prerequisites or differences, if applicable.
Ensure that both browser-based and CLI-based access methods are documented for parity.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any platform-specific instructions or examples, but it also does not mention or demonstrate Linux-specific steps, tools, or considerations. There is a lack of parity in that no Linux (or cross-platform) guidance is given.

Recommendations:

Explicitly state whether the instructions apply equally to both Windows and Linux environments.
If there are differences in setting environment variables or using the dialog on Linux-based App Service plans, provide Linux-specific guidance or screenshots.
Include a note or section clarifying any platform-specific behavior for SCM_DO_BUILD_DURING_DEPLOYMENT.

Create pull request

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