Scan Details - Linux-first Docs for Azure

380

Pages Scanned

35

Pages Flagged

380

Changed Pages

9.2%

% Pages Flagged

Live Progress

🔴 Connecting...

0%

Phase: discovery

Processing: Initializing...

Activity Feed

21:25:29 Scan started

Scan Information

Started At: 2025-07-13 21:25:29

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

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias, particularly in the certificate creation section, where only PowerShell is mentioned as a method for creating self-signed certificates. There are no Linux or cross-platform command-line examples (such as OpenSSL) provided for certificate generation. The rest of the documentation is largely platform-agnostic, focusing on Azure portal steps and XML configuration, but the omission of Linux tooling in certificate management is notable.

Recommendations:

Add Linux and cross-platform examples for creating self-signed certificates, such as using OpenSSL, alongside the existing PowerShell instructions.
Explicitly mention that certificate creation can be performed on any OS, and provide equivalent command-line instructions for macOS and Linux users.
Wherever PowerShell or Windows-specific tooling is referenced, ensure a Linux alternative is also provided or linked.
Consider including a table or section comparing certificate creation methods across Windows (PowerShell), Linux (OpenSSL), and macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by presenting PowerShell examples and instructions before CLI (Bash) or REST alternatives. The PowerShell section is more detailed, and the use of PowerShell-specific cmdlets and variable syntax is emphasized. There is no mention of Linux-specific shell environments or tools, and the CLI examples, while present, are secondary. The documentation assumes familiarity with PowerShell and Windows-centric tools, which may disadvantage Linux users.

Recommendations:

Present CLI (Bash) examples before or alongside PowerShell examples, or alternate their order to avoid always prioritizing Windows tools.
Expand CLI (Bash) sections to match the level of detail and explanation given in PowerShell sections.
Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide guidance for Linux users where appropriate.
Include notes or links for installing and using Azure CLI and PowerShell on Linux, highlighting cross-platform compatibility.
Where possible, provide examples using native Linux tools or scripting (e.g., Bash scripts) for automation scenarios.
Avoid assuming PowerShell as the default automation tool; clarify that both PowerShell and CLI are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell examples for logger creation, referencing Azure PowerShell cmdlets, and omitting equivalent CLI or scripting examples for Linux/macOS users. The PowerShell example is the only imperative command-line example given, with no Azure CLI, Bash, or cross-platform scripting alternatives. This may disadvantage users on non-Windows platforms or those who prefer cross-platform tools.

Recommendations:

Add Azure CLI examples for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash shell script examples where appropriate, especially for tasks like constructing REST API requests.
When referencing tools, mention Azure CLI and PowerShell together, or list Azure CLI first to avoid the impression of Windows-first bias.
Explicitly state that all configuration steps can be performed from any OS using REST API, Azure CLI, or ARM/Bicep templates, and provide links or examples.
Where PowerShell is used, provide a side-by-side Azure CLI or Bash equivalent to ensure parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides PowerShell-only examples for disabling certificate chain validation, with no equivalent CLI, Bash, or Linux-native instructions. It references PowerShell cmdlets (New-AzApiManagementBackend, Set-AzApiManagementBackend) as the primary automation method, which are Windows-centric tools. There is no mention of Azure CLI, Bash, or Linux scripting alternatives, and no explicit Linux or cross-platform guidance for these tasks.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for disabling certificate chain validation.
Include Bash or shell script snippets where appropriate, or clarify if tasks can be performed cross-platform.
Explicitly state that PowerShell Core is cross-platform if that is intended, or provide instructions for Linux users.
Mention and demonstrate how to perform certificate management tasks using REST API with curl or similar Linux tools.
Ensure that all automation and scripting guidance is presented in a platform-neutral way, or provide parallel examples for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The instructions for scripting and automation are tailored to Windows users, with no mention of Linux or macOS workflows. Windows tooling and terminology are prioritized, and Linux users are not given parity in guidance.

Recommendations:

Add Azure CLI examples alongside all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to both sets of documentation.
Where possible, provide Bash shell script snippets for automation tasks, or clarify that the steps are not OS-specific.
In sections that reference installing PowerShell, also reference installing Azure CLI and provide platform-agnostic instructions.
Review and update terminology to avoid implying that PowerShell is the default or only scripting environment.
Ensure screenshots and UI instructions are not specific to Windows unless unavoidable, and clarify when steps are identical across platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell cmdlet examples (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for managing API revisions, without mentioning or providing equivalent examples for Linux/macOS users (such as Azure CLI or REST API). The only automation tool referenced is PowerShell, which is traditionally associated with Windows environments, and there are no cross-platform command examples.

Recommendations:

Add 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 for revision management tasks, which are platform-agnostic.
When mentioning automation tools, list Azure CLI and REST API before or alongside PowerShell to avoid implying Windows-first workflows.
Explicitly state that all operations can be performed from any OS using Azure CLI or REST API, and provide links to relevant documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows and Azure-specific tools and workflows. It exclusively references Azure CLI, Azure Functions Core Tools, and Azure CDN, with no mention of Linux-specific workflows, alternative open-source tools, or cross-platform deployment patterns. All command-line examples assume a Windows/Azure-centric environment and do not address Linux-specific nuances or alternatives.

Recommendations:

Include explicit notes confirming that all CLI tools and commands work equally on Linux, macOS, and Windows, or provide platform-specific instructions where differences exist.
Mention and provide examples for deploying to non-Azure static hosts (e.g., AWS S3, Google Cloud Storage, or generic Nginx/Apache setups) to illustrate cross-platform parity.
List open-source or cross-platform alternatives to Azure CDN, such as Cloudflare or Fastly, and provide example configurations.
Clarify that Azure Functions Core Tools and Azure CLI are cross-platform, and provide installation instructions for Linux and macOS.
Where possible, use generic shell commands (e.g., bash) and avoid Windows-specific command syntax or tools.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias toward Windows by referencing the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only CLI-based method for adding users, without mentioning or providing examples for cross-platform tools such as Azure CLI. There are no Linux-specific or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.

Recommendations:

Include equivalent Azure CLI commands for adding users to Azure API Management, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell is available cross-platform, but also provide Bash or shell script examples where appropriate.
Add a section or note highlighting cross-platform tooling options for managing users, such as REST API calls or Azure CLI, to ensure parity for Linux and macOS users.
Where possible, avoid referencing only Windows-centric tools or provide them alongside Linux-friendly alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily through its references and examples. It mentions connecting virtual networks using PowerShell (a Windows-centric tool) in the 'Related content' section, and does not provide equivalent guidance or examples for Linux users (e.g., Azure CLI, Bash). There are no Linux or cross-platform command-line examples, and the only automation tool referenced is PowerShell. This may make the documentation less accessible or actionable for users on Linux or macOS platforms.

Recommendations:

Include Azure CLI (az) command examples alongside or instead of PowerShell for all relevant operations, especially in 'Related content' and any procedural sections.
When referencing automation or scripting, mention both PowerShell and Bash/CLI options, or provide links to both.
Avoid listing Windows/PowerShell tools first or exclusively; ensure parity by presenting cross-platform tools and workflows.
Add explicit notes or links for Linux/macOS users where procedures may differ, especially for network configuration and DNS setup.
Audit related documentation links to ensure they do not disproportionately point to Windows/Powershell-specific guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by presenting Windows SKU availability before Linux, providing Azure PowerShell automation examples (which are Windows-centric), and referencing Windows-specific behaviors and limitations. There are no Linux shell scripting examples (e.g., Bash), and PowerShell is highlighted as a primary automation tool, which may not be familiar or available on all Linux environments. The documentation also refers to the Azure portal UI without clarifying any platform differences, and does not provide parity in Linux-native automation or troubleshooting approaches.

Recommendations:

Present Linux and Windows options in parallel, or alternate which comes first to avoid implicit prioritization.
Add Bash shell scripting examples for automating tasks, alongside PowerShell, to support Linux users.
Clarify any platform-specific differences in the Azure portal UI, if applicable.
Explicitly mention cross-platform compatibility for CLI and scripting tools.
Where PowerShell is referenced, note that it is available cross-platform, but provide native Bash alternatives for Linux users.
Ensure troubleshooting and error-handling guidance is not Windows-specific and includes Linux scenarios.

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 detailed guidance and screenshots for Windows users. PowerShell commands are used for connectivity testing, and GUI-based workflows are only available on Windows. Linux support is present but less emphasized, with some features (like the GUI) unavailable and less detailed troubleshooting guidance for Linux environments.

Recommendations:

Present Windows and Linux instructions in parallel or in a more balanced way, rather than defaulting to Windows-first ordering.
Where PowerShell commands are given (e.g., Test-NetConnection), provide equivalent Linux commands (such as 'nc', 'telnet', or 'curl') for connectivity testing.
Expand Linux troubleshooting guidance, including common commands and diagnostic steps relevant to Linux environments.
Clarify feature parity and limitations up front, and provide alternative Linux workflows where GUI tools are not available.
Include more Linux-specific screenshots and examples, especially for CLI workflows.
Where GUI-only features exist on Windows, suggest or document equivalent CLI or script-based approaches for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias. It prioritizes ASP.NET and ASP.NET Web Forms (Windows-centric frameworks) in its code samples, providing detailed C# examples before other languages. The only explicit mention of platform-specific access to the client certificate is for ASP.NET, with no equivalent Linux/Unix-specific guidance. There are no examples or instructions for Linux command-line tools (such as Bash, OpenSSL, or curl), nor is there any mention of Linux-specific configuration or troubleshooting. The use of Azure CLI and Bicep is cross-platform, but the overall narrative and sample ordering favor Windows and Microsoft technologies.

Recommendations:

Add Linux/Unix-specific instructions and examples, such as how to use OpenSSL or curl to test mutual TLS authentication.
Include guidance for accessing and validating client certificates in popular Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
Provide Bash shell examples alongside Azure CLI and Bicep, demonstrating how to interact with the API or test mutual TLS.
Reorder language samples to alternate or balance Windows and Linux-first frameworks (e.g., show Node.js, Python, or Java before or alongside C#).
Explicitly mention that the provided code samples work on both Windows and Linux, or note any platform-specific considerations.
Add troubleshooting steps or notes for Linux environments, such as permissions, certificate store locations, or common errors.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page demonstrates a bias towards Windows environments by providing only a C# example using the Microsoft.IdentityModel.Tokens NuGet package (which is Windows/.NET-centric), and referencing CngKey and ECDsaCng, which are Windows-specific cryptography APIs. There are no examples or guidance for Linux users or for cross-platform tools/libraries (such as OpenSSL, Python, or Node.js). There is also no mention of how to generate the JWT client secret on Linux or macOS, nor are any cross-platform command-line examples 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 and provide code snippets for Linux and macOS users, including how to handle the .p8 key file and sign JWTs.
Avoid using Windows-specific APIs (like CngKey, ECDsaCng) in the only example, or at least provide alternatives for other platforms.
List cross-platform libraries and tools before or alongside Windows/.NET options.
Include a table or section comparing approaches for Windows, Linux, and macOS environments.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools and deployment patterns (such as Web Deploy/MSDeploy and Visual Studio) without providing Linux-specific equivalents or examples. The discussion of deployment agents and troubleshooting focuses on Windows agents, and there is no mention of Linux command-line tools (e.g., sftp, curl) or Linux-specific deployment workflows. Additionally, the documentation does not provide parity in examples or troubleshooting for Linux users.

Recommendations:

Include Linux-specific deployment examples, such as using sftp or Linux CLI tools for FTP/S deployments.
When referencing Visual Studio or Web Deploy, also mention cross-platform alternatives (e.g., VS Code, Azure CLI, Git) and clarify their support on Linux.
In troubleshooting and agent discussions, provide guidance for both Windows and Linux agents, including any differences in authentication or fallback behaviors.
Add explicit notes or sections for Linux users where workflows or commands differ, ensuring Linux parity in all deployment and configuration scenarios.
When listing deployment methods or tools, avoid always listing Windows tools first; alternate or group by platform where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily biased towards Windows. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps not supported. All troubleshooting and connectivity examples use Windows-specific tools and commands (e.g., PowerShell's Test-NetConnection, netstat -aon), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and the documentation does not acknowledge how Linux users might perform similar tasks.

Recommendations:

Clearly state at the beginning that gateway-required virtual network integration is not supported for Linux apps, and provide a prominent pointer to regional virtual network integration for Linux users.
Where Windows-only features or tools are discussed, provide equivalent Linux guidance or explicitly state that the feature is not available for Linux.
In troubleshooting sections, include Linux command equivalents for network testing (e.g., use 'nc', 'ss', or 'netcat' for TCP connectivity, 'lsof' or 'ss' for port listening, and 'dig' or 'host' for DNS resolution).
When referencing environment variables or the Kudu console, mention how Linux users can access similar information (e.g., via SSH or the Azure portal).
Add a summary table or section comparing feature support and troubleshooting steps for Windows vs. Linux, to help users quickly understand platform differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides command-line examples for exporting App Service certificates using Azure CLI and Azure PowerShell, but does not include any Linux- or Unix-specific examples or guidance beyond the Azure CLI. The PowerShell example is given equal prominence to the CLI, and the FAQ specifically references PowerShell for troubleshooting. There are no examples or notes about Linux certificate management tools or workflows, nor is there any mention of platform-specific considerations for Linux users.

Recommendations:

Add explicit Linux/Unix shell examples for certificate export and management, such as using OpenSSL to inspect or convert the downloaded .pfx file.
Clarify that Azure CLI commands are cross-platform and provide any necessary notes for Linux users (e.g., file permissions, dependencies).
Include troubleshooting steps or FAQs relevant to Linux environments, not just PowerShell.
Where PowerShell is referenced, consider also referencing Bash or other common Linux shells to ensure parity.
If any UI screenshots or instructions are OS-specific, clarify their applicability or provide Linux-relevant alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides both Azure CLI and Azure PowerShell instructions for configuring virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step parameter preparation and multiple command blocks. PowerShell is a Windows-centric tool, and its prominence, along with the lack of Bash or Linux shell examples, indicates a Windows-first and PowerShell-heavy bias. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with PowerShell patterns and tools.

Recommendations:

Provide equivalent Bash or shell script examples for Linux users, especially for multi-step operations currently only shown in PowerShell.
Ensure that CLI examples are as detailed as PowerShell ones, including parameter preparation, validation, and advanced scenarios (such as cross-subscription integration).
Explicitly mention that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, and avoid assuming PowerShell as the default scripting environment.
Where possible, structure the documentation so that cross-platform (CLI/Bash) instructions appear before or alongside PowerShell instructions, not after.
Add notes or links to Linux-specific guidance or troubleshooting for common issues encountered on non-Windows platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias, particularly in the deployment mechanisms section. Kudu is described as running as a separate process in Windows App Service and only as a 'second container' in Linux, with more detail and emphasis on the Windows implementation. FTP and WebDeploy are mentioned as deployment mechanisms, but WebDeploy is a Windows-specific tool, and no Linux equivalents (such as rsync or SCP) are discussed. There are no explicit Linux command-line examples or references to Linux-native deployment tools. While the GitHub Actions example uses Ubuntu runners and Docker (which are cross-platform), the overall framing and tool mentions prioritize Windows or Windows-centric tools and patterns.

Recommendations:

Provide explicit Linux-native deployment examples, such as using SCP, rsync, or SFTP for file transfers.
When mentioning deployment mechanisms, clarify which are cross-platform and which are Windows-only, and suggest Linux alternatives where appropriate.
Balance the discussion of Kudu by giving equal detail to its operation on Linux (as a container) and Windows (as a process), and clarify any differences in usage or troubleshooting.
Include references to Linux command-line tools and workflows (e.g., using Azure CLI on Linux, or integrating with Linux-based CI/CD tools).
If mentioning WebDeploy, also mention that it is Windows-specific and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally provides both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently presented immediately after Bash, and sometimes with explicit 'PowerShell syntax' labels. There are no Linux-specific tools or workflows mentioned, but the documentation does state that Azure CLI commands can be run in either PowerShell or Bash. No examples are exclusive to Windows or PowerShell, but the repeated explicit inclusion of PowerShell syntax and the order of presentation (Bash first, then PowerShell) may suggest a slight Windows-first or PowerShell-heavy bias.

Recommendations:

Ensure that all command examples are provided for both Bash and PowerShell, as currently done.
Consider alternating the order of Bash and PowerShell examples, or presenting them in parallel tabs, to avoid implying a default preference.
Explicitly mention Linux and macOS compatibility in the prerequisites and command sections, not just Bash.
Include screenshots or references to Linux/macOS environments where appropriate, not only Azure Portal (which is OS-agnostic but often associated with Windows workflows).
If any troubleshooting or environment setup steps differ for Linux/macOS, provide those details alongside Windows instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented after the Bash examples. There are no exclusive Windows tools or patterns, but the presence of PowerShell examples and their explicit labeling indicates a slight Windows bias. Linux (Bash) examples are present and shown first, but there is no explicit mention of Linux or macOS environments, nor troubleshooting or environment-specific notes for non-Windows users.

Recommendations:

Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows.
Add a short note at the start of the CLI section explaining which shell to use on which platform.
Ensure parity in troubleshooting or environment-specific notes for both Linux and Windows users.
Consider including zsh or other popular Linux shell variants if relevant.
Where possible, avoid implying PowerShell is the default or preferred shell for CLI usage.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation mentions Azure PowerShell alongside Azure CLI as tools to list deployed resources, but lists Azure PowerShell after Azure CLI. However, there are no explicit command examples for either tool, and no Linux-specific tools or patterns are mentioned. The mention of Azure PowerShell may imply a Windows-centric approach, but the Azure CLI is cross-platform.

Recommendations:

Provide explicit command examples for both Azure CLI and Azure PowerShell, clarifying that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
Mention that Azure PowerShell is available on all platforms, not just Windows, to avoid the implication that it is Windows-only.
Consider including Linux-native tools or shell examples (such as Bash) where appropriate.
Ensure that any future examples or screenshots include both Windows and Linux environments to reinforce cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively provides instructions using the Azure portal GUI, which is most commonly accessed and documented from a Windows environment. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux or cross-platform workflows. This can disadvantage users who prefer or require automation, scripting, or non-Windows environments.

Recommendations:

Add equivalent instructions using the Azure CLI, which is cross-platform and widely used on Linux and macOS.
If relevant, provide PowerShell examples alongside CLI examples, but do not make them the only option.
Explicitly mention that the Azure portal can be accessed from any OS with a web browser, to clarify platform neutrality.
Include notes or links to documentation for automating these tasks in CI/CD pipelines, which often run on Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence to Azure CLI, and there is no mention of Linux-specific considerations or examples. The PowerShell example is presented alongside the CLI example, but there are no explicit Linux shell (bash) examples or notes about cross-platform usage, which may implicitly favor Windows users.

Recommendations:

Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider providing bash-specific examples or notes where appropriate.
Clarify that PowerShell Core is cross-platform, but traditional Azure PowerShell is most commonly used on Windows.
Add a section or note for Linux/macOS users, highlighting any differences or confirming parity.
Ensure that CLI examples are presented first, as they are more universally applicable across platforms.
Avoid implying that PowerShell is the default or primary method unless it is truly cross-platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page primarily describes procedures using the Azure Portal UI and Azure CLI, with a single mention of Azure PowerShell. While the CLI examples are cross-platform, there is a subtle Windows bias in the order of tool presentation: Azure PowerShell is mentioned alongside the CLI and REST API, but no explicit Linux shell or scripting examples (e.g., Bash) are provided. There are no references to Windows-specific tools or commands, but the lack of Linux/Bash-specific guidance or parity in scripting examples may disadvantage Linux users.

Recommendations:

Provide explicit Bash shell examples for common operations, especially where Azure CLI is used, to demonstrate parity and clarify cross-platform usage.
When listing tools for performing tasks (e.g., disabling a regional gateway), alternate the order or explicitly state that both Azure CLI and PowerShell are supported on all platforms.
Include notes or links to documentation for running Azure CLI and PowerShell on Linux, to reinforce cross-platform support.
If referencing PowerShell, consider also referencing Bash or other popular Linux shells to avoid the perception of Windows-first bias.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses on using the Azure portal and .NET for gRPC API import and consumption, with no mention of Linux-specific tools, CLI commands, or cross-platform examples. The only client example references .NET, which is more commonly associated with Windows environments, and there are no Linux or open-source alternatives provided.

Recommendations:

Include examples using Azure CLI or Azure PowerShell for importing gRPC APIs, with explicit instructions for both Windows and Linux shells.
Provide gRPC client usage examples in other languages commonly used on Linux, such as Python, Go, or Node.js.
Mention and demonstrate the use of cross-platform tools (e.g., curl, grpcurl) for testing gRPC endpoints.
Clarify that the steps are platform-agnostic where possible, or provide platform-specific notes if there are differences.
Add a section or links for Linux users on how to prepare and upload .proto files, and how to interact with Azure API Management from Linux environments.

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 linking to a PowerShell-based guide for enabling DDoS IP Protection, without providing equivalent CLI or Linux-native instructions. There are no examples or instructions using cross-platform tools such as Azure CLI or Bash scripts, and no mention of Linux-specific workflows.

Recommendations:

Add step-by-step instructions for enabling DDoS Protection using Azure CLI, which is cross-platform and widely used on Linux.
Where PowerShell-based guides are referenced, also provide links to equivalent Azure CLI documentation.
Include Bash script examples for automation scenarios, ensuring Linux users have parity.
Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide relevant command examples.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily demonstrates deploying an Azure API Management instance using the Azure portal, with only passing mentions of Azure PowerShell and Azure CLI as alternative methods. There are no concrete examples or instructions for using the CLI or PowerShell, and no Linux-specific guidance or screenshots. The documentation implicitly assumes use of the Azure portal (which is platform-agnostic but often associated with Windows environments) and does not provide parity for Linux users who may prefer command-line deployment.

Recommendations:

Add explicit step-by-step examples for deploying the ARM template using Azure CLI, including the exact command(s) to run. Ensure these examples are platform-neutral or specify Linux/macOS compatibility.
Provide PowerShell deployment instructions as a separate section, clearly indicating that PowerShell is available on multiple platforms but is often used in Windows environments.
Include sample commands for verifying and cleaning up resources using the Azure CLI, not just the portal.
Add screenshots or terminal output examples for both CLI and PowerShell where appropriate.
Clearly state that all deployment methods (portal, CLI, PowerShell, REST API) are supported and provide equal detail for each, or link directly to detailed guides for each method.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation references Windows-specific tools (PowerShell) for backend management and omits mention of Linux-native or cross-platform alternatives. No Linux or cross-platform CLI examples or tooling are provided, and the only explicit tooling example is PowerShell.

Recommendations:

Include Azure CLI examples for backend entity management, as Azure CLI is cross-platform and widely used on Linux.
Mention and link to Azure CLI documentation alongside PowerShell and REST API references.
If scripts or automation are discussed, provide both PowerShell and Bash (or generic shell) script examples.
Review all tooling mentions to ensure Linux users are not excluded or required to use Windows-specific tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for configuration tasks, but consistently lists the Azure PowerShell examples after the Azure CLI examples. While Azure CLI is cross-platform, the inclusion and prominence of PowerShell (which is historically associated with Windows, though now cross-platform) may still signal a Windows-centric approach. There are no examples or explicit mentions of Linux shell scripting or Linux-specific tools, and troubleshooting guidance is oriented around the Azure portal UI, which is platform-agnostic but may be more familiar to Windows users.

Recommendations:

Explicitly mention that Azure CLI commands are cross-platform and suitable for both Windows and Linux users.
Where PowerShell examples are provided, consider also providing equivalent Bash shell script examples for Linux users, especially for scripting scenarios.
Add a note clarifying that all configuration steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific caveats if they exist.
Include troubleshooting steps that reference command-line tools available on Linux (e.g., using curl or jq for API calls) in addition to Azure portal instructions.
If referencing PowerShell, clarify that PowerShell Core is available on Linux and macOS, or provide Bash alternatives where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation contains a minor Windows bias in the troubleshooting section, where only the Windows-specific command ('ipconfig /flushdns') is provided for clearing the DNS cache. There are no equivalent Linux or macOS commands mentioned. No other Windows-specific tools, PowerShell scripts, or patterns are present, and the rest of the documentation is platform-neutral.

Recommendations:

Add equivalent Linux and macOS commands for clearing DNS cache in the troubleshooting section (e.g., 'sudo systemd-resolve --flush-caches' for Linux, 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder' for macOS).
When providing OS-specific troubleshooting steps, list all major platforms (Windows, Linux, macOS) or link to a cross-platform guide.
Review any included automation/script sections to ensure parity or note if scripts are cross-platform.
Continue to avoid Windows-centric terminology or tools unless alternatives are also provided.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides a detailed C#/.NET example for decoding claims, with no equivalent code samples for Linux-oriented languages or scripting environments (e.g., Python, Node.js, Bash). Framework-specific alternatives are listed, but the most detailed guidance and code are for .NET, which is most commonly associated with Windows. There are no Linux/Unix shell or tool examples, and the order of presentation favors Windows-centric technologies.

Recommendations:

Add example code for decoding the X-MS-CLIENT-PRINCIPAL header in popular Linux-first languages such as Python and Node.js.
Include a Bash or curl command-line example for decoding the header, demonstrating how Linux users can inspect claims.
Balance the framework-specific alternatives section by providing more detail and code samples for non-Windows stacks (e.g., Java, PHP, Python, Node.js).
Explicitly mention that all examples are cross-platform unless otherwise stated, and clarify any OS-specific behaviors.
Consider reordering the framework-specific alternatives to avoid always listing Windows/.NET first.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents Windows-specific tooling (Azure PowerShell) before Linux/CLI alternatives when describing how to create an Azure Kubernetes cluster. However, the main deployment instructions use cross-platform tools (kubectl) and do not show a strong bias in the core workflow. No explicit Linux examples are missing, but the ordering in prerequisites subtly prioritizes Windows tools.

Recommendations:

List cross-platform tools (such as Azure CLI) before Windows-specific tools (such as Azure PowerShell) in prerequisites and instructions.
Explicitly mention that all kubectl commands work on Windows, Linux, and macOS to reinforce cross-platform compatibility.
If possible, provide links to Linux/macOS-specific getting started guides alongside Windows/PowerShell links.
Review related content and ensure parity in references to platform-specific tooling or portals.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page exclusively describes how to upgrade and scale an Azure API Management instance using the Azure Portal UI, with no command-line examples or automation instructions. There are no references to Windows-specific tools, but there is also a complete absence of CLI-based instructions (such as Azure CLI, PowerShell, or Bash), which are important for Linux users and automation scenarios. This omission results in an implicit bias toward portal-based workflows, which are often associated with Windows-centric documentation, and does not provide parity for Linux users who may prefer or require CLI-based management.

Recommendations:

Add step-by-step examples for scaling and upgrading using the Azure CLI (az apim commands), which work cross-platform on Linux, macOS, and Windows.
If PowerShell examples are provided in the future, ensure equivalent Azure CLI or Bash examples are included and presented with equal prominence.
Explicitly mention that all CLI instructions are cross-platform and do not require Windows.
Include links to relevant Azure CLI documentation for API Management operations.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on managing App Service plans via the Azure portal UI, without providing any command-line examples. There is no evidence of Windows-specific tools or PowerShell commands, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) or Linux-oriented instructions are provided. The only mention of OS is in the context of selecting the operating system for the App Service plan, with no further guidance for Linux users.

Recommendations:

Add Azure CLI examples for all major tasks (create, move, scale, delete App Service plans), with commands that can be run on Linux, macOS, and Windows.
Where relevant, provide Bash script snippets alongside any PowerShell or Windows command-line examples.
Explicitly mention that all CLI examples are cross-platform, and clarify any OS-specific differences in behavior or prerequisites.
Include links to documentation on using Azure CLI on Linux and macOS.
If PowerShell or Windows tools are ever referenced, ensure Linux equivalents are presented with equal prominence and detail.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific examples, commands, or tools, but it also does not mention Linux or provide Linux-specific guidance, despite being tagged as 'linux-related-content'. The instructions and UI references are generic to Azure App Service and do not demonstrate explicit Windows bias, but the lack of Linux-specific context or parity checks is a subtle bias, especially for users seeking Linux-relevant information.

Recommendations:

Explicitly state whether the error page configuration process is identical for both Windows and Linux App Service plans, or highlight any differences.
Add a section or note clarifying Linux support, such as any known limitations or behavioral differences for custom error pages on Linux-based App Service.
Provide Linux-specific troubleshooting tips or examples if applicable (e.g., how error handling may differ on Linux containers).
Ensure that future updates include parity checks for both Windows and Linux App Service environments.

Create pull request

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