← Back to Dashboard
245
Pages Scanned
44
Pages Flagged
245
Changed Pages
18.0%
% Pages Flagged

Scan Information

Started At: 2026-02-04 00:00:07

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 245

Files Completed: 245

Problematic Pages

45 issues found
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is written with a clear Windows bias: it instructs users to create a .NET Framework console app in Visual Studio, which is only available on Windows. There are no instructions or examples for Linux/macOS users (e.g., using .NET Core/.NET 5+, cross-platform editors, or command-line tools). The steps and code samples assume a Windows development environment.
Recommendations
  • Add instructions for creating a cross-platform .NET console application (using .NET Core or .NET 5+) that can run on Linux/macOS.
  • Include examples using command-line tools (dotnet CLI) for project creation and NuGet package installation.
  • Mention alternative editors (e.g., VS Code) and how to set up the project outside Visual Studio.
  • Clarify in the introduction if the sample is Windows-only, or update the sample to be cross-platform if possible.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling (PSCredential, PowerShell cmdlets, Windows PowerShell examples) for managing credentials in Azure Automation. While Python examples are provided, there is no mention of Linux shell (bash) or cross-platform CLI alternatives, and the PowerShell/Windows approach is presented first and in more detail. The documentation assumes the use of PowerShell, which is traditionally a Windows tool, and does not address Linux/macOS users who may prefer bash, Azure CLI, or other cross-platform methods.
Recommendations
  • Add Azure CLI examples for credential management, especially for creating and retrieving credentials, to support Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) is supported and provide examples for cross-platform PowerShell usage.
  • Explicitly mention platform requirements and alternatives for users who do not use Windows or PowerShell.
  • Include notes or sections on how Linux/macOS users can interact with Azure Automation credentials, if possible.
  • If PowerShell is required, state this clearly at the beginning and provide guidance for installing PowerShell Core on non-Windows platforms.
GitHub Create Pull Request
App Service Use TLS/SSL Certificates in App Code ...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides detailed, step-by-step code examples for accessing certificates in Windows apps (including C# and Java using the Windows certificate store), but offers only brief or generic guidance for Linux apps and containers. Linux-specific code samples are limited to C#, with other languages (Node.js, PHP, Python, Java) being referenced only as 'see the documentation for the respective language.' Windows patterns and tools (certificate store, thumbprint usage, environment variables) are explained in detail and appear first in most sections, while Linux equivalents are less emphasized or missing.
Recommendations
  • Add concrete code examples for loading certificates in Linux containers for popular languages such as Node.js, Python, Java, and PHP.
  • Provide more detailed explanation of Linux certificate handling patterns, including how to use environment variables and file paths in various languages.
  • Ensure Linux and Windows guidance are presented in parallel, with equal detail and visibility.
  • Include links to relevant Linux language documentation or official guides for certificate handling.
  • Consider adding a comparison table or section summarizing differences and similarities between Windows and Linux certificate access in App Service.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page provides environment variable references for Azure App Service, covering both Windows and Linux scenarios. However, there is a noticeable bias toward Windows: Windows paths and conventions are often mentioned first, Windows-specific tools (such as msbuild, Web Deploy/MSDeploy, IIS, and .NET Framework) are referenced without equal Linux alternatives, and examples frequently use Windows-style paths (e.g., D:\home) or reference Windows-only features. In several cases, Linux equivalents are mentioned later or not at all, and some sections (such as build automation) provide more detail for Windows (Kudu) than Linux (Oryx).
Recommendations
  • Ensure Linux paths and conventions are presented alongside Windows examples, ideally with equal prominence.
  • Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide Linux alternatives or clarify when features are Windows-only.
  • Add Linux/macOS-specific examples and usage notes where currently only Windows examples are given.
  • In tables and lists, alternate the order of Windows and Linux references, or group them by platform for clarity.
  • Expand documentation for Linux build automation (Oryx) to match the detail provided for Windows (Kudu).
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.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 a detailed PowerShell example for enabling diagnostic logging but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line instructions are Windows-centric (PowerShell), and the referenced log converter tool is a .NET/C# utility, which is more familiar to Windows developers. There is no mention of Azure CLI, Bash, or cross-platform alternatives for enabling or managing diagnostic settings.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script snippets where appropriate, especially for tasks like downloading and converting logs.
  • Reference cross-platform log conversion tools or provide instructions for using Python or other open-source utilities to process logs.
  • Ensure that command-line instructions are presented for both PowerShell and Azure CLI, ideally with CLI examples shown first or side-by-side.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.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 for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling based on PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The documentation assumes users are familiar with PowerShell and does not mention or provide alternatives for those using Linux/macOS environments, despite Azure PowerShell being cross-platform. This creates friction for users who prefer or require Bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) commands and scripts for all migration steps, including resource ID retrieval, certificate management, and gateway creation.
  • Explicitly state that Azure PowerShell is available on Linux/macOS and in Azure Cloud Shell, and provide instructions for installing/running PowerShell on those platforms.
  • Provide Bash script examples or guidance for certificate handling and automation tasks where possible.
  • Include a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
  • Clarify any limitations or requirements for running the provided scripts on non-Windows platforms.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page includes a 'Next steps' section that links to a tutorial specifically for creating an autoscaling, zone redundant application gateway using Azure PowerShell. No equivalent Linux/macOS CLI (az CLI, Bash, etc.) example or tutorial is referenced, which may create friction for non-Windows users. The main content does not reference Windows-specific tools, but the PowerShell tutorial is highlighted before any cross-platform alternatives.
Recommendations
  • Add links to tutorials or examples using Azure CLI (az), which is cross-platform and preferred by many Linux/macOS users.
  • Ensure that any step-by-step guides for configuring autoscaling and zone redundancy are available for both PowerShell and Azure CLI.
  • In the 'Next steps' section, present cross-platform options (Azure CLI, REST API, ARM templates) alongside PowerShell, or list Azure CLI first to avoid implicit Windows-first bias.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Migration guidance and preview registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The primary tutorial linked is also PowerShell-focused, and there is no mention of Linux/macOS workflows or parity in command-line tooling.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
  • Include links to tutorials or quickstarts that use Azure CLI and ARM templates, not just PowerShell.
  • Explicitly mention that all features and management operations are available cross-platform, and clarify any exceptions.
  • Where possible, show both PowerShell and CLI examples side-by-side, or indicate which commands work on Linux/macOS.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, including configuration and public IP retention. There are no CLI (az), Bash, or Linux/macOS-specific migration instructions or examples provided. The exclusive focus on PowerShell may create friction for users on Linux or macOS platforms who prefer or require cross-platform tools.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for migration steps, especially for configuration migration and public IP retention.
  • Include Bash or shell script examples where appropriate, or clarify if PowerShell scripts are compatible with PowerShell Core on Linux/macOS.
  • Explicitly mention cross-platform options and limitations, and link to relevant Linux/macOS documentation if available.
  • Order migration tooling sections to present CLI and PowerShell options equally, or clarify if PowerShell is required and why.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.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 tutorial is heavily focused on Azure PowerShell, with all setup and configuration steps provided exclusively as PowerShell commands. It assumes the use of Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate) and file paths (e.g., c:\appgwcert.pfx), with no mention of Bash, Azure CLI, or Linux/macOS alternatives for certificate creation or resource management. There are no instructions or examples for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all steps, especially for resource creation and management.
  • Include instructions for generating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and explain how to export to PFX format.
  • Use platform-agnostic file paths or clarify how to adapt file paths for non-Windows systems.
  • Add a note at the beginning clarifying that the tutorial is PowerShell-focused, and link to a CLI-based or cross-platform version if available.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows, with no mention of Bash, Python, or Linux-native tooling for asset migration. While the page states applicability to both Linux and Windows VMs, all migration examples and instructions are PowerShell-based, and tabs/links default to Windows-centric instructions. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is required and supported.
  • Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS users.
  • Add examples or guidance for running migration tasks from Linux/macOS environments.
  • Where possible, offer Azure CLI alternatives to PowerShell cmdlets for common operations.
  • Reorder or balance examples so Linux and Windows approaches are presented equally.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.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 shows moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., data retention, backup, DSC configurations), while Linux equivalents are missing or only briefly referenced. Although there is a Linux-specific TLS upgrade example, most automation and backup instructions assume Windows/PowerShell usage, creating friction for Linux users.
Recommendations
  • Provide Linux CLI (az CLI, Bash, or Python) examples alongside or before PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
  • Include instructions or references for managing DSC nodes, assets, and runbooks from Linux environments (e.g., using Azure CLI, REST API, or SDKs).
  • Balance the order of presentation so that Linux and Windows guidance are given equal prominence.
  • Where PowerShell is referenced, clarify if cross-platform PowerShell Core can be used, or provide alternative Linux-native approaches.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. Nearly all code examples, parameter handling, and automation scenarios are shown using PowerShell, PowerShell Workflow, or C# SDK, with only brief mention of Python runbooks. There are no examples using Bash, Azure CLI, or Linux-native tools for starting or interacting with runbooks. The only non-PowerShell runbook type discussed is Python, and even then, only minimal guidance is given. All examples for starting runbooks from the command line use PowerShell cmdlets, and there is no parity for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add examples for starting and passing parameters to runbooks using Azure CLI (az automation runbook start) with equivalent parameter handling.
  • Include Bash shell examples for interacting with the REST API (using curl/jq) to start runbooks and pass parameters.
  • Expand the Python runbook section with more detailed examples, including parameter handling and invocation from Linux/macOS environments.
  • Clearly indicate which features or examples are Windows/PowerShell-specific, and provide Linux/macOS alternatives where possible.
  • Add a table or section comparing PowerShell, Azure CLI, and REST API approaches for cross-platform automation.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.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 detailed PowerShell instructions and a dedicated PowerShell section, but does not offer equivalent Linux/macOS shell (e.g., Bash) or cross-platform scripting examples for connecting to Azure Government. While Azure CLI is mentioned (which is cross-platform), the PowerShell section is more extensive, and no Linux-specific guidance or examples are provided. The ordering also places PowerShell after CLI, but the PowerShell section is more detailed and includes multiple command types.
Recommendations
  • Add explicit Bash or Linux/macOS shell examples for connecting to Azure Government and using Azure NetApp Files, especially for authentication and endpoint configuration.
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS as well as Windows.
  • Where PowerShell is referenced, consider providing equivalent Bash or shell script snippets, or at least link to Linux/macOS-specific guidance.
  • Add a brief section or note for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.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 for setting up signing integrations with Artifact Signing is heavily focused on Windows. The main integration detailed is SignTool, which is Windows-only, and all setup instructions (including installation, prerequisites, and usage) assume a Windows environment. Examples use PowerShell and reference Windows-specific tools like MSI installers, WinGet, and Visual Studio Installer. There are no Linux or macOS equivalents or alternative instructions provided for non-Windows users, even though some integrations (e.g., GitHub Actions, SDK) could be cross-platform.
Recommendations
  • Clearly indicate that SignTool integration is Windows-only, and provide guidance for Linux/macOS users on alternative signing methods.
  • Add explicit instructions or examples for using Artifact Signing with cross-platform tools (e.g., GitHub Actions, Azure DevOps, SDK) on Linux/macOS.
  • Where possible, provide parity for installation and usage steps for non-Windows environments (e.g., .NET runtime installation on Linux/macOS, using the SDK from Linux).
  • Reorder or separate sections so that cross-platform options are presented before or alongside Windows-specific instructions.
  • Include a table or matrix summarizing which integrations are supported on which operating systems.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples are in PowerShell, and references are made to 'Windows PowerShell' and Windows-specific modules. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting approaches. The documentation assumes the use of PowerShell, which, while available cross-platform, is still more familiar to Windows users. The term 'Windows PowerShell' is used, and no parity is provided for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash for Linux/macOS users, especially for credential asset creation and runbook management.
  • Clarify that PowerShell Core (pwsh) is cross-platform and supported, and update terminology to avoid 'Windows PowerShell' unless specifically required.
  • Provide guidance or links for installing and using PowerShell on Linux/macOS if PowerShell is required.
  • Mention and, where possible, provide examples for using REST APIs or SDKs (e.g., Python, .NET) for automation tasks.
  • Explicitly state if certain features are only available via PowerShell or Windows, and offer alternatives if available.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.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 managing certificates in Azure Automation is heavily focused on PowerShell-based workflows and cmdlets, which are most commonly used on Windows. All detailed examples for certificate creation and management use PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. The Python section provides parity for retrieving certificates in runbooks, but creation and management are exclusively shown with PowerShell. The portal instructions also recommend PowerShell as a workaround for CSP accounts, again prioritizing Windows tooling.
Recommendations
  • Add Azure CLI examples for certificate creation, management, and retrieval, as Azure CLI is cross-platform.
  • Include Bash or shell script snippets for common certificate operations, especially for uploading and managing certificates.
  • Explicitly note any limitations or differences for Linux/macOS users in Azure Automation, and provide guidance for those platforms.
  • Reorder or balance examples so that PowerShell and cross-platform methods (CLI, Python) are presented equally, or at least clarify that PowerShell is not required on non-Windows systems.
GitHub Create Pull Request
Azure Change Tracking Inventory Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent ...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation covers both Windows and Linux in general terms, but there is a notable Windows bias in the registry tracking section, which exclusively lists Windows registry keys and provides no Linux equivalent (such as configuration file or daemon tracking examples). Windows terminology and features (e.g., registry, Internet Explorer, explorer.exe) are described in detail, while Linux-specific mechanisms are not discussed. Examples and screenshots mention both platforms, but Windows concepts are presented first and in more depth.
Recommendations
  • Add equivalent Linux examples for configuration tracking, such as monitoring changes to /etc files, systemd unit files, or other common Linux configuration locations.
  • Include a table or section describing how Linux daemons and configuration files are tracked, with concrete examples.
  • Balance the depth of explanation for Windows registry with similar coverage for Linux configuration tracking.
  • Where screenshots or examples are provided, alternate between Windows and Linux, or show both side-by-side.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation for Azure Functions Core Tools is generally cross-platform, but several areas show Windows bias. Windows-specific tools and behaviors (such as PowerShell managed dependencies, .NET Framework, and storage emulator references) are mentioned without equivalent Linux/macOS alternatives or with Windows-first phrasing. Some examples and warnings (e.g., Python packaging issues on Windows) highlight Windows as the default environment, and Linux/macOS users may need to infer or research their own approaches. There are references to Windows-only features (like the Microsoft Azure Storage Emulator) without clear Linux/macOS alternatives. PowerShell is called out as a supported worker runtime, but Linux shell scripting is not mentioned. In some sections, Windows behaviors or tools are described before Linux equivalents.
Recommendations
  • Where Windows-only tools (e.g., Microsoft Azure Storage Emulator) are mentioned, add explicit Linux/macOS alternatives (such as Azurite) and link to relevant setup guides.
  • When discussing managed dependencies for PowerShell, clarify Linux/macOS support or limitations.
  • Add more explicit Linux/macOS usage notes, especially for commands that behave differently or require additional steps on non-Windows platforms (e.g., Python packaging, Docker usage).
  • Ensure examples and troubleshooting tips are provided for Linux/macOS users, not just Windows.
  • Avoid Windows-first phrasing; present cross-platform instructions or clearly indicate platform-specific steps.
  • Where PowerShell is referenced, mention Bash/zsh scripting as alternatives for Linux/macOS users.
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 covers networking options for Azure Functions across hosting plans and platforms. However, there are several areas where Windows bias is evident: Hybrid Connections are only supported on Windows, and this is clearly stated. In automation and configuration sections, examples are given for Azure CLI, PowerShell, and portal, but PowerShell is a Windows-specific tool and is presented alongside CLI. There is a recommendation for subnet sizing that distinguishes between Windows and Linux, but Windows is mentioned first. No Linux/macOS-specific troubleshooting or tool guidance is provided, and the documentation does not offer parity in examples for Linux users (e.g., Bash scripts, Linux-native tools).
Recommendations
  • For automation/configuration examples, provide Bash or shell script equivalents alongside PowerShell, especially for tasks that can be performed cross-platform.
  • Where PowerShell is used, clarify that Azure CLI is fully supported on Linux/macOS and provide CLI-first examples.
  • In subnet sizing recommendations, present Linux and Windows requirements with equal prominence, or list Linux first in some cases.
  • For troubleshooting, mention Linux/macOS-compatible tools or approaches (e.g., using Azure CLI, curl, or other network utilities).
  • Explicitly state when a feature is Windows-only (as is done for Hybrid Connections) and, where possible, offer Linux alternatives or workarounds.
GitHub Create Pull Request
Azure Functions Migrate C# app from in-process to isolated worker model ...es/azure-functions/migrate-dotnet-to-isolated-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides only Azure PowerShell scripts for identifying function apps to migrate, with no mention of Azure CLI or Bash alternatives. PowerShell is Windows-centric, and presenting it as the sole option creates friction for Linux/macOS users. Additionally, PowerShell is introduced before any cross-platform alternatives, which are absent.
Recommendations
  • Add equivalent Azure CLI (az) commands and Bash examples for identifying function apps to migrate.
  • Explicitly mention that Azure CLI is available and cross-platform, and provide links or examples.
  • Where PowerShell is used, clarify that it is available on Linux/macOS, but also offer CLI/Bash alternatives for parity.
  • Review other sections for tooling references and ensure cross-platform instructions are present where relevant.
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.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 provides both Windows and Linux guidance, but Windows/PowerShell examples and instructions are often presented first or in more detail. PowerShell is included as a first-class method for viewing and updating settings, while Linux-specific instructions (especially for pinning runtime versions) are less prominent and require more manual steps. Some Linux operations (like setting linuxFxVersion) are not available in the portal or PowerShell, but this is explained. However, the overall structure and example order favor Windows users.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than listing Windows/PowerShell first.
  • Add explicit Linux CLI examples for all tasks, including viewing/updating app settings, not just for linuxFxVersion.
  • Clarify limitations for Linux users up front (e.g., portal/PowerShell not supported for linuxFxVersion), and suggest alternative workflows.
  • Consider adding bash script examples for Linux users where PowerShell scripts are provided for Windows.
  • Ensure that Linux-specific terminology and steps are as detailed and accessible as Windows/PowerShell equivalents.
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: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is focused on creating SMB volumes for Azure NetApp Files, which is a protocol supported by both Windows and Linux clients. However, the instructions and examples for managing and controlling access to SMB volumes are exclusively Windows-centric. Only Windows tools (MMC, Windows File Browser, Control Panel) are mentioned for setting permissions and managing shares, with no guidance for Linux or macOS users. The documentation does not provide Linux-based examples for mounting SMB volumes or managing permissions, nor does it mention Linux SMB clients or tools such as smbclient, mount.cifs, or setfacl.
Recommendations
  • Add instructions or references for managing SMB share and NTFS permissions from Linux/macOS clients, such as using smbclient, mount.cifs, or setfacl.
  • Include examples for mounting SMB volumes on Linux and macOS, or link to relevant documentation.
  • Mention cross-platform SMB client compatibility and any caveats for non-Windows environments.
  • Clarify which management tasks require Windows tools and which can be performed from Linux/macOS.
GitHub Create Pull Request
Azure Netapp Files SMB performance best practices for Azure NetApp Files ...ure-netapp-files/azure-netapp-files-smb-performance.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 is heavily Windows-focused: all examples, commands, and monitoring instructions use Windows tools (PowerShell cmdlets, netstat, perfmon). There are no Linux/macOS client examples or equivalent instructions, despite SMB being a cross-platform protocol. Linux tools and configuration steps are not mentioned, and all performance testing and monitoring guidance assumes a Windows environment.
Recommendations
  • Add equivalent Linux/macOS client examples for mounting SMB shares, verifying SMB Multichannel, and measuring performance (e.g., using smbclient, mount.cifs, or relevant Linux tools).
  • Include Linux-specific commands for checking RSS/network interface capabilities (e.g., ethtool, lshw, or ip commands).
  • Provide guidance for monitoring SMB performance on Linux (e.g., using iostat, nload, or atop).
  • Clarify which recommendations are Windows-specific and add Linux/macOS sections where appropriate.
  • If Azure NetApp Files SMB support is intended for Windows clients only, explicitly state this in the documentation.
GitHub Create Pull Request
Azure Netapp Files Create volume replication for Azure NetApp Files ...etapp-files/cross-region-replication-create-peering.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page provides feature registration and status check examples using Azure PowerShell first and in detail, with only a brief mention of Azure CLI alternatives. This prioritizes Windows/PowerShell usage, which may create friction for Linux/macOS users who typically use Azure CLI. No Linux/macOS-specific examples or screenshots are provided, and the workflow is described primarily through Azure Portal UI and PowerShell commands.
Recommendations
  • Provide full Azure CLI command examples for feature registration and status checks, not just links.
  • Include CLI command syntax side-by-side with PowerShell examples where applicable.
  • Add notes or screenshots showing the Azure Portal UI on non-Windows platforms if there are differences.
  • Clarify that all steps can be performed using Azure CLI or Portal on any OS, and link to relevant CLI documentation.
  • Consider listing CLI examples before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Azure Netapp Files Create a capacity pool for Elastic zone-redundant service in Azure NetApp Files ...icles/azure-netapp-files/elastic-capacity-pool-task.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation mentions PowerShell usage and provides update instructions for the Az.NetAppFiles PowerShell module before mentioning Azure CLI or REST API alternatives. PowerShell is a Windows-centric tool, and its explicit update instructions are given, while equivalent Linux/macOS CLI instructions are not. No Linux/macOS-specific examples or parity guidance are provided.
Recommendations
  • Provide Azure CLI update instructions alongside PowerShell, especially since Azure CLI is cross-platform.
  • Include explicit examples or references for Linux/macOS users where PowerShell is mentioned.
  • Clarify that PowerShell instructions are for Windows users and offer CLI or REST API alternatives for Linux/macOS users.
  • Consider listing Azure CLI before PowerShell in prerequisites to avoid Windows-first ordering.
GitHub Create Pull Request
Azure Relay Authenticate with managed identities for Azure Relay resources .../articles/azure-relay/authenticate-managed-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by providing step-by-step instructions and examples exclusively for Windows VMs. It references Windows VM creation, Windows-specific connection methods (RDP), and does not include equivalent instructions or examples for Linux VMs or macOS environments. While code samples are cross-platform (.NET, Java, JavaScript), the walkthrough for enabling managed identity and running the sample app is Windows-only.
Recommendations
  • Add parallel instructions for creating and configuring a Linux VM with managed identity.
  • Include guidance for connecting to Linux VMs (e.g., SSH) and copying files.
  • Provide sample commands for building and running the sample app on Linux/macOS.
  • Clarify that the sample apps are cross-platform and can be run on non-Windows environments.
  • Reference documentation for enabling managed identity on Linux VMs.
GitHub Create Pull Request
Azure Relay Authenticate from an application - Azure Relay .../main/articles/azure-relay/authenticate-application.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 primarily demonstrates authentication with Azure Relay using .NET console application samples, which are most commonly run on Windows. The highlighted code and walkthrough focus on .NET/C#, with no explicit mention of Linux/macOS compatibility or instructions for running the sample on those platforms. While Java and JavaScript samples are linked, the main example and step-by-step guidance center on .NET. Additionally, PowerShell is mentioned first in the 'Next steps' section for role assignment, before CLI or REST API alternatives.
Recommendations
  • Explicitly mention that the .NET sample can be run on Linux/macOS using .NET Core/.NET 5+.
  • Provide example commands or instructions for running the sample on Linux/macOS (e.g., using 'dotnet run' on Ubuntu).
  • Include a Linux/macOS terminal screenshot or walkthrough alongside the Windows example.
  • List Azure CLI instructions before or alongside PowerShell for role assignment, or clarify parity.
  • Highlight Java and JavaScript samples in the main body, not just in the 'Samples' section, and note their cross-platform nature.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is focused on creating a .NET Framework console application using Visual Studio, which is a Windows-centric development environment and technology. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ (cross-platform) or alternative IDEs like VS Code. The NuGet package installation steps are specific to Visual Studio's GUI, with no mention of command-line alternatives suitable for Linux/macOS.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/.NET 5+) console application using the 'dotnet' CLI.
  • Include NuGet package installation steps using the 'dotnet add package' command.
  • Mention alternative IDEs such as Visual Studio Code or JetBrains Rider, which are available on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay package and sample code are compatible with .NET Core/.NET 5+ on Linux/macOS.
  • Provide example commands and code snippets that work on Linux/macOS.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md ...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows-centric. Instructions for creating the console app and installing NuGet packages are given only for Visual Studio on Windows, with no mention of cross-platform alternatives like .NET Core/.NET 5+ or command-line tooling usable on Linux/macOS. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Add instructions for creating a cross-platform .NET console application using .NET Core/.NET 5+ (e.g., 'dotnet new console').
  • Include guidance for installing NuGet packages via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify whether the Microsoft.Azure.Relay SDK and sample code work on Linux/macOS, and provide any necessary platform-specific notes.
  • Present both Visual Studio (Windows) and VS Code/CLI (cross-platform) workflows, or at least mention alternatives.
  • Consider showing code examples that target .NET Standard or .NET 5+ for broader OS compatibility.
GitHub Create Pull Request
Azure Relay https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md ...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation instructs users to create a Console App (.NET Framework) project in Visual Studio and uses Visual Studio's GUI for NuGet package management. These are Windows-centric tools and workflows. There is no mention of cross-platform alternatives (e.g., .NET Core/.NET 5+, CLI commands, VS Code, or Linux/macOS development environments). The code itself is C# and could be cross-platform if targeting .NET Core/.NET 5+, but the instructions are Windows-first and omit Linux/macOS guidance.
Recommendations
  • Add instructions for creating a cross-platform .NET Core or .NET 5+ console application using the dotnet CLI, which works on Linux and macOS.
  • Include NuGet package installation steps using the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') for non-Windows environments.
  • Mention alternative development environments such as VS Code or JetBrains Rider that are available on Linux/macOS.
  • Clarify whether the Microsoft.Azure.Relay SDK and Hybrid Connections are supported on non-Windows platforms, and provide any necessary platform-specific notes.
GitHub Create Pull Request
API Center Import APIs from Azure API Management - Azure API Center ...main/articles/api-center/import-api-management-apis.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides Azure CLI examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown after bash examples. There is no evidence of exclusive use of Windows tools, PowerShell-heavy bias, or missing Linux/macOS examples. The page is cross-platform in its approach, but bash examples are always shown first, which is a minor 'windows_first' bias (since PowerShell is primarily used on Windows, but also available on other platforms).
Recommendations
  • Consider alternating the order of bash and PowerShell examples, or explicitly state that both shells are supported equally.
  • Add a note clarifying that all examples work on Linux, macOS, and Windows, as long as Azure CLI is installed.
  • If possible, include a table or toggle to switch between bash and PowerShell examples for improved parity and user experience.
GitHub Create Pull Request
API Center Include file .../includes/configure-managed-identity-kv-secret-user.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are included for every step and are shown immediately after Bash. This creates a slight Windows-first impression and emphasizes PowerShell usage, which is primarily relevant for Windows users.
Recommendations
  • Clearly label Bash and PowerShell examples as 'Linux/macOS (Bash)' and 'Windows (PowerShell)' to help users identify which to use.
  • Consider showing Bash examples first, as Bash is the default shell on Linux/macOS and is also available on Windows via WSL.
  • Add a brief note explaining that Bash examples are suitable for Linux/macOS and Windows users using WSL, while PowerShell examples are for native Windows environments.
  • Ensure variable naming and usage is consistent between examples to reduce confusion.
GitHub Create Pull Request
API Center Include file ...ter/includes/configure-managed-identity-apim-reader.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell versions are shown immediately after Bash for each step, which may suggest a slight Windows-first bias. There is no mention of Linux-specific tools or workflows, but the Bash examples ensure Linux/macOS users are supported. The presence of PowerShell examples is helpful for Windows users but could be perceived as unnecessary duplication if not balanced with Linux/macOS context.
Recommendations
  • Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with a short note at the top of the CLI section.
  • If possible, use tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make it clear which environment each example targets.
  • Consider listing Bash examples first, as Azure CLI is cross-platform and Bash is the default shell on many systems.
  • Add a note that Azure CLI commands work in Bash on Windows (e.g., via WSL) to further support cross-platform users.
GitHub Create Pull Request
API Management Deploy an Azure API Management Instance to Multiple Azure Regions ...management/api-management-howto-deploy-multi-region.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides Azure CLI and Azure PowerShell examples for managing multi-region deployments of Azure API Management, but it mentions the PowerShell cmdlet ('set-azapimanagement') before the Azure CLI command ('az apim update') when describing how to disable routing to a regional gateway. Additionally, the reference to 'other Azure tools' is vague and does not specify Linux/macOS-compatible alternatives. There are no explicit Linux/macOS examples or notes about cross-platform usage, and screenshots and instructions are focused on the Azure Portal UI, which is cross-platform but does not address CLI parity.
Recommendations
  • List Azure CLI commands before PowerShell commands, as Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI is available on Linux/macOS and provide installation links or references.
  • Provide Bash shell script examples where appropriate, especially for automation tasks.
  • Clarify 'other Azure tools' to include REST API usage and cross-platform SDKs.
  • Add a note that all Azure CLI commands work on Linux, macOS, and Windows.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally provides cross-platform guidance, especially for certificate creation and management, with clear OpenSSL (Linux/macOS) and Azure CLI examples. However, there are several instances where Windows tools (IIS, Certreq.exe, PowerShell) are mentioned as primary or alternative methods, sometimes before Linux equivalents. In automation and permission assignment sections, both Azure CLI and PowerShell are shown, but PowerShell is given a dedicated section. The export instructions for certificates reference IIS and Certreq.exe for Windows users, while OpenSSL is used for Linux/macOS. The FAQ and automation sections also provide both Azure CLI and PowerShell links, but PowerShell is sometimes listed first.
Recommendations
  • Ensure that Linux/macOS tools (like OpenSSL) are always mentioned alongside Windows tools (IIS, Certreq.exe) and not as an afterthought.
  • When listing automation or scripting options, alternate the order between Azure CLI and PowerShell, or group them together as 'cross-platform options' rather than defaulting to PowerShell/Windows-first.
  • Where possible, provide explicit Linux/macOS GUI or workflow equivalents if Windows GUI tools (like IIS) are referenced.
  • Clarify in each section that both Windows and Linux/macOS users are supported, and highlight any OS-specific limitations up front.
  • If a Windows tool is referenced (e.g., IIS, Certreq.exe), provide a direct Linux/macOS alternative in the same context, not just as a secondary note.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides installation instructions for Helm on both Windows and Linux, but the Windows example (using PowerShell and winget) is presented first, followed by the Linux example. The Windows installation method is highlighted before Linux, which may subtly prioritize Windows users. However, the majority of commands throughout the guide use Azure CLI and Bash syntax, which are cross-platform and suitable for both Linux and Windows environments. There are no sections that are Windows-only or that omit Linux equivalents.
Recommendations
  • Present Linux and Windows installation instructions for Helm in parallel tabs or sections, or alternate which OS is shown first to avoid implicit prioritization.
  • Explicitly state that all Azure CLI and Helm commands can be run on Linux, macOS, and Windows (with Bash or PowerShell as appropriate).
  • Consider adding a macOS-specific Helm installation example for completeness.
  • Clarify that Azure Cloud Shell is cross-platform and available to all users, reducing OS-specific friction.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis with Azure Private Link ...n/articles/azure-cache-for-redis/cache-private-link.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 PowerShell and Azure CLI examples for managing private endpoints with Azure Cache for Redis. However, PowerShell examples are presented first and in more detail, which may suggest a Windows-first approach. The Azure portal instructions are platform-neutral, but command-line automation favors Windows tools before Linux/macOS equivalents.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or alternate their order to avoid implicit prioritization.
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
  • Consider adding Bash or shell script snippets for DNS verification (e.g., using 'dig' or 'nslookup') to demonstrate parity for Linux/macOS users.
  • Where possible, clarify which tools are platform-specific and which are cross-platform.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are several areas where Windows-specific tools, commands, or patterns are mentioned first or exclusively. Windows is often listed before Linux in configuration instructions, and PowerShell/Azure CLI examples sometimes default to Windows syntax or omit explicit Linux/Bash alternatives. Some deployment and configuration steps reference Windows-specific concepts or tools before their Linux equivalents, and a few sections (e.g., ReadyToRun, checking 32/64-bit status) provide more detailed instructions for Windows than Linux.
Recommendations
  • When listing platform-specific instructions (e.g., configuration, deployment, debugging), alternate the order or present Linux/macOS first in some sections.
  • For every Azure CLI or PowerShell example, ensure both Windows (PowerShell/CMD) and Linux (Bash) command syntax are provided, using tabs or clear headings.
  • Where possible, provide parity in depth of explanation for both Windows and Linux (e.g., ReadyToRun, 32/64-bit checks, debugging).
  • Avoid phrases like 'On Windows, do X' without immediately following with 'On Linux, do Y' when both are supported.
  • Explicitly mention macOS where applicable, or clarify when instructions are identical for Linux/macOS.
  • Review all code and CLI snippets to ensure they are cross-platform or provide alternatives.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ 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 signs of Windows bias: some examples (e.g., AzureWebJobs_TypeScriptPath uses Windows-style paths), Windows-specific settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are called out, and PowerShell-specific settings are documented in detail. In a few places, Windows terminology or tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI), and Windows path conventions appear in examples before Linux alternatives.
Recommendations
  • Where path examples are given (e.g., AzureWebJobs_TypeScriptPath), provide both Windows and Linux formats, or clarify OS-specific usage.
  • When referencing tools for managing settings (Azure CLI, Azure PowerShell), mention Azure CLI first or equally with PowerShell, as CLI is cross-platform.
  • For settings that are OS-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION), clearly label them as Windows-only and, where possible, provide Linux alternatives or guidance.
  • Review examples and sample values to ensure Linux/macOS users see relevant formats and instructions.
  • Consider adding a summary table or section highlighting OS-specific settings for quick reference.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.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 presents deployment methods in a cross-platform manner, but there is a subtle Windows bias. Windows tools (Visual Studio, Kudu) and Windows-specific deployment scenarios are often mentioned first or in more detail. Visual Studio (a Windows-centric tool) is frequently listed before Visual Studio Code or CLI tools. Some explanations and examples (e.g., remote build, deployment slots) focus on Windows behaviors or tools before Linux equivalents, and the use of Kudu/scm is described in more detail for Windows. However, Linux deployment methods are covered, and Linux-specific scenarios (like Docker, remote build on Linux) are included.
Recommendations
  • When listing deployment tools, consistently mention cross-platform tools (Azure CLI, Core Tools, Visual Studio Code) before Windows-only tools (Visual Studio).
  • Provide equal detail for Linux and Windows deployment scenarios, especially in sections like remote build and deployment slots.
  • Explicitly call out when a tool or method is cross-platform versus Windows-only, to help Linux/macOS users identify their options quickly.
  • Where possible, include Linux/macOS command-line examples alongside or before Windows/PowerShell examples.
  • Clarify any differences in deployment experience or limitations for Linux users in each relevant section.
GitHub Create Pull Request
Azure Functions Develop and run Azure Functions locally ...in/articles/azure-functions/functions-develop-local.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides cross-platform guidance for developing Azure Functions locally, but there is a mild Windows bias. Visual Studio (Windows-only) is listed first in C# environments, and Windows-specific tools (Visual Studio, PowerShell) are mentioned before their Linux/macOS equivalents. However, Linux/macOS support is clearly indicated for most environments, and alternative tools are provided.
Recommendations
  • List cross-platform tools (e.g., Visual Studio Code, command-line/terminal) before Windows-only tools in environment tables and sections.
  • Explicitly mention Linux/macOS alternatives or parity wherever Windows tools are referenced (e.g., for HTTP testing, debugging, and project setup).
  • Add more examples or links for Linux/macOS-specific workflows, such as using bash/zsh, or package managers (apt, brew, etc.) for installing dependencies.
  • Clarify in introductory sections that all major workflows are supported on Linux/macOS, not just Windows.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ linux_first ⚠️ linux_tools ⚠️ windows_equity ⚠️ no_missing_linux_example
Summary
This documentation demonstrates a strong commitment to cross-platform parity, with a slight Linux-first bias. Linux migration is prioritized, and the most automated migration tooling (az functionapp flex-migration) is currently Linux-only and called out as such. Both Linux and Windows migration paths are clearly documented, with equivalent Azure CLI and portal steps for each. There are no sections where only Windows or PowerShell examples are given, nor are Windows tools or patterns mentioned before Linux equivalents. In fact, Linux is often presented first, and Linux-specific automation is highlighted. There are no missing Linux examples; if anything, Windows users have to perform more manual steps due to current tooling limitations.
Recommendations
  • Continue to maintain parity by updating the documentation if/when az functionapp flex-migration or similar automation becomes available for Windows.
  • Consider clarifying in the introduction that Linux migration is prioritized due to current platform support, to set expectations for Windows users.
  • If possible, provide more automation or scripting for Windows users to reduce manual migration friction.
  • Monitor for any future Linux-only features and ensure Windows users are provided with clear alternatives or workarounds.
GitHub Create Pull Request
Azure Netapp Files Configure customer-managed keys for Azure NetApp Files volume encryption .../azure-netapp-files/configure-customer-managed-keys.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 Azure PowerShell examples for configuring customer-managed keys for Azure NetApp Files. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as the tabbed instructions), PowerShell is presented before or alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell. There are no Linux/macOS-specific shell examples (e.g., Bash), but the CLI examples are cross-platform. No Windows-only tools or patterns are mentioned, and the instructions are generally platform-neutral outside of the PowerShell sections.
Recommendations
  • Ensure Azure CLI examples are presented first in tabbed sections, as CLI is cross-platform and more widely used outside Windows.
  • Clearly indicate that PowerShell is optional and primarily for Windows users.
  • Consider adding Bash script snippets for common tasks, especially where CLI commands are used in pipelines or with environment variables.
  • Add a brief note clarifying that all CLI examples work on Linux/macOS and Windows, while PowerShell is Windows-centric.
GitHub Create Pull Request
Azure Netapp Files Troubleshoot volume errors for Azure NetApp Files ...in/articles/azure-netapp-files/troubleshoot-volumes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation covers troubleshooting for Azure NetApp Files volumes across SMB, NFS, and dual-protocol scenarios. While it is not Windows-only, there is a mild Windows bias: in sections involving Kerberos and NFSv4.1, PowerShell commands (Set-ADComputer) are provided for configuring Kerberos encryption types, but equivalent Linux/UNIX LDAP/NFS administrative commands are not shown. Additionally, Active Directory (AD DS) and Microsoft Entra Domain Services are discussed before any mention of Linux-based directory services or alternatives, and some troubleshooting steps reference Windows tools (Active Directory Users and Computers) without Linux equivalents.
Recommendations
  • Provide Linux/UNIX command-line equivalents for AD/LDAP operations where PowerShell or Windows UI steps are shown (e.g., using ldapmodify, samba-tool, or relevant utilities).
  • Include troubleshooting steps for common Linux-based directory services (such as OpenLDAP or Samba AD) where applicable, or clarify that only Microsoft AD DS is supported.
  • When referencing tools like 'Active Directory Users and Computers', mention Linux alternatives or note that these steps require access to a Windows system.
  • Where PowerShell commands are shown, add equivalent steps for Linux administrators (e.g., using Kerberos or LDAP tools).
  • Ensure that examples for mounting, troubleshooting, and configuring NFS/LDAP include both Windows and Linux client perspectives.
GitHub Create Pull Request