← Back to Dashboard
227
Pages Scanned
32
Pages Flagged
227
Changed Pages
14.1%
% Pages Flagged

Scan Information

Started At: 2026-01-22 00:00:10

Finished At: 2026-01-22 00:24:27

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 227

Files Completed: 227

Problematic Pages

33 issues found
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on Windows tools and workflows, especially SignTool, PowerShell, and MSI/WinGet installers. All setup instructions and examples are Windows-specific, with no mention of Linux or macOS equivalents or alternatives. Even in sections about GitHub Actions and Azure DevOps, there are no explicit Linux/macOS instructions or parity notes.
Recommendations
  • Clearly state if Artifact Signing is Windows-only, or if Linux/macOS support is planned or available.
  • If cross-platform support exists (e.g., via GitHub Actions or SDKs), provide explicit Linux/macOS setup instructions and examples.
  • Add notes or sections for Linux/macOS users, including any limitations or alternative tools/workflows.
  • If only Windows is supported for certain integrations (like SignTool), clarify this early in the documentation.
  • For SDK-based integrations, provide cross-platform code samples and installation instructions.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments: all instructions, screenshots, and examples assume SQL Server is running on Windows VMs. Steps reference Windows-specific tools (SSMS, NT SERVICE accounts, Windows file paths), and PowerShell is the only automation example provided. There is no mention of Linux-based SQL Server VMs or guidance for Linux users, despite SQL Server on Linux being supported in Azure.
Recommendations
  • Add a section or callout clarifying whether the Azure Backup solution supports SQL Server on Linux VMs, and if not, state this explicitly.
  • If Linux is supported, provide parallel instructions for SQL Server on Linux VMs, including how to configure permissions, manage service accounts, and automate tasks using Bash or relevant Linux tools.
  • Include Linux file path examples and explain differences in service account management between Windows and Linux.
  • If some features (like the AzureBackupWindowsWorkload extension) are Windows-only, clearly state this at the beginning of the article.
  • Provide links to Linux-specific documentation or alternatives if full parity is not possible.
GitHub Create Pull Request
Azure Functions Azure Functions Core Tools reference ...cles/azure-functions/functions-core-tools-reference.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation for Azure Functions Core Tools is generally cross-platform, but several areas show Windows bias. Windows-specific issues (such as Python packaging problems on Windows) are called out, but Linux/macOS equivalents or best practices are not always equally emphasized. The 'managed-dependencies' option is noted as PowerShell-only, but Linux alternatives are not discussed. Some examples and notes (e.g., certificate creation for HTTPS) assume Windows defaults and do not clarify Linux/macOS differences. There is a lack of explicit Linux/macOS command-line examples, troubleshooting, or parity notes, especially for tasks like Docker usage, certificate management, and remote builds.
Recommendations
  • Add explicit Linux/macOS command-line examples and troubleshooting notes for common tasks (e.g., Docker usage, certificate management, remote builds).
  • Where Windows-specific issues are called out (e.g., Python packaging), provide Linux/macOS best practices and highlight differences.
  • Clarify when options or behaviors differ on Linux/macOS (e.g., certificate creation for HTTPS, local encryption of settings).
  • Ensure parity in examples and recommendations for PowerShell and other language runtimes, including Linux/macOS equivalents where applicable.
  • Consider adding a section summarizing cross-platform considerations and linking to OS-specific guidance.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation generally maintains platform neutrality, but there are several areas where Windows bias is evident. Hybrid Connections are explicitly Windows-only, and this is clearly stated. However, in the section on enabling dynamic scale monitoring for virtual network triggers, PowerShell and Azure CLI examples are provided, but the PowerShell example is shown after the CLI. There are no Linux/macOS-specific command examples or troubleshooting steps, and some subnet sizing recommendations mention Windows before Linux. The troubleshooting and automation sections reference Azure CLI and PowerShell, but do not mention Bash or Linux-specific tools. The overall impact is moderate, as Linux users can still complete most tasks, but may need to adapt instructions or seek additional guidance.
Recommendations
  • Provide Linux/macOS-specific command examples where relevant, especially for automation and troubleshooting.
  • When listing command-line examples, alternate or parallelize Azure CLI and PowerShell, and clarify cross-platform compatibility.
  • In subnet sizing recommendations, present Windows and Linux requirements in parallel rather than listing Windows first.
  • Add troubleshooting guidance for Linux/macOS environments where applicable.
  • Explicitly note when a feature (like Hybrid Connections) is Windows-only, as is already done, and provide alternative solutions for Linux users if possible.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation generally covers both Windows and Linux deployment options for Azure Functions, but there is a subtle Windows bias. Windows-based deployment technologies (such as Kudu/SCM, source control, Local Git, FTPS) are mentioned as 'Windows-only' in several places, and examples or tool references (Visual Studio, Azure CLI) are often presented without explicit Linux alternatives or parity. In some sections, Windows deployment mechanisms are described first or in more detail, while Linux-specific instructions (such as required environment variables for remote build) are presented later or as exceptions. There are few direct Linux command-line examples, and some deployment methods (source control, Local Git, FTPS) are not available for Linux Consumption plan users, but this is a platform limitation rather than a documentation bias.
Recommendations
  • Provide explicit Linux/macOS command-line examples alongside Windows/PowerShell ones, especially for Azure CLI and Core Tools usage.
  • Clarify tool parity for Linux users (e.g., Visual Studio Code, Azure CLI, Core Tools) and highlight any differences in workflow or prerequisites.
  • Where deployment methods are Windows-only due to platform limitations, clearly state this is a product constraint, not a documentation gap.
  • Add more guidance for Linux users on alternative deployment strategies when Windows-only methods are unavailable (e.g., using zip deploy or containers).
  • Consider reordering sections so that Linux and Windows deployment options are presented with equal prominence.
GitHub Create Pull Request
Azure Functions Monitor executions in Azure Functions .../main/articles/azure-functions/functions-monitoring.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is generally cross-platform and avoids Windows-specific bias in most sections. However, there are a few areas where Linux parity is lacking: performance counters are noted as unsupported on Linux, and the built-in log streaming method is unavailable for Linux Consumption plan apps. These limitations are mentioned, but no Linux alternatives or workarounds are provided. There is also a slight bias in referencing Windows-centric tools (App Service platform log streaming) without offering equivalent Linux guidance.
Recommendations
  • For sections where features are unavailable on Linux (e.g., performance counters, built-in log streaming for Consumption plan), provide Linux-specific alternatives or workarounds, such as using Live Metrics Stream or exporting logs to external systems.
  • Explicitly document differences in feature availability between Windows and Linux, and link to Linux-specific monitoring solutions where possible.
  • Where a feature is Windows-only, offer guidance on how Linux users can achieve similar monitoring outcomes, even if via different tools.
  • Consider adding example workflows for Linux users, especially for log streaming and performance monitoring.
GitHub Create Pull Request
Azure Netapp Files Create an SMB volume for Azure NetApp Files ...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example ⚠️ powershell_heavy
Summary
The documentation is focused on creating and managing SMB volumes for Azure NetApp Files, which is inherently a Windows-centric protocol. However, the sections on managing permissions and share properties exclusively reference Windows tools (MMC, Windows SMB client) and do not mention or provide guidance for Linux or macOS clients, which can also access SMB shares. There are no examples or instructions for mounting or managing SMB volumes from non-Windows systems.
Recommendations
  • Add a section or examples showing how to mount and access the SMB volume from Linux and macOS clients (e.g., using the 'mount -t cifs' command on Linux, or Finder on macOS).
  • Include instructions or references for managing SMB permissions from Linux (e.g., using 'smbclient', 'setfacl', or other Samba tools where applicable).
  • Clarify which management tasks must be performed from Windows and which can be performed from other platforms, to set user expectations.
  • Link to the 'Mount a volume for Windows or Linux virtual machines' article earlier in the workflow, especially in the 'Control access' section.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 3.x to 4.x ...rticles/azure-functions/migrate-version-3-version-4.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell script as the only example for identifying function apps to migrate, with no equivalent Azure CLI, Bash, or cross-platform example. PowerShell is a Windows-centric tool (despite cross-platform support, it's less common on Linux/macOS), and its exclusive use here may create friction for Linux/macOS users. Additionally, references to Azure PowerShell precede mention of other cross-platform tools.
Recommendations
  • Provide an equivalent Azure CLI (az) or Bash script example for identifying function apps to migrate, and present it alongside or before the PowerShell example.
  • Explicitly mention that users can use Azure CLI or the Azure Portal as alternatives to PowerShell for cross-platform compatibility.
  • Where possible, use neutral/cross-platform terminology (e.g., 'Use Azure CLI or PowerShell') rather than defaulting to PowerShell.
  • Consider adding a table or section comparing PowerShell and Azure CLI commands for common migration tasks.
GitHub Create Pull Request
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is primarily focused on Azure CLI usage, which is cross-platform. However, there are several instances of Windows bias: PowerShell objects and file paths are referenced first or exclusively (e.g., '.\OSSPolicy.json'), and the 'default PowerShell object' is described before CLI equivalents. The documentation assumes a Windows/PowerShell environment for file manipulation and command syntax, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • When referencing file paths, use platform-neutral syntax (e.g., './OSSPolicy.json') or provide both Windows ('.\file.json') and Linux/macOS ('./file.json') examples.
  • Avoid describing PowerShell objects as the default or primary method unless the documentation is specifically for PowerShell. Instead, focus on CLI and JSON file manipulation, which are cross-platform.
  • If mentioning PowerShell objects, immediately follow with equivalent Linux/macOS or Bash-based approaches.
  • Explicitly state that all Azure CLI commands work on Windows, Linux, and macOS, and clarify any OS-specific differences in file handling or command usage.
  • Add notes or examples for common Linux/macOS shell usage, such as using 'mv' instead of 'rename', or using '/' as the path separator.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation references PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and during the backup configuration process. While it briefly mentions alternatives like PG admin or PSQL, these are only listed as secondary options after PowerShell. There are no concrete examples or scripts provided for Linux/macOS users, and PowerShell is presented first and most prominently.
Recommendations
  • Provide explicit examples for granting privileges using psql (the standard PostgreSQL CLI tool available on Linux/macOS) alongside PowerShell.
  • List cross-platform or Linux-native tools (e.g., psql, bash scripts) before or alongside PowerShell in both the prerequisites and step-by-step instructions.
  • Include sample commands for both PowerShell and psql/PG admin where privilege assignment is required.
  • Clarify that PowerShell is not required and that all steps can be performed using platform-agnostic tools.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for backing up Azure Database for PostgreSQL server demonstrates a moderate Windows bias. It references PowerShell scripts as the primary method for granting database privileges, with alternatives (PG admin or PSQL tool) mentioned only secondarily and without example commands. No explicit Linux/macOS CLI examples or screenshots are provided, and the workflow assumes use of the Azure portal, which is cross-platform but does not address OS-specific command-line tooling. The PowerShell approach is presented first and in detail, while Linux-native tools are only briefly referenced.
Recommendations
  • Provide explicit example commands for granting database privileges using psql (Linux/macOS) and pgAdmin, alongside the PowerShell script.
  • Clarify that the PowerShell script can be run on Linux/macOS using PowerShell Core, or provide equivalent bash/psql scripts.
  • Add screenshots or step-by-step instructions for using Linux/macOS tools where applicable.
  • Ensure that any ARM template or automation instructions are OS-agnostic or include Linux/macOS usage notes.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page predominantly features Windows-centric examples and patterns. All code samples use C# and reference Windows VM images, with command lines using Windows syntax (cmd /c, backslashes). While Linux is mentioned in environment variable formatting and application ID restrictions, there are no Linux-specific code samples, shell command examples, or explicit guidance for deploying to Linux nodes. The documentation implicitly assumes Windows as the default platform, which may create friction for Linux/macOS users.
Recommendations
  • Add Linux-specific code samples, such as using Linux VM images in pool creation and shell command lines (e.g., bash syntax, forward slashes).
  • Include examples of referencing application packages in Linux tasks, showing environment variable usage in bash scripts.
  • Clarify any platform-specific differences in deployment, troubleshooting, and file paths.
  • Present Windows and Linux examples side-by-side where applicable, or clearly indicate platform-specific instructions.
  • Reference cross-platform tools and APIs, not only .NET/C#.
GitHub Create Pull Request
Cost Management Billing Manage Azure Reservations ...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell-only examples for splitting reservations, with no equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. The documentation also refers to PowerShell cmdlets as the primary automation method, rather than presenting CLI or API options first or alongside.
Recommendations
  • Add Azure CLI examples for splitting reservations, updating scope, and other management tasks.
  • Include REST API sample requests for reservation management operations.
  • Present CLI and API options alongside PowerShell, or list CLI first for cross-platform parity.
  • Explicitly mention that PowerShell examples are for Windows users and provide links to CLI/API docs for Linux/macOS users.
GitHub Create Pull Request
Cost Management Billing View Azure Reservation purchase and refund transactions ...nagement-billing/reservations/view-purchase-refunds.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page references Power BI as a method to view reservation transactions, which is primarily a Windows tool and does not mention cross-platform alternatives or clarify Power BI's availability on Linux/macOS. No command-line or scripting examples (e.g., Azure CLI, Bash, PowerShell) are provided for Linux/macOS users, and the REST API section lacks concrete usage examples. The page does not provide Linux/macOS-specific guidance or parity for viewing reservation transactions outside the Azure portal.
Recommendations
  • Clarify Power BI's platform support and mention any web-based or cross-platform alternatives for Linux/macOS users.
  • Add examples using Azure CLI or Bash scripts to retrieve reservation transactions via the REST API, ensuring Linux/macOS users have actionable guidance.
  • Provide sample REST API requests (e.g., using curl) for reservation transactions to help users on all platforms.
  • Explicitly state if certain tools (like Power BI) are Windows-only and suggest alternatives where possible.
GitHub Create Pull Request
Cost Management Billing Permissions to View and Manage Azure Reservations ...t-management-billing/reservations/view-reservations.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides detailed instructions for managing Azure reservations primarily through the Azure portal and Azure PowerShell. PowerShell is featured as the only command-line automation example, with no mention of Azure CLI or Bash/Linux-native tools. The 'Grant access by using PowerShell' section is the only automation example provided, and PowerShell is referenced before any Linux-friendly alternatives. This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, especially in the 'Grant access by using PowerShell' section.
  • Explicitly mention that Azure CLI can be used for RBAC and reservation management, and link to relevant Azure CLI documentation.
  • Where possible, provide Bash or shell script examples alongside PowerShell to improve accessibility for Linux/macOS users.
  • Clarify that PowerShell Core is cross-platform, but also highlight Azure CLI as a first-class alternative.
GitHub Create Pull Request
Cost Management Billing SQL IaaS extension registration options for Cost Management administrators ...billing/scope-level/sql-iaas-extension-registration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples and scripts exclusively for PowerShell, with no mention of Linux or macOS equivalents (such as Azure CLI or Bash). The registration process is described primarily through the Azure portal and PowerShell, both of which are Windows-centric. There are no instructions or examples for users on Linux or macOS platforms, creating friction for those users.
Recommendations
  • Provide Azure CLI and/or Bash script examples for checking and registering SQL IaaS Agent extension, alongside PowerShell.
  • Explicitly mention that the Azure portal is cross-platform and can be used from any OS, but clarify any limitations.
  • If any steps are Windows-specific, clearly label them and offer alternative instructions for Linux/macOS users where possible.
  • Link to cross-platform tooling documentation (e.g., Azure CLI docs) for managing SQL IaaS Agent extension.
GitHub Create Pull Request
Cost Management Billing Transition to centrally managed Azure Hybrid Benefit ...-management-billing/scope-level/transition-existing.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell script as the only example for analyzing SQL Server license usage across Azure subscriptions. There are no equivalent examples or guidance for users on Linux or macOS platforms, nor are cross-platform alternatives (such as Azure CLI, Bash, or REST API) mentioned. This creates friction for non-Windows users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or REST API for analyzing SQL Server license usage.
  • Clearly indicate whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation instructions if so.
  • If the script is Windows-only, explicitly state this and offer alternative methods for Linux/macOS users.
  • Wherever possible, present cross-platform solutions first or alongside PowerShell examples to ensure parity.
GitHub Create Pull Request
Dev Box Use Customizations to Connect to Azure Resources or Clone Private Repositories ...x/how-to-customizations-connect-resource-repository.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page provides YAML customization examples that consistently use Windows paths (e.g., C:\workspaces), references Windows base images, and demonstrates automation tasks using PowerShell and the Windows-specific winget package manager. There are no Linux/macOS equivalent examples, and Windows tools/patterns are presented exclusively. This creates friction for Linux/macOS users who may wish to use Dev Box customizations in non-Windows environments.
Recommendations
  • Add parallel examples using Linux/macOS paths (e.g., /home/dev/workspaces) and base images, where supported.
  • Provide sample tasks using bash or shell scripts instead of PowerShell, and use cross-platform package managers (e.g., apt, yum, brew) for installing CLI tools.
  • Clarify which features are Windows-only and which are cross-platform, so users know when Linux/macOS is supported.
  • If Dev Box customizations can be used with Linux images, include explicit Linux/macOS usage scenarios and YAML samples.
GitHub Create Pull Request
Event Grid Quickstart: Publish on an MQTT topic by using the CLI .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page exhibits Windows bias in the certificate generation section, where all example commands use PowerShell syntax and Windows-specific instructions (e.g., opening Command Prompt via Win+R and %USERPROFILE%). There are no Linux or macOS equivalents provided for generating certificates, viewing thumbprints, or file path conventions. The rest of the CLI instructions are cross-platform, but the initial setup creates friction for non-Windows users.
Recommendations
  • Provide Linux/macOS shell (bash) equivalents for certificate generation and thumbprint commands using step CLI.
  • Include instructions for opening a terminal and navigating to the user profile/home directory on Linux/macOS.
  • Use platform-neutral file path examples or clarify differences between Windows and Unix-like systems.
  • Explicitly state that the step CLI is cross-platform and link to installation instructions for Linux/macOS.
  • Add notes or tabs to switch between Windows and Linux/macOS instructions where commands differ.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for ExpressRoute virtual network gateways primarily provides Azure PowerShell examples and references PowerShell cmdlets for configuration tasks. There are no equivalent Azure CLI (cross-platform) or Bash examples shown for key operations such as subnet creation. The REST API is mentioned, but scripting guidance is focused on PowerShell, which is traditionally Windows-centric. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration snippets, especially for gateway subnet creation and management.
  • Explicitly mention that both PowerShell and Azure CLI can be used for these tasks, and link to CLI documentation.
  • Include Bash scripting examples where appropriate, or clarify cross-platform support for all tools.
  • Ensure REST API references are up-to-date and provide guidance for using them from Linux/macOS environments.
GitHub Create Pull Request
Firewall Monitor Azure Firewall ...e-docs/blob/main/articles/firewall/monitor-firewall.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform and focuses on Azure portal, Log Analytics, and Kusto queries, which are accessible from any OS. However, there is a notable Windows bias in the section about enabling Azure Firewall Fat Flow Log (Top flow log), which explicitly states that configuration must be done through Azure PowerShell. There are no Linux/macOS CLI or Azure CLI alternatives provided for this task, and PowerShell is a Windows-centric tool (though it can run on Linux, but is less commonly used there). Additionally, the tip about log converter tools references Visual Studio and C#, which are traditionally Windows development environments, though not strictly Windows-only.
Recommendations
  • Provide Azure CLI or REST API instructions for enabling Fat Flow Log, if available, to ensure Linux/macOS users can perform this configuration without relying on PowerShell.
  • If PowerShell is the only supported method, clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS users.
  • Offer alternative log conversion tools or scripts (e.g., Python, Bash) for users who do not use Visual Studio or C#.
  • Explicitly mention that all log viewing and analysis tasks (JSON, CSV, Kusto queries, Azure portal workbooks) are fully supported on Linux/macOS.
GitHub Create Pull Request
Azure Functions Event-driven Scaling in Azure Functions .../main/articles/azure-functions/event-driven-scaling.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring scale limits, but PowerShell is presented as a primary tab alongside CLI, and there are no explicit Linux/macOS shell examples (e.g., Bash, zsh). The only OS-specific note is about Windows Consumption plan apps and drain mode, but this is a factual distinction, not a bias. Overall, the examples and instructions are cross-platform, but the prominence of PowerShell and lack of explicit Linux/macOS shell commands may create minor friction for non-Windows users.
Recommendations
  • Add explicit Bash or shell examples for configuration tasks, especially where PowerShell is shown.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Where PowerShell is presented, consider adding a note or alternative for Linux/macOS users who may not use PowerShell.
  • Ensure that any OS-specific behaviors (like drain mode for Windows Consumption plan apps) are clearly marked as such and alternatives or clarifications for Linux/macOS are provided if relevant.
GitHub Create Pull Request
Azure Functions App settings reference for Azure Functions ...ain/articles/azure-functions/functions-app-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are minor instances of Windows bias: some examples use Windows-style paths (e.g., %HOME%\typescript), and in a few cases, Windows-specific settings (like WEBSITE_NODE_DEFAULT_VERSION) are presented before Linux equivalents or without Linux alternatives. Additionally, references to using Azure CLI or Azure PowerShell for managing settings may implicitly favor Windows users, though CLI is cross-platform.
Recommendations
  • Where paths or environment variables are shown, provide both Windows and Linux/macOS examples (e.g., %HOME%\typescript and $HOME/typescript).
  • When mentioning tools for managing settings (Azure CLI, PowerShell), clarify that Azure CLI is cross-platform and provide Bash or shell examples where appropriate.
  • For settings that are OS-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION), explicitly state their applicability and, where possible, provide Linux/macOS equivalents or alternatives.
  • Ensure that examples and explanations do not default to Windows conventions unless the setting is Windows-only.
GitHub Create Pull Request
Azure Functions Use Python and TensorFlow for machine learning in Azure ...ure-functions/functions-machine-learning-tensorflow.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides platform-specific instructions for creating and activating Python virtual environments, copying files, and running HTTP servers, with examples for Bash (Linux/macOS), PowerShell, and Cmd (Windows). However, Windows examples (PowerShell and Cmd) are consistently listed after Bash, and Windows-specific tools (such as 'py' launcher and registry edits) are mentioned. There is a notable Windows troubleshooting section for long path issues, but Linux/macOS equivalents are not discussed. The documentation does include Bash examples and notes for Linux users, but Windows-specific instructions and troubleshooting are more detailed.
Recommendations
  • Ensure troubleshooting sections include Linux/macOS equivalents where relevant (e.g., file path issues, permissions).
  • Balance troubleshooting advice for Windows and Linux/macOS users.
  • Where Windows-specific tools (like 'py' launcher) are mentioned, clarify Linux/macOS alternatives (e.g., always use 'python3').
  • Consider listing Bash (Linux/macOS) and Windows examples in alternating order, or clarify that all platforms are equally supported.
  • Add notes about common Linux/macOS issues (e.g., permissions, package installation errors) where Windows-specific issues are discussed.
GitHub Create Pull Request
Azure Functions Memory profiling of Python apps in Azure Functions ...es/azure-functions/python-memory-profiler-reference.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation generally provides cross-platform instructions and examples, but in the 'Profile Python function app in local development environment' section, Windows commands and terminology are presented before Linux equivalents (e.g., 'py -m venv .venv' for Windows is listed before 'python3 -m venv .venv' for Linux, and PowerShell activation before Linux shell). This is a minor ordering bias, but Linux users are not blocked and all necessary Linux commands are present.
Recommendations
  • Present Linux and Windows commands in parallel tabbed sections or side-by-side for parity.
  • When listing commands for both platforms, alternate which platform is shown first, or clarify that both are equally supported.
  • Explicitly mention macOS where relevant (e.g., 'Linux/macOS shell') to cover all non-Windows users.
  • Consider using tabbed code blocks for 'Windows', 'Linux', and 'macOS' where commands differ.
GitHub Create Pull Request
Backup Use Azure Backup Server to back up workloads ...articles/backup/backup-azure-microsoft-azure-backup.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_only ⚠️ windows_tools ⚠️ missing_linux_example
Summary
This documentation is focused exclusively on Microsoft Azure Backup Server (MABS), which is designed to run only on Windows Server. All installation, configuration, and operational steps assume a Windows Server environment, with no mention of Linux or macOS support or equivalents. All examples, tools, and instructions are Windows-centric, including registry edits, PowerShell cmdlets, and references to Windows-only features like Windows Server Deduplication.
Recommendations
  • If MABS is Windows-only by design (as appears here), clarify this explicitly at the start of the documentation to set expectations for cross-platform users.
  • If any cross-platform alternatives exist (such as Azure Backup for Linux workloads via other agents or services), provide prominent links or references to those solutions.
  • Consider adding a comparison or guidance section for users seeking Linux or macOS backup solutions in Azure, pointing to relevant Azure documentation.
  • Ensure that any shared or related documentation (such as for the MARS agent or Recovery Services vaults) clearly distinguishes which features are Windows-only and which are cross-platform.
GitHub Create Pull Request
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Windows and Linux instructions for installing the Azure VM agent, but the Windows instructions are listed first in the relevant table. All other instructions are platform-agnostic, as the process is performed through the Azure Portal UI and not via OS-specific tools or scripts. No PowerShell, Windows command-line, or Windows-only tools are mentioned outside of the agent installation section.
Recommendations
  • Present Linux and Windows agent installation instructions in parallel or alternate which is shown first.
  • Explicitly state that all portal-based steps apply equally to both Windows and Linux VMs.
  • Where relevant, provide links to both Windows and Linux troubleshooting or reference guides.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. In browser support, Windows browsers are mentioned first and more options are listed for Windows than Mac. Keyboard layout instructions are only provided for Windows, with no guidance for Linux or macOS users. Some sections reference Windows-specific tools or patterns (e.g., Windows key, Windows toolbar) without Linux/macOS equivalents. There are no explicit Linux/macOS examples for tasks like keyboard layout configuration or file transfer.
Recommendations
  • In the browser support section, list supported browsers for all platforms equally and avoid mentioning Windows first unless there is a technical reason.
  • For keyboard layout configuration, provide instructions for Linux and macOS users in addition to Windows.
  • When referencing keyboard shortcuts or OS-specific actions (e.g., 'Click the Windows key'), include equivalents for Linux (e.g., Super key) and macOS (e.g., Command key) where applicable.
  • For file transfer and native client usage, clarify support and provide examples for Linux/macOS clients (e.g., using SSH/SCP from a Mac or Linux terminal).
  • Review the documentation for other subtle Windows-centric language and add Linux/macOS parity where possible.
GitHub Create Pull Request
Batch Jobs and tasks in Azure Batch .../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation generally maintains cross-platform language, but there are subtle signs of Windows bias. In the section on specifying the task command line, the Windows example ('cmd /c MyTaskApplication.exe %MY_ENV_VAR%') is shown before the Linux example ('/bin/sh -c MyTaskApplication $MY_ENV_VAR$'). Additionally, in the 'Start task' section, the documentation suggests using 'robocopy' and 'setup.exe' or MSI installers as examples of setup operations, which are Windows-specific tools and formats. There are no Linux-specific tool examples (e.g., 'cp', 'tar', 'bash', '.sh' scripts) provided in these contexts.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side by side to avoid implicit prioritization.
  • When mentioning Windows-specific tools like 'robocopy' or 'setup.exe', also provide equivalent Linux examples such as 'cp', 'rsync', or '.sh' scripts.
  • Explicitly state that the examples apply to both Windows and Linux nodes, and provide guidance or links for common Linux setup patterns.
  • Where possible, use neutral language or clarify when an example is platform-specific.
GitHub Create Pull Request
Batch Configure node endpoints in Azure Batch pool ...lob/main/articles/batch/pool-endpoint-configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides parallel examples for both Windows (RDP) and Linux (SSH) pools, using C# for Windows and Python for Linux. However, in each example pair, the Windows/RDP example is presented first, followed by the Linux/SSH example. This ordering may subtly signal a Windows-first bias, though the technical content is balanced and both platforms are covered equally.
Recommendations
  • Alternate the order of examples so that Linux/SSH examples are sometimes presented first.
  • Add a brief statement at the start clarifying that Azure Batch supports both Windows and Linux pools equally.
  • Consider providing both C# and Python code snippets for each scenario, regardless of OS, to further reinforce parity.
  • Explicitly mention that the configuration approach is identical for both platforms, with only the protocol/port differing.
GitHub Create Pull Request
Batch Batch security and compliance best practices ...cs/blob/main/articles/batch/security-best-practices.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation generally covers both Linux and Windows for Azure Batch, but there are subtle signs of Windows bias. Windows-specific tools (PowerShell) and documentation links are mentioned before Linux equivalents in several places, and Windows OS configuration guidance is more detailed. For example, the section on discovering image EOL dates lists PowerShell before Azure CLI, and the TLS configuration section provides Windows registry links without Linux equivalents. The documentation also references RDP before SSH when discussing remote access. However, Linux is acknowledged as a supported platform and most guidance is applicable to both OS types.
Recommendations
  • When listing tools or commands, alternate or list Linux/Azure CLI examples before or alongside Windows/PowerShell examples.
  • Provide equivalent Linux guidance for OS-level security settings (e.g., TLS/cipher suite configuration) and link to relevant Linux documentation.
  • When discussing remote access, mention SSH before or alongside RDP, and clarify Linux-specific procedures where relevant.
  • Ensure that all examples and references to command-line tools include both PowerShell and Azure CLI (or Bash) options.
  • Add explicit Linux security best practices where Windows-specific advice is given.
GitHub Create Pull Request
Batch Create a simplified node communication pool without public IP addresses ...tch/simplified-node-communication-pool-no-public-ip.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally maintains cross-platform neutrality, but some sections show mild Windows bias. In troubleshooting, Windows PowerShell commands (Test-NetConnection) are presented before Linux equivalents (nc), and the Windows command is more verbose. There are no explicit Linux/macOS CLI examples for pool creation, and the Azure portal instructions do not mention platform-specific differences. REST API and ARM template examples use Ubuntu images, which is positive for Linux parity.
Recommendations
  • Present Linux and Windows troubleshooting commands side-by-side, with equal detail and explanation.
  • Include explicit Azure CLI examples for pool creation, showing both Windows and Linux usage.
  • Ensure that command-line instructions and screenshots do not assume Windows as the default platform.
  • Where PowerShell is mentioned, also mention Bash or other Linux-native tools if applicable.
GitHub Create Pull Request
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page for 'Code to cloud options in Azure Container Apps' demonstrates minor Windows bias. Visual Studio (Windows-only) is mentioned before Visual Studio Code (cross-platform), and deployment examples/resources focus on Visual Studio first. In the Infrastructure as Code section, PowerShell is mentioned alongside Bash, but no Linux/macOS-specific CLI usage or examples are provided. There are no explicit Linux/macOS examples or screenshots, and Windows tooling (Visual Studio, PowerShell) is referenced before or more prominently than Linux equivalents.
Recommendations
  • Present Visual Studio Code (cross-platform) examples before or alongside Visual Studio, clarifying platform compatibility.
  • Include explicit Bash and Linux/macOS CLI usage examples or screenshots where automation is discussed.
  • Add notes or sections highlighting Linux/macOS workflows, such as using Docker CLI, Azure CLI in Bash, or VS Code on Linux/macOS.
  • Balance references to PowerShell and Bash, ensuring Linux/macOS users see their preferred shell represented equally.
  • Where possible, clarify which tools are Windows-only and which are cross-platform.
GitHub Create Pull Request