Scan Details - Linux-first Docs for Azure

1635

Pages Scanned

42

Pages Flagged

1635

Changed Pages

2.6%

% Pages Flagged

Scan Information

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

Finished At: 2025-09-14 00:34:37

Status: completed

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation is heavily focused on Windows, specifically WPF desktop applications, and provides only C#/.NET code samples that are relevant to Windows environments. There are no Linux or cross-platform desktop application examples, nor any mention of Linux tools, patterns, or alternative frameworks. The guidance assumes the developer is working on Windows with WPF, omitting parity for Linux or macOS desktop application development.

Recommendations:

Add equivalent examples for cross-platform desktop frameworks such as .NET MAUI, Avalonia, or Electron, which can run on Linux.
Include code samples and configuration steps for Linux and macOS environments, or explicitly state the Windows-only scope if applicable.
Mention and link to MSAL libraries and authentication patterns for Linux-compatible desktop applications.
If WPF is the only supported scenario, clarify this limitation early in the documentation and provide links to cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools and documentation (such as Schannel SSP and Windows-focused TLS configuration guides) in the 'Next steps' section, without providing equivalent Linux guidance or examples. There are no Linux or cross-platform configuration instructions or references, and the troubleshooting and enabling guides are Windows-centric.

Recommendations:

Include links to Linux-focused resources for configuring TLS 1.2 and cipher suites (e.g., OpenSSL, Apache, Nginx documentation).
Provide examples or references for checking and enabling TLS 1.2 and required cipher suites on common Linux distributions.
Balance the 'Next steps' section by adding Linux and cross-platform articles alongside Windows resources.
Mention cross-platform tools (such as OpenSSL command-line utilities) for testing endpoint compatibility, in addition to SSL Labs.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong Windows bias. All AD FS configuration steps are described exclusively using Windows GUI tools (Server Manager, AD FS Management snap-in) and PowerShell cmdlets, with no mention of Linux equivalents or cross-platform alternatives. Troubleshooting guidance is focused on Windows Event Viewer. There are no examples or instructions for performing any step on Linux or macOS, nor is it acknowledged that AD FS is a Windows-only technology, which could help set expectations for non-Windows users.

Recommendations:

Clearly state early in the documentation that AD FS is a Windows Server technology and requires Windows for configuration and management.
Where possible, provide PowerShell command-line alternatives for all GUI steps, and ensure these are presented alongside or before GUI instructions.
If any steps (such as certificate generation or SAML metadata inspection) can be performed on Linux/macOS, provide equivalent OpenSSL or command-line examples.
For troubleshooting, mention cross-platform tools (such as reading logs remotely, or using SAML-tracer browser extensions) where appropriate.
If Linux-based SAML identity providers are supported, link to or reference documentation for configuring those as alternatives.
Explicitly acknowledge the Windows dependency for AD FS and suggest alternatives for Linux environments, such as Shibboleth or SimpleSAMLphp, where relevant.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation provides only a PowerShell script example for programmatically accessing audit logs, with no equivalent example for Linux or cross-platform tools such as Bash, curl, or Python. The script assumes use of PowerShell (which is native to Windows), and there is no mention of Linux command-line tools or how to perform the same task on non-Windows platforms. This creates a bias towards Windows users and may hinder Linux administrators from following the instructions easily.

Recommendations:

Provide equivalent Bash/curl and/or Python script examples for accessing the Microsoft Graph API and downloading audit logs, demonstrating how to authenticate and paginate results.
Explicitly mention that the API can be accessed from any platform, and link to cross-platform SDKs or CLI tools (such as Microsoft Graph CLI, Azure CLI, or REST API usage with curl).
Add a section or note clarifying that PowerShell Core is available on Linux and macOS, and provide installation instructions or alternatives.
Ensure that all automation and scripting examples have Linux-friendly equivalents, and present them either alongside or before Windows/PowerShell examples to promote parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation demonstrates a Windows bias by referencing Windows tools (Git Bash from Git for Windows, Visual Studio Immediate Window) as the primary or only examples for command-line and password encoding tasks. It also mentions Azure PowerShell before Azure CLI in several places, and provides detailed instructions for Visual Studio (a Windows-centric IDE) for URL encoding passwords, without offering equivalent Linux/macOS alternatives. There are no explicit Linux/macOS command-line examples or tool recommendations.

Recommendations:

Provide parallel Linux/macOS instructions and examples wherever Windows-specific tools or workflows are mentioned (e.g., suggest using the native terminal or Terminal.app, and provide equivalent shell commands).
When referencing tools like Visual Studio for password encoding, include cross-platform alternatives (e.g., Python, Node.js, or command-line utilities for URL encoding).
Avoid defaulting to Windows tools in examples; instead, use platform-agnostic tools or present both Windows and Linux/macOS options side by side.
List Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first approach.
Explicitly state that the instructions apply to all platforms and provide links to Git installation instructions for Linux/macOS as well as Windows.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page exclusively uses Azure PowerShell for all code examples and automation steps, with no mention or examples of equivalent Azure CLI, Bash, or cross-platform scripting. File paths and certificate handling assume Windows conventions (e.g., C:\ paths, .pfx files), and there is no guidance for Linux or macOS users. The prerequisites and instructions focus on Windows tooling and patterns, potentially excluding or confusing users on Linux or macOS.

Recommendations:

Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps, alongside or instead of PowerShell.
Use cross-platform file path examples (e.g., $HOME/certs/ or ~/certs/) or note the differences for Linux/macOS users.
Include notes or sections on how to generate and use certificates on Linux/macOS, including OpenSSL commands for .pfx and .cer files.
Mention that Azure PowerShell is available on Linux/macOS via PowerShell Core, but also recommend Azure CLI as a fully supported, cross-platform alternative.
Where referencing tools or commands, avoid assuming a Windows environment; provide parity in instructions for Linux/macOS.
Add troubleshooting and verification steps using Bash/curl that are platform-agnostic.
Explicitly state in the prerequisites that all steps can be performed on Linux/macOS, and provide links to relevant setup guides.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing PowerShell examples for logger creation, referencing the Azure PowerShell module, and omitting equivalent CLI (az), Bash, or cross-platform scripting examples. The PowerShell example is the only imperative command-line example, and it appears before declarative options (Bicep, ARM). There are no Linux-native or cross-platform command-line instructions for users who do not use PowerShell.

Recommendations:

Add Azure CLI (az) command examples for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script examples or generic REST API curl examples to demonstrate how to perform tasks without relying on PowerShell.
When listing tools or examples, present cross-platform options (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell), or clearly indicate that PowerShell is just one of several options.
Explicitly mention that all steps can be performed from any OS using the Azure portal, REST API, or Azure CLI, not just PowerShell.
Review and update the documentation to ensure Linux and macOS users are equally supported and not required to adapt Windows-centric instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates bias towards Windows 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-native tools or cross-platform command-line instructions are mentioned, and the only automation examples are Windows-centric.

Recommendations:

Provide Azure CLI examples alongside PowerShell cmdlets for all command-line operations, as Azure CLI is cross-platform and widely used on Linux.
Include REST API examples for users who prefer direct HTTP requests, which are platform-agnostic.
Clearly indicate when a feature is only available via the Azure portal, and if so, ensure screenshots or instructions are not Windows-specific.
Review all automation instructions to ensure Linux and macOS users are equally supported, not just Windows/PowerShell users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, and by referencing PowerShell before cross-platform or Linux-native options. There are no explicit Linux or bash examples, and the documentation does not mention Linux-specific tools or workflows. The order and emphasis favor Windows-centric tools and patterns.

Recommendations:

Provide explicit bash or shell command examples alongside PowerShell commands when referencing management tasks.
List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
Mention that Azure CLI and Resource Manager templates are fully supported on Linux and macOS.
Include links or references to Linux/macOS setup guides for Azure CLI and other tools.
Avoid implying PowerShell is the default or preferred tool; clarify tool parity across platforms.

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 Azure PowerShell scripts for generating OAuth tokens and calling APIs, with no equivalent Linux/bash/cURL examples. The only command-line tooling referenced is PowerShell/Invoke-RestMethod, which is Windows-centric (though available cross-platform, it is not the default shell on Linux). The documentation also references the Azure Portal UI exclusively, which is more familiar to Windows users, and does not mention or prioritize Linux-native tools or workflows.

Recommendations:

Provide equivalent Linux/bash/cURL examples for generating tokens and calling APIs, alongside the PowerShell scripts.
Explicitly mention that PowerShell Core is cross-platform, but also offer native bash/cURL commands for Linux/macOS users.
Include CLI-based alternatives (e.g., Azure CLI commands) where possible, not just portal steps.
Add a note or section on how to perform the same tasks on Linux/macOS, including any prerequisites or differences.
Ensure that examples and instructions are presented in a platform-neutral order, or alternate which platform is shown first.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation exclusively references Windows PowerShell cmdlets and scripts for managing Azure API Management via Azure Automation. There are no examples or mentions of Linux-compatible tools (such as Azure CLI, Bash, or Python), nor is there guidance for non-Windows environments. The focus on PowerShell and Windows tooling creates a bias towards Windows users and may exclude or hinder Linux users.

Recommendations:

Provide equivalent examples using Azure CLI, which is cross-platform and works natively on Linux.
Include Bash or Python script samples for managing Azure API Management via Azure Automation.
Mention and link to documentation for Linux/macOS users where appropriate.
Structure sections to present cross-platform solutions first or in parallel with Windows/PowerShell examples.
Clarify which tools and scripts are platform-agnostic and which are Windows-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. Azure PowerShell is given equal prominence to Azure CLI, with explicit PowerShell commands and update instructions, while Linux-native tools or shell examples are not provided. The Azure CLI is mentioned, but no bash or Linux-specific guidance is included. The order of presentation often puts PowerShell before or alongside CLI, and Windows-centric tools (PowerShell, Azure portal) are emphasized. There are no explicit Linux shell or scripting examples, and the documentation assumes familiarity with Windows tools.

Recommendations:

Provide Linux shell (bash) equivalents for all PowerShell commands, especially for checking and updating Azure CLI.
Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS installation and update instructions.
When listing tools, consider mentioning cross-platform tools (CLI, Terraform, Bicep) before Windows-centric ones (PowerShell).
Add examples or links for managing API Management via bash scripts or Linux automation tools.
Clarify that the Azure portal and REST API are platform-agnostic, and highlight this in relevant sections.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) instructions for provisioning the service principal, referencing the AzureAD PowerShell module (which is primarily used on Windows), and omitting equivalent CLI or Bash examples. No Linux/macOS-specific instructions or cross-platform alternatives (such as Azure CLI or REST API) are provided for key setup steps. The documentation assumes the use of the Azure Portal and PowerShell, both of which are more familiar to Windows users.

Recommendations:

Add equivalent Azure CLI (az) commands for provisioning the service principal and other setup steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
Explicitly mention that all PowerShell steps can be performed on Linux/macOS using Azure CLI or Bash, and provide those examples side-by-side.
Where possible, provide REST API alternatives for automation scenarios.
Clarify in prerequisites that PowerShell is not required and that users on Linux/macOS can follow along using CLI or portal.
Review all code snippets and ensure parity between Windows (PowerShell) and Linux/macOS (CLI/Bash) instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure tools and services, such as Azure CLI, Azure Function App, and Azure CDN, without mentioning or providing examples for Linux or cross-platform alternatives. There are no explicit Linux-specific instructions or examples, and the guidance assumes the use of Azure's ecosystem, which is more commonly associated with Windows environments.

Recommendations:

Include equivalent instructions and examples for Linux environments, such as using Bash scripts or Linux-native tools where applicable.
Mention and provide examples for deploying to non-Azure hosting solutions (e.g., AWS S3, Google Cloud Storage, or generic Nginx/Apache static hosting) to ensure cross-platform applicability.
Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux and macOS, not just Windows.
Offer alternative CDN recommendations beyond Azure CDN, such as Cloudflare or AWS CloudFront, to avoid exclusive Azure bias.
Explicitly state that all npm and CLI commands are platform-agnostic, and note any platform-specific caveats if they exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a mild Windows bias, most notably in Step 6 ('Upload static files to a blob'), where it explicitly instructs users to 'Open Windows Command Prompt, PowerShell, or other command shell' before running Azure CLI commands. No mention is made of Linux or macOS terminals, and no Linux-specific instructions or examples are provided. The general pattern is to assume a Windows environment, even though the rest of the steps are cross-platform and use generic shell commands.

Recommendations:

Update language in Step 6 to reference all major platforms, e.g., 'Open your terminal (Command Prompt, PowerShell, or terminal on Linux/macOS)'.
Explicitly state that all commands are cross-platform unless otherwise noted.
Wherever a shell or terminal is referenced, provide parity by mentioning Linux/macOS equivalents alongside Windows tools.
If there are any platform-specific considerations (such as path separators or environment variable syntax), call them out with examples for both Windows and Linux/macOS.
Consider adding a short section or note at the start of the document clarifying that the instructions are intended to be cross-platform, and that the Azure CLI and other tools work on Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation assumes usage of the Azure Portal and Power Platform GUIs, which are most accessible and fully featured on Windows environments. There are no CLI, Bash, or cross-platform automation examples, nor is there mention of Linux-compatible tools or workflows. Troubleshooting guidance references Application Insights and browser developer tools, but does not mention cross-platform command-line tools or Linux-specific approaches. The documentation implicitly prioritizes Windows/GUI workflows and omits Linux or cross-platform alternatives.

Recommendations:

Include Azure CLI and/or Azure PowerShell command examples for configuring CORS policies, making sure to show both Windows (PowerShell) and Linux (Bash) syntax.
Mention and provide examples for using cross-platform tools (e.g., az CLI, curl, jq) to automate or verify CORS policy configuration.
Add troubleshooting steps that leverage cross-platform tools, such as curl for testing CORS headers from Linux/macOS terminals.
Explicitly state that the Azure Portal and Power Platform GUIs are web-based and accessible from any OS, but provide parity for users who prefer or require command-line or scriptable solutions.
Where screenshots or UI steps are provided, consider linking to equivalent documentation for CLI-based workflows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the explicit inclusion of Azure PowerShell (which is most commonly used on Windows and follows Windows scripting conventions) and the absence of any Linux- or bash-specific examples (such as using curl or jq, or mentioning Linux shell environments) demonstrates a Windows-centric bias. Additionally, PowerShell is given equal prominence to CLI, and there is no mention of Linux-native tools or workflows.

Recommendations:

Add explicit bash/shell examples for Linux users, such as using curl to download the OpenAPI spec and az CLI commands in a Linux shell context.
Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary shell syntax differences.
If PowerShell is included, consider also including bash or zsh examples to ensure parity for Linux/macOS users.
Mention Linux and macOS compatibility in the prerequisites and tool installation sections.
Where possible, avoid Windows-centric terminology (such as 'cmdlet') or explain it for non-Windows 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 gives equal prominence to PowerShell (a Windows-centric tool) and includes detailed PowerShell instructions and context setup. There is no mention of Bash, Linux shell, or cross-platform scripting alternatives, and PowerShell is referenced in both prerequisites and example sections. The structure and language (e.g., 'Azure PowerShell') reinforce a Windows-first perspective, even though Azure CLI is cross-platform.

Recommendations:

Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes or examples where relevant.
Clarify that PowerShell Core is cross-platform, or provide Bash shell equivalents for context setup and scripting.
Balance the order of examples: alternate between CLI and PowerShell, or lead with CLI (as the more cross-platform tool).
In prerequisites, clarify that Azure CLI is available on all major platforms, and provide installation links for Linux/macOS.
Consider adding a short section or callout for Linux/macOS users, highlighting any differences or tips.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation page exhibits a strong Windows bias. All migration tools and examples focus exclusively on migrating ASP.NET apps from Windows/IIS environments, with repeated references to Windows-specific tools (App Service Migration Assistant, PowerShell scripts) and no mention of Linux-based migration scenarios or tools. The documentation does not provide guidance or examples for migrating .NET apps hosted on Linux servers, nor does it mention Linux-native web servers (e.g., Apache, Nginx) or command-line tools (e.g., Bash scripts).

Recommendations:

Add examples and guidance for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx) to Azure App Service.
Include Linux-specific migration tools or scripts, or clarify if such tools are not available.
Provide parity in documentation by offering both Windows (PowerShell) and Linux (Bash, shell script) command-line examples for migration tasks.
Mention any limitations or differences in migrating from Linux environments, and provide remediation steps or alternative approaches.
Explicitly state the supported source environments (Windows, Linux) at the beginning of the documentation.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates some Windows bias, particularly in the sections discussing configuration and process management. The only explicit tool mentioned for Node.js process management is PM2 on Linux, but the 'web.config' file and 'iisnode' settings are referenced without Linux equivalents or alternatives. The documentation refers to Windows-centric configuration patterns (web.config, iisnode) and does not provide parallel Linux-native examples or mention Linux-specific configuration files or process managers (other than PM2). There is also a tendency to mention Windows approaches first or exclusively, with Linux guidance appearing as an afterthought or in a limited context.

Recommendations:

For every mention of 'web.config' or 'iisnode', provide equivalent Linux-native configuration guidance (e.g., appsettings.json, environment variables, or nginx/apache configuration).
When discussing auto-healing or process management, include Linux-native approaches (such as systemd, supervisord, or Azure-specific Linux features) alongside Windows methods.
Ensure that examples and troubleshooting steps are provided for both Windows and Linux environments, and avoid assuming 'web.config' is universally applicable.
When referencing tools or configuration files, explicitly state which OS/platform they apply to, and offer alternatives for the other platform.
Consider providing side-by-side examples or a table comparing Windows and Linux approaches for common tasks (e.g., process management, configuration, diagnostics).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. The automation section provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) script examples, and the PowerShell example is given equal prominence to the CLI example, despite CLI being cross-platform. Portal instructions and screenshots do not show OS-specific differences, but the overall pattern is to mention or demonstrate Windows-first or Windows-specific tools.

Recommendations:

Alternate the order of Windows and Linux instructions/examples, or present Linux first in some sections.
Add bash shell script examples alongside Azure PowerShell, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
Where possible, provide Linux-specific guidance or screenshots if there are UI or workflow differences.
Consider including a table summarizing command differences for Windows and Linux users for clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by prioritizing Windows terminology, tools, and examples. PowerShell is presented as a primary automation tool, and while Azure CLI is cross-platform, there are no explicit Linux shell or scripting examples. Windows-specific features and limitations are discussed before Linux equivalents, and Linux automation or troubleshooting steps are not covered in parity with Windows.

Recommendations:

Provide Linux shell (bash) script examples alongside PowerShell for automation tasks.
Ensure that Linux-specific instructions (e.g., for custom containers) are as detailed as Windows instructions.
When listing features or limitations, present Linux and Windows information in parallel, not with Windows first.
Include troubleshooting steps or common issues for Linux deployments, not just Windows.
Clarify when instructions or features are platform-specific, and avoid assuming the reader is on Windows.
Add explicit examples for Linux container deployments, since the Premium V4 tier supports them.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first bias by focusing exclusively on ASP.NET web applications and development workflows typical of Windows environments. It references Visual Studio and Visual Studio Code, but does not provide explicit Linux or cross-platform instructions, nor does it mention Linux-specific tools or considerations. There are no examples or guidance for running, debugging, or deploying the application on Linux systems.

Recommendations:

Explicitly mention that .NET Core and ASP.NET Core are cross-platform and can be developed and run on Linux and macOS as well as Windows.
Provide Linux-specific instructions for installing the .NET SDK, creating projects, and running applications (e.g., using apt, yum, or snap for installation).
Include terminal commands and examples that are platform-agnostic or show both Windows (cmd/PowerShell) and Linux/macOS (bash) equivalents.
Reference popular Linux editors (such as VS Code, Vim, or JetBrains Rider) and include instructions for using them.
Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, HTTPS certificate trust, environment variables).
Clarify that the dotnet CLI commands work the same on Linux, and provide sample output or screenshots from a Linux terminal.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes the use of Visual Studio Code and its extensions, which are cross-platform, but all example instructions and screenshots are oriented toward the VS Code GUI and keyboard shortcuts (e.g., Ctrl+Shift+P) that are Windows-centric. There are no explicit Linux or macOS-specific instructions, nor are there any command-line alternatives or references to Linux-specific tools or patterns. The documentation does not mention any differences or considerations for Linux users, and the keyboard shortcuts and UI references are presented in a Windows-first manner.

Recommendations:

Include keyboard shortcut alternatives for macOS (e.g., Cmd+Shift+P) and mention that shortcuts may differ on Linux.
Explicitly state that the Visual Studio Code extension and instructions apply to Windows, Linux, and macOS, and note any platform-specific differences if they exist.
Provide command-line alternatives (such as using the Azure CLI or scripts) where possible, or clarify if only the GUI is supported.
Add screenshots or notes that reflect the appearance of the extension on Linux and macOS, if there are any differences.
Ensure that any referenced tools or processes (such as authentication flows) are validated and documented for Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently presents Bash examples first, followed by PowerShell. There is a note clarifying that examples can run in either shell and that differences in variable syntax are addressed with separate examples. No Windows-specific tools or patterns are mentioned, and Linux parity is generally maintained. However, the explicit labeling of 'Formatted for PowerShell' and the inclusion of PowerShell-specific syntax throughout indicate a slight bias toward Windows/PowerShell users, though not to the exclusion of Linux users.

Recommendations:

Continue to provide both Bash and PowerShell examples, but consider alternating the order in which they are presented or grouping them side-by-side to avoid implicit prioritization.
Explicitly state in the prerequisites that all examples are cross-platform and tested on both Windows (PowerShell) and Linux/macOS (Bash).
Where possible, use variable syntax that is compatible across shells, or provide a table summarizing syntax differences.
Ensure that any referenced scripts or downloadable assets are compatible with both Bash and PowerShell environments.

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 explicitly labeled and formatted, suggesting a focus on Windows users. Additionally, PowerShell examples are presented immediately after Bash, which may imply a slight Windows-first ordering. There are no Linux-specific tools or workflows mentioned beyond Bash, and no explicit mention of Linux environments.

Recommendations:

Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows, to help users identify the right commands for their platform.
Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows) examples, or use tabs to allow users to select their OS.
Add a brief note clarifying that Bash examples are intended for Linux/macOS terminals and PowerShell for Windows, ensuring parity in guidance.
If possible, include troubleshooting notes or environment setup tips for both Linux and Windows users.

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 immediately after the Bash examples. There is no explicit mention of Linux or macOS, and the PowerShell examples may suggest a Windows-first approach. However, Bash examples are present and shown first, which helps mitigate bias. No Windows-only tools or patterns are used, but the presence of PowerShell examples throughout and lack of explicit Linux/macOS references indicate a mild Windows bias.

Recommendations:

Explicitly mention that the Bash examples are suitable for Linux and macOS users, and the PowerShell examples are for Windows users.
Add a short note clarifying cross-platform compatibility of Azure CLI and the provided scripts.
Consider using tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for clearer parity.
Ensure that any platform-specific instructions (such as line continuation characters) are clearly explained for each OS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exclusively provides instructions using the Azure portal GUI, which is a cross-platform web interface but often aligns with Windows-centric workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. This can disadvantage Linux users who prefer or require CLI-based automation or scripting.

Recommendations:

Add equivalent Azure CLI examples for all steps, showing how to enable managed identity and assign roles via command line.
Explicitly mention that the Azure portal is web-based and platform-agnostic, but provide links or examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) automation.
Include a section comparing portal-based and CLI-based approaches, highlighting when each is appropriate.
Ensure that any future examples or screenshots do not assume a Windows environment (e.g., file paths, UI conventions).

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively references Visual Studio Code and its Azure extension, which are available cross-platform but are most commonly associated with Windows environments. There is no mention of Linux-specific tools, command-line alternatives, or instructions for Linux users. No examples or guidance are provided for users who may prefer or require Linux-native workflows.

Recommendations:

Explicitly mention that Visual Studio Code and the Azure API Center extension are available on Linux and macOS, not just Windows.
Provide alternative instructions or examples for Linux users, such as using the Azure CLI or other command-line tools where possible.
Include a note or section addressing Linux setup considerations, such as installation commands for VS Code and the extension on Linux distributions.
If relevant, mention any differences or limitations when using the tools on Linux compared to Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell is given equal prominence to CLI, which can be interpreted as a Windows-centric approach since PowerShell is primarily a Windows tool (despite cross-platform support). There is no mention of Linux-specific considerations, nor are there examples using native Linux tools or shell scripting. The order of presentation (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method, without similar attention to Bash scripting or Linux-native workflows, reflects a subtle Windows bias.

Recommendations:

Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
Consider adding a Bash shell script example for Linux users, especially for automation scenarios.
Clarify that PowerShell Core is cross-platform, but note that many Linux users may prefer Bash.
If referencing PowerShell, also reference Bash or other common Linux shells to ensure parity.
Add a brief section or note about running these commands on Linux, including any differences in file paths or environment setup.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes the use of Visual Studio Code and its Azure API Center extension, which are cross-platform, but it does not mention or provide any Linux-specific guidance, troubleshooting, or alternative workflows. There is an implicit Windows-first bias as there are no references to Linux environments, terminal commands, or platform-specific considerations. All instructions and screenshots are generic or implicitly Windows-oriented.

Recommendations:

Explicitly state that Visual Studio Code and the Azure API Center extension are available on Windows, macOS, and Linux.
Include notes or sections addressing any Linux-specific installation steps, such as using package managers (apt, yum, snap) for VS Code.
Provide screenshots or examples from Linux desktop environments to demonstrate parity.
Mention any known issues or differences in behavior on Linux, if applicable.
Add troubleshooting tips for Linux users, such as permissions or dependency issues.

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 is tightly coupled to the Microsoft ecosystem, with no guidance for users who may prefer or require Linux-based or open-source solutions.

Recommendations:

Provide alternative examples using Azure CLI or REST API calls that can be executed from any platform, including Linux.
Include guidance or examples for integrating with non-Microsoft notification systems (e.g., Slack, email, or webhooks) to demonstrate cross-platform compatibility.
Mention and link to automation options that are platform-agnostic, such as using GitHub Actions, Azure Functions (with code samples in bash or Python), or other open-source workflow engines.
Explicitly state that the workflow can be adapted for non-Windows environments and provide at least one example or reference for Linux users.
Where possible, avoid assuming the use of the Azure Portal GUI and provide equivalent command-line or API-based instructions.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation provides only .NET (C#) code samples and references the Azure portal GUI, both of which are more commonly associated with Windows environments. There are no Linux-specific or cross-platform CLI examples (such as Bash, curl, or Python), nor is there mention of Linux tools or workflows. The documentation implicitly assumes a Windows/.NET development environment, which may disadvantage Linux users.

Recommendations:

Add equivalent code samples using cross-platform languages such as Python (e.g., using boto3 and requests) to demonstrate calling the Bedrock API through API Management from Linux or macOS.
Include command-line examples using curl or HTTPie for invoking the API endpoint, which are standard on Linux systems.
Mention and provide examples for using the Azure CLI (az) for relevant configuration steps, as it is cross-platform.
Clarify that the .NET example is cross-platform, but explicitly state and show how to run it on Linux (e.g., using .NET Core on Ubuntu).
Where possible, avoid implying that the Azure portal is the only way to perform configuration; provide CLI or ARM template alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation demonstrates a moderate Windows bias. PowerShell examples are provided first and in greater detail, with variable setup and multiple access scenarios. Azure CLI (Bash) and REST examples are present, but PowerShell is prioritized and more thoroughly explained. There are no explicit Linux-specific tools or shell examples beyond Azure CLI, and no mention of Linux-native scripting or automation approaches. The documentation assumes familiarity with PowerShell, which is traditionally a Windows-centric tool, despite its cross-platform availability.

Recommendations:

Present Azure CLI (Bash) examples before or alongside PowerShell examples to avoid implying PowerShell is the primary or preferred approach.
Expand Azure CLI sections to match the detail and coverage of PowerShell sections, including variable setup and all access scenarios.
Explicitly mention that PowerShell and Azure CLI are both cross-platform, and clarify that all examples work on Linux, macOS, and Windows.
Where possible, add Linux-native automation examples (e.g., Bash scripts, cron usage) or reference Linux shell scripting in the context of automation.
Review language to ensure it does not assume a Windows environment or familiarity with Windows-specific tools.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools, Bash, or CLI alternatives. No command-line examples are provided, but the only automation tool specifically named is Azure PowerShell, which is primarily associated with Windows environments. There are no Linux-specific or cross-platform examples or tool mentions.

Recommendations:

When suggesting automation tools, mention cross-platform options such as Azure CLI (az), Bash scripts, or REST API calls alongside Azure PowerShell.
Provide example commands for both Azure PowerShell and Azure CLI to demonstrate parity.
Explicitly state that Azure CLI and REST API approaches are fully supported on Linux, macOS, and Windows.
Avoid implying that PowerShell is the default or only automation tool; present it as one of several options.
Consider including a table or section comparing how to perform key management tasks using PowerShell, Azure CLI, and REST API.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a bias towards Windows by only referencing the Azure portal (which is web-based and cross-platform, but often associated with Windows workflows) and .NET for gRPC client/server examples, without providing equivalent Linux or cross-platform command-line examples (e.g., using grpcurl, curl, or other open-source tools). There are no Linux-specific instructions or examples, and the only programming language ecosystem referenced is .NET, which is historically Windows-centric.

Recommendations:

Add examples for calling gRPC services using cross-platform tools such as grpcurl or Postman, including command-line instructions that work on Linux.
Include references or links to gRPC client/server tutorials in other languages (e.g., Python, Go, Java) that are commonly used on Linux.
Explicitly mention that the Azure portal is accessible from any OS, and consider providing Azure CLI or ARM/Bicep deployment examples from a Linux shell.
Balance .NET examples with equivalent Linux-friendly or open-source alternatives to ensure parity for non-Windows users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by only referencing ASP.NET Core and Visual Studio Code for creating and publishing web APIs, which are traditionally associated with Windows development environments. There are no examples or references for Linux-based frameworks, tools, or deployment workflows. The documentation does not mention or provide parity for Linux users or alternative stacks.

Recommendations:

Include examples for creating and publishing web APIs using popular Linux-based frameworks (e.g., Node.js/Express, Python/Flask, Java/Spring Boot) and show how to deploy them to Azure App Service.
Add instructions or links for deploying web apps to Azure from Linux environments using the Azure CLI, GitHub Actions, or other cross-platform tools.
Ensure that references to development tools (such as Visual Studio Code) clarify their cross-platform nature, and provide Linux-specific setup guidance where appropriate.
Provide sample commands or scripts for Linux shells (bash/zsh) alongside any PowerShell or Windows command examples, if relevant.
Explicitly state that Azure App Service and API Management support web apps developed and deployed from both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation primarily uses Azure Portal and Azure CLI examples, which are cross-platform, but there is a subtle Windows bias in the 'Test in virtual network' section where only nslookup is shown as the DNS utility example (nslookup is more commonly associated with Windows, though available on Linux). There are no PowerShell-specific or Windows-only tool examples, but Linux/Unix alternatives (like dig) are only mentioned in passing and not shown in example commands. The documentation does not provide explicit Linux shell or scripting examples, nor does it mention Linux-specific tools or workflows.

Recommendations:

When suggesting DNS utilities, provide both Windows (nslookup) and Linux (dig) command examples side by side.
Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell prompts for both (e.g., Bash and PowerShell).
Where possible, include Linux/Unix command-line examples (e.g., curl, dig) alongside any Windows-centric examples.
If referencing the Azure Portal, clarify that it is web-based and platform-agnostic.
Add a note or section for common troubleshooting or validation steps using Linux tools and shell environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily describes deploying an Azure API Management instance using the Azure portal, with only brief mentions of Azure PowerShell and Azure CLI as alternative methods. There are no explicit examples or instructions for using Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there any Linux-specific tools or terminal instructions. The mention of Azure PowerShell (traditionally Windows-centric) appears before Azure CLI, and no Linux shell or bash examples are provided.

Recommendations:

Add explicit, step-by-step instructions and code examples for deploying the ARM template using Azure CLI (az deployment), including sample commands.
Ensure that Azure CLI instructions are presented before or alongside Azure PowerShell, as CLI is cross-platform and widely used on Linux.
Include bash shell examples for common tasks such as resource cleanup, in addition to portal-based instructions.
Clarify that all command-line methods work on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
Consider adding a table or section summarizing all deployment options (Portal, CLI, PowerShell, REST API) with links or code snippets for each.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not provide any OS-specific command-line examples or tooling, but it also does not include any examples involving Windows, PowerShell, or Windows-specific tools. However, there is a subtle bias in that all UI navigation and instructions assume use of the Azure Portal web interface, which is platform-agnostic, but there are no CLI (Azure CLI, Bash, or PowerShell) examples provided. This omission may disadvantage Linux users who prefer or require command-line automation.

Recommendations:

Add equivalent Azure CLI examples for all major configuration steps, such as creating named values, configuring backends, and assigning managed identities.
Where possible, provide Bash shell snippets for API calls or configuration, especially for authentication flows.
Explicitly mention that all steps can be performed via the Azure CLI or REST API, and link to relevant documentation.
If showing policy XML, consider including example CLI commands to apply or update policies, not just portal navigation.
Ensure parity by including both command-line and portal-based instructions, catering to both Linux and Windows users.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions creating an Azure Kubernetes cluster using the Azure CLI, Azure PowerShell, or the Azure portal, with PowerShell (a Windows-centric tool) listed before the portal and after the CLI. However, the main deployment instructions use kubectl commands, which are cross-platform and standard for Kubernetes. No explicit Linux or Bash examples are missing, but the ordering in the prerequisites may subtly prioritize Windows tooling.

Recommendations:

List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in prerequisites to avoid suggesting a Windows-first approach.
Explicitly mention that all kubectl commands work on Windows, Linux, and macOS terminals.
If possible, provide links to Linux/macOS-specific instructions for creating AKS clusters, or clarify that the Azure CLI is recommended for all platforms.
Ensure parity in documentation by not listing Windows tools before cross-platform or Linux tools unless there is a technical reason.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides a hosts file editing example, mentioning the Windows path (%SystemDrive%\drivers\etc\hosts) before the Linux/macOS equivalent (/etc/hosts). No other OS-specific tools or commands are referenced, and no PowerShell or Windows-only tools are used elsewhere. However, the ordering prioritizes Windows.

Recommendations:

List Linux and Windows hosts file paths in parallel or mention Linux/macOS first to balance representation.
Where possible, provide explicit examples for both Linux and Windows, not just file paths but also editing commands (e.g., using 'nano /etc/hosts' for Linux, 'notepad' for Windows).
Review other documentation sections for similar ordering or implicit prioritization and adjust for parity.

Create pull request

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