← Back to Dashboard
256
Pages Scanned
66
Pages Flagged
256
Changed Pages
25.8%
% Pages Flagged

Scan Information

Started At: 2026-01-27 00:00:09

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

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 256

Files Completed: 256

Problematic Pages

66 issues found
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
High 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+ or cross-platform editors like VS Code. The NuGet package installation steps are also tailored to Visual Studio, omitting command-line alternatives suitable for Linux/macOS.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application, which is cross-platform and supported on Linux/macOS.
  • Include examples for using VS Code or command-line tools (dotnet CLI) to create and manage projects and NuGet packages.
  • Clarify whether the Microsoft.Azure.Relay package and sample code are compatible with .NET Core/.NET 5+ and non-Windows platforms.
  • Provide parity in code samples and setup steps for Linux/macOS users.
GitHub Create Pull Request
Azure Relay Tutorial: REST tutorial using Azure Relay ...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High 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 tutorial is heavily focused on Windows development tools and patterns, specifically Visual Studio, .NET Framework, and WCF, all of which are traditionally Windows-centric. All examples and instructions assume the use of Visual Studio on Windows, with no mention of Linux/macOS alternatives or cross-platform approaches. There are no instructions or code samples for Linux/macOS users, nor guidance on running the sample outside Windows environments.
Recommendations
  • Clarify early in the tutorial that WCF and .NET Framework are primarily Windows technologies, and note any cross-platform limitations.
  • If possible, provide guidance or references for running similar Azure Relay REST services using .NET Core/.NET 5+ (which are cross-platform) or other languages/frameworks that work on Linux/macOS.
  • Offer alternative instructions for Linux/macOS users, such as using VS Code, the .NET CLI, or Mono where feasible.
  • Explicitly state any Windows-only requirements, and suggest equivalent Linux/macOS workflows if available.
  • Include a note about the lack of Linux/macOS support if the tutorial cannot be completed on those platforms.
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, referencing Windows PowerShell modules, cmdlets, and patterns throughout. All code examples are in PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of PSCredential and related cmdlets are Windows-centric, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
  • Add Azure CLI examples for credential management and authentication workflows.
  • Clarify which steps are cross-platform and which are Windows-specific.
  • Provide Bash or Python runbook examples for managing Azure resources.
  • Document any limitations or differences for Linux/macOS users in Azure Automation.
  • Reference cross-platform modules or SDKs (e.g., Microsoft Graph SDK for Python, Azure CLI) where applicable.
GitHub Create Pull Request
Azure Relay Azure Relay Hybrid Connections - WebSockets in .NET ...e-relay/relay-hybrid-connections-dotnet-get-started.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The tutorial assumes use of Visual Studio on Windows and does not mention or provide guidance for developing or running the .NET applications on Linux or macOS. All instructions and examples are tailored to Windows users, with no mention of cross-platform .NET development tools or alternatives.
Recommendations
  • Add instructions for using cross-platform .NET SDK (dotnet CLI) to create, build, and run the sample applications.
  • Mention and provide examples for using VS Code or other cross-platform editors.
  • Clarify that .NET Core/.NET 5+ can run on Linux and macOS, and provide steps for those platforms.
  • Include terminal commands for Linux/macOS users to build and run the applications.
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 covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a noticeable Windows-first bias: Windows paths and conventions are often mentioned before Linux equivalents, some examples and explanations use Windows-centric tools (such as msbuild, Web Deploy/MSDeploy, IIS, and Windows file paths), and certain environment variables are described primarily in the context of Windows apps. Linux-specific details are present, especially for container scenarios and Oryx build automation, but Windows terminology and examples tend to dominate or appear first. Some settings lack Linux-specific usage examples or clarifications, and references to Windows tools (like msbuild, Web Deploy, applicationHost.config) are not always balanced with Linux alternatives.
Recommendations
  • Where environment variables or settings apply to both Windows and Linux, present Linux examples and paths alongside Windows ones, or alternate which is shown first.
  • Add Linux-specific usage examples for settings currently described only in Windows terms (e.g., msbuild, Web Deploy, applicationHost.config).
  • Clarify which settings are Windows-only, Linux-only, or cross-platform in all tables and explanations.
  • For build automation, provide more detail and parity for Oryx (Linux) configuration, matching the depth given to Kudu (Windows).
  • Where Windows tools are referenced, mention Linux alternatives or note their absence.
  • Ensure that environment variable descriptions include both Windows and Linux paths/formats where applicable.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based workflows, with all migration scripts, examples, and installation instructions provided exclusively for PowerShell. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The use of PowerShell Gallery and PowerShell modules is assumed throughout, and the documentation does not mention or provide alternatives for users on Linux or macOS, nor does it clarify cross-platform compatibility of the scripts.
Recommendations
  • Explicitly state whether the provided PowerShell scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions for those platforms.
  • Add equivalent Azure CLI (az) commands and workflows for key migration steps, or clarify if CLI-based migration is not supported.
  • Include Bash or shell script examples for common tasks (e.g., fetching resource IDs, uploading certificates) where possible.
  • Add a section addressing cross-platform usage, including any limitations or requirements for Linux/macOS users.
  • If migration is only supported via PowerShell, clearly state this limitation up front and provide guidance for Linux/macOS users on how to use PowerShell Core or Azure Cloud Shell.
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 are provided exclusively via Azure PowerShell commands, with no equivalent Azure CLI (cross-platform) or Bash examples. The main tutorial link also points to a PowerShell-based walkthrough, and there is no mention of Linux/macOS-specific instructions or parity for these operations. This creates friction for users on Linux/macOS who may prefer or require Azure CLI or Bash scripts.
Recommendations
  • Provide Azure CLI and Bash equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
  • Ensure tutorial links include both PowerShell and Azure CLI/Bash options, or clarify which platforms are supported.
  • Add notes or sections explicitly addressing cross-platform usage, highlighting any differences or limitations.
  • Where PowerShell is referenced, clarify if Azure CLI can be used for the same tasks and link to relevant documentation.
GitHub Create Pull Request
API Management Deploy an Azure API Management Instance to Multiple Azure Regions ...management/api-management-howto-deploy-multi-region.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides command-line examples for managing API Management regional gateways using Azure CLI and Azure PowerShell, but does not mention or provide examples for Linux/macOS-specific tools or workflows. PowerShell is referenced as a primary management tool alongside Azure CLI, and Windows-centric terminology (such as 'cmdlet') is used. No Linux shell (bash) or cross-platform scripting examples are given, and Windows tools are mentioned before their Linux equivalents (if any).
Recommendations
  • Include explicit bash examples for Azure CLI commands, demonstrating usage on Linux/macOS terminals.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide installation links for these platforms.
  • When referencing PowerShell, specify that Azure PowerShell is available cross-platform, or provide equivalent bash/CLI commands where possible.
  • Avoid using Windows-centric terminology (such as 'cmdlet') without noting cross-platform alternatives.
  • Add a note or section highlighting Linux/macOS workflows for managing API Management instances, especially for tasks currently only shown with PowerShell.
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 provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, but does not mention or link to equivalent instructions for Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS. The only explicit tooling example is Windows-centric (PowerShell).
Recommendations
  • Add links or sections for creating autoscaling, zone-redundant Application Gateways using Azure CLI, ARM templates, or Bicep.
  • Ensure that examples and tutorials are provided for both Windows (PowerShell) and cross-platform tools (CLI, templates).
  • Where possible, present cross-platform options before or alongside Windows-specific ones.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no CLI (az) or Bash examples provided, nor are Linux/macOS-friendly migration instructions mentioned. The migration tooling and guidance appear to assume a Windows/PowerShell environment, which may create friction for Linux/macOS users.
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 for common migration tasks.
  • Clarify whether the PowerShell scripts can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide installation/setup instructions for non-Windows users.
  • Explicitly mention Linux/macOS support or alternatives in migration guidance sections.
  • Consider linking to or creating migration guides tailored for Linux/macOS environments.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The tutorial is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate). There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and certificate creation relies on Windows-only PowerShell modules. This creates friction for Linux/macOS users, who must find their own workarounds for several steps.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and how to export to PFX format.
  • Add notes or links to cross-platform tools for certificate management.
  • Indicate which steps are Windows-specific and offer alternatives where possible.
  • Consider reordering examples so that cross-platform solutions are presented first or alongside Windows/PowerShell options.
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 for asset migration, with no mention of Bash, Python, or other Linux-native scripting alternatives. All migration examples and instructions are PowerShell-based, and tabs/defaults reference Windows first. While the Automation service itself is cross-platform, Linux users may encounter friction due to the lack of Linux-centric guidance.
Recommendations
  • Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI to support Linux/macOS users.
  • Explicitly state PowerShell Core (cross-platform) compatibility and provide instructions for running scripts on Linux/macOS, if supported.
  • Include tabs or sections with Linux-first examples, or clarify any platform limitations for the provided scripts.
  • Reference Azure CLI or REST API alternatives for asset migration, if available.
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 ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently throughout the page. Key backup and retention operations reference Windows PowerShell cmdlets without Linux CLI or REST API equivalents, and Windows registry settings are linked before Linux OpenSSL guidance. Linux examples are present for TLS, but parity is lacking for backup/export and resource management tasks.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) or REST API examples for resource management and backup/export tasks currently described only with PowerShell cmdlets.
  • Ensure Linux instructions are presented alongside or before Windows instructions in tables and step-by-step guides.
  • Reference Linux tools (such as Bash scripts, az CLI, or Python) for operations like exporting runbooks, DSC configurations, and managing resources.
  • Clarify which cmdlets or procedures are Windows-only, and offer alternative guidance for Linux/macOS users where possible.
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_tools ⚠️ windows_first
Summary
The documentation page for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and workflows, with most examples and instructions using PowerShell. The guidance for creating certificates via the portal recommends PowerShell as a workaround for CSP accounts, and all advanced examples (including Resource Manager template deployment) use PowerShell. There is minimal mention of Linux/macOS workflows, and no CLI (az), Bash, or cross-platform scripting examples. The Python section is present, but only for retrieving certificates in runbooks, not for management operations like creation or deletion.
Recommendations
  • Add Azure CLI (az) examples for certificate management tasks, such as creating, retrieving, and deleting certificates.
  • Include Bash or cross-platform scripting examples where possible, especially for certificate upload and management.
  • Clarify which operations can be performed from Linux/macOS environments and provide guidance or alternatives for those that are PowerShell-only.
  • If PowerShell is required for certain tasks, explicitly state platform requirements and suggest PowerShell Core (pwsh) usage on Linux/macOS.
  • Expand Python examples to include certificate management (creation, deletion) if supported via SDKs or REST API.
  • Add a section or table comparing management options across platforms (Windows, Linux, macOS).
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation generally describes Azure Change Tracking and Inventory as supporting both Windows and Linux, and mentions features applicable to both (such as file and daemon/service monitoring). However, the 'Track registry keys' section is exclusively focused on Windows registry keys, listing only Windows-specific examples and explanations, with no mention of Linux equivalents (such as configuration files or system settings). Additionally, Windows terminology and features (e.g., registry, Internet Explorer, explorer.exe) are presented in detail, while Linux-specific configuration tracking is not covered or exemplified.
Recommendations
  • Add examples of Linux-specific configuration tracking, such as monitoring changes to important configuration files (/etc/passwd, /etc/ssh/sshd_config, etc.), systemd unit files, or other relevant Linux system settings.
  • Include a table or section similar to the registry key list, but for commonly tracked Linux files or directories.
  • Clarify in the 'Track registry keys' section that this feature is Windows-only, and provide guidance or links for Linux users on what types of configuration changes can be tracked.
  • Ensure that examples and screenshots are balanced between Windows and Linux, or explicitly state when a feature is Windows-only.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tools and patterns. Most examples, code snippets, and instructions use PowerShell, PowerShell Workflow, and Windows-specific cmdlets. SDK and REST API sections are platform-neutral, but all CLI-based examples use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS workflows. The Python runbook section is brief and lacks parity in example depth. There are no Linux/macOS-specific instructions or examples for starting runbooks or passing parameters.
Recommendations
  • Add equivalent examples using Azure CLI (az automation runbook start ...) for Linux/macOS users.
  • Include Bash shell examples for passing parameters to runbooks, especially for JSON input.
  • Clarify which instructions are platform-agnostic (e.g., REST API, SDK) and which are Windows/PowerShell-specific.
  • Expand the Python runbook section to include more detailed parameter passing and invocation examples.
  • Add notes or links to cross-platform tooling for Azure Automation (e.g., az CLI, Bash, Python SDK).
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 page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples use PowerShell cmdlets, and the creation of credential assets is described only via the Azure portal or Windows PowerShell. There is no mention of Bash, Linux shell, or cross-platform CLI alternatives for credential management. PowerShell examples are presented before Python, and no Linux/macOS-specific guidance is provided for credential asset creation or retrieval outside of Python runbooks.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported, to provide parity for Linux/macOS users.
  • Clarify whether credential asset creation and management can be performed via REST API or SDKs, and provide examples.
  • Explicitly state any platform limitations (e.g., if PowerShell is required for certain operations) to set expectations for non-Windows users.
  • If PowerShell Core (pwsh) is supported cross-platform, mention it and provide usage guidance for Linux/macOS.
  • Consider including a section or note on how Linux/macOS users can interact with Azure Automation credentials outside of Python runbooks.
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
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 detailed Azure portal instructions (which are cross-platform via browser), but when it comes to scripting, it presents full PowerShell examples before Azure CLI equivalents. PowerShell is Windows-centric, while Azure CLI is cross-platform. There are no Linux/macOS-specific examples or notes, and the FAQ and troubleshooting sections reference commands (e.g., nslookup) that are available on both platforms but do not clarify Linux/macOS usage. There are no explicit Linux/macOS instructions or screenshots.
Recommendations
  • Present Azure CLI examples before PowerShell, or side-by-side, to emphasize cross-platform support.
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
  • Include Linux/macOS screenshots or terminal examples where appropriate (e.g., for DNS verification).
  • Add troubleshooting steps or verification commands (such as nslookup) with sample outputs from both Windows and Linux/macOS terminals.
  • Mention that all portal steps are OS-agnostic, but scripting options may differ by platform.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ linux_first ⚠️ linux_tools ⚠️ missing_windows_automation
Summary
The documentation demonstrates a Linux-first bias: Linux migration is automated via dedicated Azure CLI commands (az functionapp flex-migration), while Windows users must perform a manual, multi-step migration. Linux instructions and tooling are presented before Windows equivalents, and Linux users benefit from a streamlined process not available for Windows. There is no evidence of Windows bias; instead, Linux users are prioritized and provided with more advanced tooling.
Recommendations
  • Develop and release equivalent automated migration tooling (such as az functionapp flex-migration) for Windows Consumption plan apps, or clarify if/when such tooling will be available.
  • Explicitly state in the introduction that Linux migration is currently more automated and that Windows users must follow manual steps.
  • Provide a summary table comparing Linux and Windows migration experiences to set expectations.
  • Continue to update the documentation as Windows automation features become available.
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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides Azure PowerShell examples first and in detail for feature registration, with only a brief mention of Azure CLI as an alternative. The step-by-step instructions and screenshots are focused on the Azure Portal UI, which is platform-agnostic, but the command-line guidance is Windows/PowerShell-centric and does not show Linux/macOS equivalents up front.
Recommendations
  • Provide explicit Azure CLI examples alongside Azure PowerShell for feature registration and status checking, with full command syntax and example output.
  • When referencing command-line steps, present both PowerShell and CLI options side-by-side, or clearly indicate which is cross-platform.
  • Consider listing Azure CLI (cross-platform) commands first, or equally, to avoid Windows-first impression.
  • Add notes or links for Linux/macOS users on how to install and use Azure CLI for these operations.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation generally presents deployment methods and examples in a cross-platform manner, but there is a subtle Windows bias: Windows-based deployment technologies (such as Kudu, source control, Local Git, FTPS) are mentioned as 'Windows-only' in the availability table, and Windows terminology/tools (Visual Studio, Kudu) are often listed before Linux equivalents. Some explanations (e.g., remote build) provide more detail for Windows scenarios first, and the use of Windows-centric tools is more prominent in example lists. Linux-specific instructions and caveats are present, but often appear after Windows details.
Recommendations
  • Ensure Linux and macOS deployment examples are presented alongside or before Windows examples, especially in sections describing tooling (e.g., CLI, Core Tools, VS Code).
  • Where deployment technologies are Windows-only, clarify alternatives for Linux users in the same section, rather than in later paragraphs.
  • Provide explicit Linux/macOS command-line examples (e.g., bash, zsh) where PowerShell or Windows tools are referenced.
  • Highlight Linux-specific behaviors and limitations earlier in each relevant section, not just in footnotes or after Windows details.
  • Add a summary table or quick-start guide for Linux/macOS users to identify supported deployment methods and tools.
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 from a .NET console application, with code samples and instructions focused on .NET/C#. The 'Run the sample' section only references running the .NET sample, with no explicit instructions for Linux/macOS users or for running Java/JavaScript samples. The 'Next steps' section lists Azure PowerShell before Azure CLI, which is more cross-platform. There is no mention of Linux/macOS-specific considerations, nor are there examples or guidance for running the sample on those platforms.
Recommendations
  • Add explicit instructions for running the Java and JavaScript samples, including prerequisites and platform-specific notes for Linux/macOS users.
  • Include guidance on installing .NET Core/SDK on Linux/macOS if users wish to run the .NET sample outside Windows.
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform.
  • Add a note clarifying that the authentication flow and SDKs are supported on Linux/macOS, and link to relevant platform setup guides.
  • Provide example commands or troubleshooting tips for Linux/macOS environments.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government using Azure CLI, REST API, and PowerShell. While the CLI section is platform-neutral, the PowerShell section is detailed and includes multiple connection types and commands, reflecting a strong emphasis on PowerShell (a Windows-centric tool). The PowerShell access section is more extensive than the CLI or REST API sections, and PowerShell is mentioned after CLI but before REST API, which may suggest a slight ordering bias toward Windows tools. There are no Linux/macOS-specific examples or parity notes, and no mention of Bash, shell scripting, or Linux-native tools.
Recommendations
  • Add explicit Bash or shell scripting examples for connecting to Azure Government, especially for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS terminal environments if any differences exist.
  • Balance the PowerShell section by providing equivalent instructions for Bash/Unix shell environments, or at least acknowledge that PowerShell is primarily a Windows tool.
  • Consider reordering sections to present platform-neutral tools (CLI, REST API) before platform-specific ones (PowerShell).
GitHub Create Pull Request
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation exclusively describes creating a .NET Framework console application using Visual Studio, a Windows-only IDE, and does not mention or provide instructions for Linux/macOS users (e.g., using .NET Core/.NET 5+ with VS Code or CLI). All steps and examples assume a Windows development environment.
Recommendations
  • Add instructions for creating a .NET Core or .NET 5+ console application using the dotnet CLI, which works cross-platform.
  • Include alternative steps for Linux/macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows where possible.
  • Explicitly state if the sample code is compatible with .NET Core/.NET 5+ and how to run it on non-Windows platforms.
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 exclusively providing step-by-step instructions for running the sample application on a Windows VM, including references to RDP and Windows-specific VM creation guides. There are no equivalent instructions or examples for running the sample on Linux VMs or other platforms, despite managed identities and Azure Relay supporting cross-platform development. While code samples are in .NET (which is cross-platform), the operational guidance is Windows-centric.
Recommendations
  • Add instructions for deploying and running the sample application on a Linux VM, including SSH access and relevant Linux commands.
  • Provide parity in guidance for enabling managed identity on Linux VMs, linking to Linux-specific Azure documentation.
  • Clarify that the .NET sample can run on Linux and macOS, and provide build/run steps for those platforms.
  • Include examples or references for Java and JavaScript samples, especially for Linux environments.
GitHub Create Pull Request
Azure Relay Configure IP firewall for Azure Relay namespace ...n/articles/azure-relay/ip-firewall-virtual-networks.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces using the Azure portal and Resource Manager templates. While the technical steps are platform-neutral, the only explicit deployment guidance for the template links to a PowerShell-based deployment page, which is typically Windows-first. There are no Linux/macOS CLI or automation examples, and no mention of cross-platform tools like Azure CLI or Bicep.
Recommendations
  • Add instructions or links for deploying Resource Manager templates using Azure CLI (az deployment), which is cross-platform.
  • Include examples or references for using Bicep, which is also platform-neutral.
  • Where possible, provide parity in deployment steps for Linux/macOS users, such as Bash or Azure CLI examples.
  • Clarify that PowerShell is not required and that other deployment methods are available.
GitHub Create Pull Request
Azure Relay Hybrid Connections - HTTP requests in .NET ...ay-hybrid-connections-http-requests-dotnet-get-started.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 Windows environments throughout, with all examples and instructions referencing Visual Studio for creating and running .NET console applications. There is no mention of cross-platform .NET development tools (such as VS Code, CLI, or Linux/macOS compatibility), nor are there instructions or examples for running the sample applications on Linux or macOS. This creates friction for users on non-Windows platforms, even though .NET Core/.NET 5+ is cross-platform.
Recommendations
  • Add instructions for creating and running the .NET applications using the .NET CLI, which works on Windows, Linux, and macOS.
  • Mention and provide examples for using Visual Studio Code or other cross-platform editors.
  • Clarify that the sample code works on .NET Core/.NET 5+ and is not Windows-only.
  • Include notes or steps for Linux/macOS users, such as terminal commands for building and running the applications.
  • Explicitly state any platform-specific requirements if present.
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 provides instructions for creating a .NET Framework console application using Visual Studio, a Windows-centric IDE, and references project types only available on Windows. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform development tools.
Recommendations
  • Add instructions for creating a cross-platform .NET (Core/.NET 5+) console application using the 'dotnet' CLI, which works on Windows, Linux, and macOS.
  • Include alternative steps for installing NuGet packages via CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
  • Clarify that the code sample works with .NET Core/.NET 5+ and provide guidance for using VS Code or other cross-platform editors.
  • Mention that Visual Studio is Windows-only and suggest alternatives for non-Windows users.
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 ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation exclusively references Visual Studio and .NET Framework, both of which are traditionally Windows-centric tools. There are no instructions or examples for creating the application using cross-platform tools (e.g., .NET Core/.NET 5+, VS Code, CLI) or on Linux/macOS environments. The workflow assumes a Windows development environment and omits Linux/macOS alternatives.
Recommendations
  • Add instructions for creating the project using the .NET CLI (dotnet new console) for .NET Core/.NET 5+.
  • Clarify whether the Microsoft.Azure.Relay package and sample code work on .NET Core/.NET 5+ and on Linux/macOS.
  • Provide examples for installing NuGet packages via CLI (dotnet add package) and for editing code in cross-platform editors like VS Code.
  • Explicitly mention platform compatibility and any limitations for Linux/macOS users.
  • If the sample is Windows-only due to .NET Framework, state this clearly at the top.
GitHub Create Pull Request
Azure Relay Integrate Azure Relay with Azure Private Link Service ...blob/main/articles/azure-relay/private-link-service.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 instructions for integrating Azure Relay with Azure Private Link Service, but command-line automation is only covered using Azure PowerShell, with no equivalent Azure CLI or Linux/macOS shell examples. The validation step explicitly references creating a Windows VM and does not mention Linux VM options or provide parity in testing instructions. The overall flow and screenshots are portal-based (cross-platform), but scripting and VM validation are Windows-centric.
Recommendations
  • Add Azure CLI examples alongside Azure PowerShell for creating and managing private endpoints, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • In the validation section, provide instructions for creating a Linux VM and running equivalent DNS validation commands (e.g., using nslookup or dig), or clarify that the steps apply equally to Linux/macOS VMs.
  • Where possible, avoid language or examples that imply Windows is the default or only supported platform unless a feature is genuinely Windows-only.
  • Consider including a note that all Azure portal steps are platform-agnostic and can be performed from any OS with a supported browser.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.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 for relocating Azure Firewall provides examples and instructions using the Azure Portal and Azure PowerShell, but does not include Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its usage may create friction for Linux/macOS users who typically use Azure CLI. Additionally, PowerShell instructions are presented as a primary alternative to the portal, with no parity for Linux-native tooling.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all template export, modification, and deployment steps.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent commands.
  • Ensure that all references to creating or modifying resources via scripts include both PowerShell and CLI options.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.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 provides several examples and command references using Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Azure CLI or Linux/macOS shell examples in those sections. In some cases, PowerShell commands are mentioned before CLI alternatives, and certain steps (such as retrieving images) only show PowerShell syntax. This creates friction for Linux/macOS users who typically use Azure CLI and Bash.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI command and/or Bash script.
  • When listing commands, present Azure CLI (cross-platform) examples first, followed by PowerShell alternatives.
  • Ensure all critical steps (such as retrieving images, associating AKS clusters, etc.) have CLI/Bash examples.
  • Clarify when a command is only available in PowerShell, and suggest workarounds for CLI users if needed.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Machine Scale Sets to another region ...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides instructions for relocating Azure Virtual Machine Scale Sets but consistently references the Azure portal and PowerShell/ARM templates without offering Linux/macOS-specific CLI examples. The use of screenshots and step-by-step instructions is focused on the Azure portal, which is platform-agnostic but often more familiar to Windows users. There is no mention of Linux shell commands or parity for Linux/macOS users in exporting templates or managing resources.
Recommendations
  • Add Azure CLI examples for key steps such as exporting templates, modifying resources, and deploying in the target region.
  • Include explicit instructions or links for performing tasks using Linux/macOS terminals, especially for Infrastructure as Code workflows.
  • Present PowerShell and CLI examples side-by-side where applicable, or clarify that all steps can be performed on any OS using the CLI.
  • Add notes or sections highlighting cross-platform compatibility for all major steps.
GitHub Create Pull Request
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.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 describes the Azure VM restore process in a generally OS-neutral way, but there is notable bias in the 'Restore an encrypted VM' scenario. This section exclusively references Windows-specific encryption guides and instructs users to use PowerShell to create the VM after restoring disks, without mentioning Linux equivalents or providing guidance for encrypted Linux VMs. Additionally, the restore examples and links for encrypted VMs are all Windows-centric, and PowerShell is presented as the default tool, which may create friction for Linux users.
Recommendations
  • Add explicit guidance for restoring encrypted Linux VMs, including links to relevant documentation and any required steps/tools.
  • Provide CLI (az CLI) or Bash examples alongside PowerShell instructions for VM creation after disk restore.
  • Clarify whether the encrypted VM restore scenario applies only to Windows VMs, or add a note about Linux support and differences.
  • Ensure parity in restore scenarios by mentioning Linux-specific considerations where relevant.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides general guidance for restoring Azure VMs using the Azure portal and covers both Windows and Linux VMs in principle. However, there is a noticeable Windows bias: examples and links for post-restore steps, network configuration, and special scenarios (such as restoring domain controllers, availability sets, and SQL VMs) almost exclusively reference Windows-specific tools, PowerShell, and Windows documentation. Linux-specific restore scenarios, troubleshooting, and examples are largely missing or referenced only briefly (e.g., cloud-init password reset). Windows links and examples are presented first or exclusively in many sections.
Recommendations
  • Add explicit Linux VM restore examples and walkthroughs, including restoring disks, creating VMs from restored disks, and handling common Linux-specific post-restore issues (e.g., SSH key management, cloud-init, SELinux, systemd services).
  • Provide links to Linux documentation for attaching disks, configuring network interfaces, and setting static IP addresses (e.g., using Azure CLI or the portal for Linux VMs).
  • Include troubleshooting steps for common Linux VM restore issues, such as boot failures, kernel/initramfs mismatches, and agent installation.
  • Balance references to PowerShell with Azure CLI or Bash examples, especially in sections about creating VMs from restored disks and configuring network settings.
  • Add guidance for restoring Linux VMs with special configurations (e.g., multiple NICs, custom images, encrypted disks) and clarify any differences from Windows VM restore flows.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation generally covers both Windows and Linux Azure VMs, including their respective disk encryption technologies (BitLocker for Windows, dm-crypt for Linux). However, there is a notable bias in example commands: the only explicit command-line example for identifying a VM's associated key vault uses PowerShell, with no equivalent Azure CLI or Bash example provided. Additionally, PowerShell is mentioned before Azure CLI in the section about setting access policies, and the documentation tends to reference Windows technologies first when describing ADE (BitLocker is mentioned before dm-crypt).
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples alongside PowerShell commands, especially for tasks like identifying a VM's associated key vault.
  • When listing technologies or steps that apply to both Windows and Linux, alternate the order or present them in parallel to avoid Windows-first bias.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
  • Where screenshots or UI references are platform-agnostic, clarify that the process is identical for both Windows and Linux VMs.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.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 provides comprehensive coverage for both Windows and Linux Azure VM backup scenarios, but there are several instances of Windows bias. Windows backup options (such as MARS agent and DPM/MABS) are described in greater detail and are supported for more features, while Linux support is often listed as 'not supported' for these agents. Restore instructions and examples frequently mention PowerShell and Windows-centric tools, with Linux equivalents rarely referenced. Windows scenarios and tools are often presented first, and some restore workflows (e.g., creating a new VM from disk) mention PowerShell without Linux CLI alternatives.
Recommendations
  • Where PowerShell is referenced for restore operations, add equivalent Azure CLI or Bash examples for Linux users.
  • Clarify in restore sections that the process applies equally to Linux VMs, and provide explicit Linux VM examples where possible.
  • In tables and lists, alternate the order of Windows and Linux examples, or group them together to avoid Windows-first presentation.
  • For agent-based backup options, clearly state Linux alternatives or workarounds (if any), and link to relevant Linux documentation.
  • Expand file-level restore documentation to include more Linux-specific scenarios and limitations, with troubleshooting tips.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively discusses the MARS agent (Windows-only), System Center Data Protection Manager (DPM), and Microsoft Azure Backup Server (MABS)—all Windows-based tools—for backing up on-premises machines. There is no mention of Linux backup agents, Linux-compatible backup workflows, or equivalent Linux tooling for on-premises backup. The examples and architectural diagrams focus on Windows Server and Windows VMs, with Linux support only referenced as 'not supported' for the MARS agent.
Recommendations
  • Explicitly clarify Linux support and limitations for on-premises backup scenarios, including a summary table of supported OSes for each backup method.
  • If Azure Backup does not support direct backup of on-premises Linux machines, provide links or guidance to alternative solutions (e.g., third-party backup tools, Azure File Sync, or Azure Blob Storage for Linux data).
  • Include a section or note on how Linux workloads in Azure (Linux VMs) are backed up, and whether the Azure VM backup extension is OS-agnostic.
  • Where possible, provide parity in examples and workflows for Linux and macOS users, or clearly state when features are Windows-only.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.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 covers both Windows and Linux encrypted Azure VMs, but there is a notable Windows bias in the restore process examples. The only explicit automation example for recreating a VM from restored disks is via PowerShell, with no CLI or Linux-native alternative shown. Additionally, the OS disk swap note links only to Windows instructions. The Linux-specific restore steps are brief and lack detailed guidance or command examples, making it harder for Linux users to follow parity workflows.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for restoring VMs from disks, not just PowerShell.
  • Include a link or section for swapping OS disks on Linux VMs, similar to the Windows link provided.
  • Expand the Linux restore section with step-by-step instructions and example commands for reinstalling the ADE extension and reconfiguring Key Vault integration.
  • When referencing automation or scripting, present cross-platform options (PowerShell, CLI, ARM templates) or clarify which are supported for Linux VMs.
GitHub Create Pull Request
Data Share Tutorial: Accept & receive data - Azure Data Share ...ob/main/articles/data-share/subscribe-to-data-share.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 step-by-step instructions for accepting and receiving data via Azure Data Share, with examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell examples and references are prominent and sometimes include Windows-centric paths (e.g., D:\testFiles). PowerShell is presented as a first-class option alongside CLI, but there are no explicit Linux/macOS shell (bash) examples for tasks like file uploads or storage management. The PowerShell examples assume familiarity with Windows file system conventions and do not mention Linux/macOS equivalents, which may cause friction for non-Windows users.
Recommendations
  • Add explicit bash (Linux/macOS) examples for file operations, such as uploading files to Azure Storage using az CLI or Azure Storage SDKs.
  • Replace or supplement Windows-style file paths (e.g., D:\testFiles) with Linux/macOS equivalents (e.g., /home/user/testFiles) in examples.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample shell commands for common tasks (e.g., creating containers, uploading files) using az CLI.
  • Where PowerShell is referenced, note that Azure PowerShell is available cross-platform, but provide guidance or links for Linux/macOS installation and usage.
  • Consider reordering examples so that cross-platform CLI instructions appear before PowerShell, or present both equally.
GitHub Create Pull Request
DNS Resolve Azure and on-premises domains. .../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed instructions and screenshots for configuring hybrid DNS using Azure DNS Private Resolver, but only demonstrates on-premises DNS configuration using a Windows DNS server. There are no examples or guidance for configuring conditional forwarders on Linux-based DNS servers (such as BIND), nor are Linux/macOS command-line examples shown for DNS testing. Windows/PowerShell quickstarts are mentioned before CLI alternatives.
Recommendations
  • Add a section or example showing how to configure conditional forwarders on a Linux DNS server (e.g., BIND), including sample configuration files.
  • Include Linux/macOS command-line examples (e.g., using dig or nslookup) for DNS query testing, alongside or instead of Windows screenshots.
  • When listing quickstarts, mention CLI and Linux-compatible options before or alongside PowerShell/Windows-specific ones.
  • Clarify that the procedures are applicable to both Windows and Linux environments, and provide parity in troubleshooting steps.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides equivalent instructions for Azure Portal, Azure CLI, and PowerShell. However, the PowerShell examples and guidance are prominent and include Windows-centric paths (e.g., D:\testFiles), and PowerShell is traditionally a Windows-first tool. The PowerShell tab is present alongside CLI, but examples such as file upload use Windows-style paths and do not mention Linux/macOS alternatives. There is no explicit Linux/macOS example for uploading files, and PowerShell requirements are referenced without clarifying cross-platform usage.
Recommendations
  • Add explicit notes that Azure PowerShell is cross-platform and can be used on Linux/macOS, or clarify when examples are Windows-specific.
  • For file upload examples, include both Windows and Linux/macOS path formats (e.g., D:\testFiles\textfile.csv and /home/user/testFiles/textfile.csv).
  • Where PowerShell is referenced, mention that Azure CLI is fully supported on Linux/macOS and provide parity in examples.
  • Consider reordering tabs so that Azure CLI (which is natively cross-platform) appears before PowerShell.
  • Add a brief section or callout confirming that all steps can be completed on Linux/macOS using Azure CLI or PowerShell Core.
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.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 demonstrates a moderate Windows bias. Windows/PowerShell examples (using psping.exe) are shown first and in more detail, with Linux equivalents (telnet) mentioned briefly and only for port checking, not for packet drops or latency. The recommended troubleshooting tools (psping.exe, tcpping.exe) are Windows-only, and there is no guidance or example for Linux/macOS users to perform equivalent packet drop or latency tests. This creates friction for non-Windows users attempting network troubleshooting.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands, such as using 'nc', 'nmap', or 'hping3' for port and packet tests.
  • Show Linux/macOS examples alongside Windows/PowerShell examples, not after or as an afterthought.
  • Mention cross-platform tools (e.g., Wireshark, curl) where possible.
  • Clarify which steps/tools are Windows-only and offer alternatives for other platforms.
  • Consider reordering examples so that Windows and Linux/macOS are presented equally.
GitHub Create Pull Request
Event Hubs Geo-disaster recovery - Azure Event Hubs| Microsoft Docs ...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.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 platform-specific instructions for manual failover using Azure portal, Azure CLI, Azure PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C#. No explicit Linux/macOS shell examples (e.g., Bash) are provided, and the ordering of examples tends to favor Windows tools first. There are screenshots of the Azure portal, which is platform-neutral, but no command-line examples for Linux/macOS users beyond Azure CLI.
Recommendations
  • Ensure Azure CLI examples are clearly marked as cross-platform and provide Bash shell usage examples where relevant.
  • List cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell) in example sections.
  • Add explicit notes or examples for Linux/macOS users, such as using Bash scripts or automation with Azure CLI.
  • Consider including sample automation scripts for Linux environments, especially for failover scenarios.
  • Clarify that PowerShell examples are primarily for Windows users and suggest alternatives for Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Bicep functions - resources ...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_tools
Summary
The documentation page is generally cross-platform and focused on Bicep language functions for Azure Resource Manager deployments. However, in the section describing how to discover resource types with list operations, it mentions the Windows PowerShell cmdlet (Get-AzProviderOperation) before the Azure CLI equivalent, and provides a PowerShell example first. This is a minor instance of Windows bias, as Azure CLI is cross-platform and should be prioritized or presented equally for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly state that both PowerShell and Azure CLI are supported and provide parity for Linux/macOS users.
  • Where possible, add Bash or shell scripting examples for common tasks.
  • Consider noting platform compatibility for each tool when examples are given.
GitHub Create Pull Request
Azure Resource Manager Template functions - resources ...ource-manager/templates/template-functions-resource.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for discovering list operations, but the PowerShell example is shown first. No other evidence of Windows bias is present: all ARM template examples are platform-neutral (JSON), and CLI coverage is present. No Windows-only tools or patterns are promoted, and Linux/macOS users can fully follow the documentation.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Explicitly note that both Azure CLI and PowerShell are cross-platform, and users may choose either.
  • Where possible, provide Bash or shell script snippets for common tasks, especially in sections referencing command-line usage.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation generally presents information in a cross-platform manner, with both Windows and Linux VM scenarios addressed. However, in the 'Install the VM agent' section, instructions for Windows appear before those for Linux, which is a minor instance of 'windows_first' bias. Both platforms are otherwise covered with appropriate guidance.
Recommendations
  • Alternate the order of Windows and Linux instructions in sections where both are equally relevant, or present them in parallel (side-by-side or tabbed) to avoid the perception of prioritizing one OS.
  • Continue to ensure that all examples, screenshots, and instructions are provided for both Windows and Linux where applicable.
GitHub Create Pull Request
Azure App Configuration Configuration Provider Overview ...e-app-configuration/configuration-provider-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation lists .NET-based (Microsoft-centric) libraries and examples first in all tables, with Windows-oriented platforms (.NET Standard, ASP.NET Core, .NET Framework) leading before Java, Python, JavaScript, and Go. However, the content covers cross-platform libraries and provides parity for Linux/macOS users, with samples and release notes for all major languages and platforms.
Recommendations
  • Consider rotating or randomizing the order of provider libraries in tables, or grouping by platform type (e.g., Microsoft/.NET, JVM, Python, JavaScript, Go) to avoid implicit prioritization.
  • Explicitly mention cross-platform compatibility for .NET Standard and ASP.NET Core providers, clarifying that they work on Linux/macOS as well as Windows.
  • Add a brief note at the top stating that all listed libraries are supported on Linux and macOS unless otherwise specified.
  • Where possible, provide direct links to Linux/macOS-specific usage guides or samples for .NET and other providers.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a generally cross-platform guide for running C# Azure Functions in an isolated worker process, with clear support for both Windows and Linux. However, there are minor instances of Windows bias: Windows-based tools (Visual Studio, Azure PowerShell) are listed before Linux equivalents (Visual Studio Code, Azure CLI) in some sections, and some CLI examples default to Windows scenarios. References to Windows-specific configuration (e.g., ReadyToRun, runtime identifiers) are presented before Linux alternatives, and PowerShell is mentioned as a deployment option alongside CLI, but not as prominently for Linux. All critical workflows (development, deployment, configuration) are documented for both platforms, and Linux-specific instructions are present where needed.
Recommendations
  • When listing development or deployment tools, alternate the order or present Linux and Windows options side-by-side to avoid implicit prioritization.
  • Ensure that CLI examples include both Windows and Linux syntax where differences exist.
  • Where PowerShell is mentioned, clarify its platform specificity and provide equivalent Bash/Azure CLI commands for Linux/macOS users.
  • Explicitly state platform parity in sections where both Windows and Linux are supported, to reassure users.
  • Consider adding more Linux/macOS-specific troubleshooting tips or notes where relevant.
GitHub Create Pull Request
Azure Functions host.json reference for Azure Functions 2.x ...b/main/articles/azure-functions/functions-host-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_tools
Summary
The documentation is generally cross-platform and does not show a strong Windows bias. However, there are a few minor references to Windows-specific environment variables (e.g., %TEMP%) and tools (Kudu) without explicit Linux/macOS equivalents or clarifications. Most examples and explanations are platform-neutral, and Linux-specific options (such as DisableColors for console logs) are included.
Recommendations
  • Where environment variables like %TEMP% are mentioned, clarify Linux/macOS equivalents (e.g., $TMPDIR or /tmp).
  • When referencing tools like Kudu, note their availability or alternatives for Linux/macOS environments.
  • Ensure that any file path or environment variable examples are shown for both Windows and Linux/macOS.
  • Explicitly state platform differences where relevant, especially for settings that may behave differently on Linux/macOS.
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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation generally provides cross-platform guidance for Azure Functions app settings, but there are some signs of Windows bias. Windows-specific syntax (e.g., %HOME% in AzureWebJobs_TypeScriptPath) is used in examples without Linux equivalents. PowerShell-specific settings are documented in detail, and Windows tools (Azure PowerShell) are mentioned before Linux alternatives (Azure CLI) in some guidance. In a few cases, Windows-only settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are clearly marked as such, which is appropriate. However, examples and instructions sometimes default to Windows-first patterns.
Recommendations
  • Where environment variable paths or syntax are shown (e.g., %HOME%), provide Linux/macOS equivalents (e.g., $HOME).
  • When mentioning tools for managing settings (Azure CLI, Azure PowerShell), list Azure CLI first or equally, as it is cross-platform.
  • For PowerShell-heavy sections, ensure parity by referencing equivalent settings or behaviors for other languages/runtimes.
  • Review all examples to ensure Linux/macOS users are not left guessing about platform-specific details.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform, but there are subtle signs of Windows bias. In the 'Mount file shares' section, both Azure CLI (Linux/macOS-friendly) and PowerShell (Windows-centric) examples are provided, but PowerShell is shown second. Earlier in the document, references to features like Azure Files and scaling mention 'Windows only' before Linux, and some settings (e.g., WEBSITE_CONTENTAZUREFILECONNECTIONSTRING) are described with Windows scenarios first. The 'Managed dependencies in PowerShell' note in the Azure Files table highlights PowerShell specifically, which is a Windows technology. However, Linux-specific instructions are present, and there is a dedicated section for Linux file share mounting.
Recommendations
  • Ensure that Linux/macOS examples are presented before or alongside Windows/PowerShell examples, especially in sections relevant to both platforms.
  • Where features differ by OS, clarify parity and limitations for both Linux and Windows up front.
  • Expand Linux/macOS-specific guidance, such as providing Bash or Python scripting examples where PowerShell is used.
  • Avoid highlighting Windows tools (like PowerShell) as the default unless the feature is Windows-only.
  • In tables or feature lists, mention Linux and Windows options with equal prominence.
GitHub Create Pull Request
Azure Government Azure guidance for secure isolation ...es/azure-government/azure-secure-isolation-guidance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ minor_windows_examples
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure secure isolation. However, there are several instances where Windows terminology, tools, and examples are mentioned first or exclusively, such as references to Windows Firewall, BitLocker, Hyper-V, and PowerShell. Linux equivalents are present but sometimes appear after Windows examples or are less detailed. Some sections (e.g., Hypervisor isolation, Drawbridge) are inherently Windows-centric due to Azure's underlying technology, but overall, the guidance is intended for both Windows and Linux users.
Recommendations
  • Ensure Linux tools and terminology (e.g., iptables, firewalld, SELinux, DM-Crypt) are mentioned alongside or before Windows equivalents where applicable.
  • Provide Linux-first or parallel examples for management tasks (e.g., using Azure CLI and Bash, not just PowerShell).
  • Clarify when features or patterns are Windows-only and provide explicit Linux alternatives or guidance.
  • Balance references to Windows-specific technologies (e.g., Hyper-V, BitLocker) with Linux equivalents, or note when no direct equivalent exists.
  • Where management instructions are given, ensure both Azure CLI and PowerShell are covered equally, with Linux/macOS usage shown.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are some instances of Windows bias. Windows-specific technologies (e.g., VSS, DPM, MABS, MARS agent) are referenced without equal mention of Linux alternatives or parity, and Windows terminology (VSS) is explained before mentioning Linux equivalents. The 'Application consistent backup' entry references VSS first, then Linux scripts, and the VSS entry links only to Windows documentation. Some backup features and agents are described in a Windows-centric way, though this may reflect Azure Backup's current support matrix.
Recommendations
  • Where Windows-specific technologies (e.g., VSS) are mentioned, clarify Linux equivalents or workflows (e.g., pre/post scripts, fsfreeze, etc.) and link to relevant Linux documentation.
  • For entries like 'Application consistent backup', present Linux and Windows approaches with equal prominence.
  • If backup agents or extensions are Windows-only, explicitly state this and, where possible, mention Linux support status or alternatives.
  • Add references or links to Linux backup documentation or Azure Backup support for Linux workloads where applicable.
  • Review glossary entries for implicit Windows-first ordering and rephrase to be platform-neutral where possible.
GitHub Create Pull Request
CDN Get started with the Azure CDN SDK for Node.js .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for 'Get started with the Azure CDN SDK for Node.js' demonstrates minor Windows bias by recommending Visual Studio Code (a Microsoft tool popular on Windows, though cross-platform) as the editor and referencing Visual Studio Code's launch.json for debugging and passing command-line parameters. The only explicit tool recommendation is for Visual Studio Code, and the tip about debugging is tailored to its configuration, which may be less familiar to Linux/macOS users. No Linux/macOS-specific editors, consoles, or debugging instructions are mentioned. However, all code and commands are cross-platform, and there are no PowerShell-only or Windows-only steps.
Recommendations
  • Mention alternative editors and debuggers commonly used on Linux/macOS, such as Vim, Emacs, Sublime Text, or JetBrains WebStorm.
  • Provide instructions for running and debugging the Node.js application from the command line on Linux/macOS, including how to pass command-line parameters.
  • Clarify that Visual Studio Code is available cross-platform, or provide links to setup guides for Linux/macOS.
  • Add a brief note or example showing how to run the Node.js script directly from a Bash or Terminal shell (e.g., `node app.js list profiles`).
GitHub Create Pull Request
Container Apps Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file ...iner-apps/microservices-dapr-azure-resource-manager.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 (Linux/macOS) and PowerShell (Windows) examples for all CLI commands, ensuring cross-platform usability. However, PowerShell examples are consistently included and sometimes shown before or alongside Bash, which may create a slight perception of Windows-first bias. There are no missing Linux/macOS examples, and all tooling (Azure CLI, Git) is cross-platform. No Windows-specific tools or patterns are mentioned.
Recommendations
  • Ensure Bash examples are shown first when presenting command tabs, as Bash is the default shell for most Linux/macOS users.
  • Explicitly state that all commands work on Linux/macOS unless otherwise noted.
  • Consider adding a brief note at the start clarifying parity and platform support for Azure CLI and Git.
  • If possible, minimize the prominence of PowerShell unless a Windows-only step is required.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The Azure Bastion FAQ documentation shows minor Windows bias in several areas. Browser recommendations list Windows browsers first and provide more detail for Windows users. Keyboard layout configuration instructions are given only for Windows workstations, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like setting keyboard layouts or file transfer, despite Bastion supporting SSH and RDP to non-Windows VMs.
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS workstations, not just Windows.
  • When listing supported browsers, present all platforms equally and provide configuration details for Linux/macOS where relevant.
  • Include examples or notes for Linux/macOS users in sections about native client usage, file transfer, and keyboard shortcuts.
  • Where tasks are platform-agnostic (e.g., SSH/RDP), ensure examples and guidance are not Windows-centric.
GitHub Create Pull Request
Container Apps Deploy the Dapr extension for Azure Functions in Azure Container Apps ...in/articles/container-apps/dapr-functions-extension.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 PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently presented first. This ordering may subtly signal a preference for Windows tooling. However, Linux/macOS users are not blocked, as curl examples are present and all Azure CLI commands are cross-platform.
Recommendations
  • Alternate the order of PowerShell and curl examples, or present curl first to better reflect cross-platform usage.
  • Explicitly mention that all CLI and curl commands work on Linux/macOS, and clarify that PowerShell is optional.
  • Consider adding Bash script examples for common automation tasks, if relevant.
  • Where possible, use generic shell commands (curl, Azure CLI) as the primary example, with PowerShell as an additional tab.
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 presents deployment options for Azure Container Apps in a generally cross-platform manner, but there are subtle signs of Windows bias. Visual Studio is mentioned before Visual Studio Code, and PowerShell is referenced alongside Bash for CLI automation, with no explicit Linux/macOS command examples. There are no Linux-specific editor or tool recommendations, and the resources and examples lean toward Microsoft-centric tooling, which is more familiar to Windows users.
Recommendations
  • Provide explicit Bash and Linux/macOS command examples alongside PowerShell, especially in CLI sections.
  • Include references to popular Linux/macOS code editors (e.g., JetBrains Rider, Vim, etc.) or clarify that Visual Studio Code is cross-platform.
  • Ensure that examples and resource links are balanced between Windows and Linux/macOS environments.
  • Consider listing Visual Studio Code before Visual Studio to reflect its cross-platform nature.
  • Add notes or links for Linux/macOS users about prerequisites or environment setup where relevant.
GitHub Create Pull Request
Container Apps Create a zone-redundant container app ...main/articles/container-apps/how-to-zone-redundancy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides step-by-step instructions for creating a zone-redundant container app using the Azure Portal, Azure CLI, and Azure PowerShell. The Azure PowerShell section is included alongside Azure CLI, and examples for both are provided. However, the PowerShell instructions are shown in full detail, and the tab order places Azure PowerShell immediately after Azure CLI, which may suggest a slight Windows-first orientation. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the Azure CLI instructions are fully cross-platform and suitable for Linux/macOS users. No critical steps are Windows-only, and Linux users can complete all tasks using the CLI.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider mentioning Bash or shell scripting for Linux/macOS users where environment variables are set (e.g., using export instead of PowerShell syntax).
  • Ensure tab order does not imply Windows preference (e.g., list CLI before PowerShell, or clarify cross-platform support).
  • Add a note that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
GitHub Create Pull Request
Container Apps Troubleshooting in Azure Container Apps ...s/blob/main/articles/container-apps/troubleshooting.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 is generally cross-platform, focusing on Azure CLI and portal workflows. However, there are some subtle Windows biases: references to 'elevated command prompt' and 'Docker on Windows' appear before Linux/macOS equivalents, and PowerShell examples are provided alongside Bash, but not Linux shell alternatives for PowerShell-specific tasks. The troubleshooting steps and examples are mostly platform-agnostic, but Windows terminology and tools are mentioned first or exclusively in a few places.
Recommendations
  • When mentioning Docker usage, include references to Linux/macOS installation and usage guides alongside Windows.
  • Replace 'elevated command prompt' with 'terminal with appropriate permissions' or specify both Windows and Linux/macOS equivalents.
  • For PowerShell examples, clarify that Bash/CLI commands are suitable for Linux/macOS users, and provide Linux/macOS alternatives for any PowerShell-specific tasks.
  • Ensure that any references to platform-specific tools (like 'Docker on Windows') are balanced with links or notes for Linux/macOS users.
GitHub Create Pull Request
Container Apps Integrate a virtual network with an Azure Container Apps environment ...-docs/blob/main/articles/container-apps/vnet-custom.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 (Azure CLI) and PowerShell examples for all major steps, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, and in some cases, PowerShell-specific patterns (e.g., use of hashtables, cmdlets) may be more familiar to Windows users. The presence of PowerShell tabs and examples throughout, and the use of PowerShell for resource management, reflects a moderate Windows bias, but Linux/macOS users can fully complete all tasks using Bash/Azure CLI commands. No critical steps are Windows-only, and Linux parity is generally good.
Recommendations
  • Consider listing Bash/Azure CLI examples before PowerShell examples, as Bash is the default shell on Linux/macOS and Azure CLI is cross-platform.
  • Add a brief note clarifying that Bash/Azure CLI commands work on Linux, macOS, and Windows (with WSL or native Bash), while PowerShell examples are primarily for Windows users.
  • Where possible, simplify PowerShell examples to avoid advanced Windows-centric patterns unless necessary.
  • Ensure that any referenced tooling or prerequisites (e.g., Azure CLI installation) include Linux/macOS instructions or links.
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
Low 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 environments, specifying installation paths and supported features for each. However, there is a slight Windows-first bias in some sections (e.g., installation paths listed with Windows first), and some examples or feature notes are Windows-specific (such as the HealthCheck 'forever' option and run_on_shutdown command not being supported on Windows). There are no PowerShell-only examples or exclusive use of Windows tools, but Linux-specific usage patterns (such as systemd or bash scripting) are referenced without detailed Linux examples.
Recommendations
  • List Linux paths and features before or alongside Windows equivalents to avoid implicit prioritization.
  • Provide explicit Linux command-line examples where feature behavior differs (e.g., show a bash script example for run_on_shutdown).
  • Clarify feature parity and differences in a dedicated section/table for quick reference.
  • Where commands or features are not supported on Windows, offer alternative approaches or explicitly state Linux usage.
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides authentication setup instructions for built-in, Active Directory, LDAP, and Entra ID methods. In the Active Directory section, Windows-centric patterns (DOMAIN\user) are described first and illustrated, with Windows user examples shown before UPN (user@domain.com) patterns. However, the overall instructions are platform-neutral, and Linux authentication scenarios (LDAP, Entra ID with SSH keys) are covered. There are no PowerShell-only examples, Windows-only tools, or missing Linux equivalents.
Recommendations
  • In the Active Directory section, clarify that both Windows (DOMAIN\user) and UPN (user@domain.com) formats are supported equally, and provide explicit Linux/macOS login examples if relevant.
  • Add a note in the Active Directory section that Linux/macOS users typically use UPN (user@domain.com) format, and mention any platform-specific considerations for authentication.
  • Ensure screenshots and examples alternate or include both Windows and Linux/macOS user scenarios where applicable.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform and references both Windows and Linux environments for HDInsight clusters and transformation activities. However, the only linked tutorial at the end is specifically for Spark transformation using PowerShell, which is Windows-centric. There is a slight tendency to mention Windows in cluster descriptions ("Windows/Linux-based HDInsight cluster") with Windows listed first. No Linux/macOS-specific examples or CLI alternatives are provided in the main page.
Recommendations
  • Add tutorials or example links for transforming data using Bash, Azure CLI, or other cross-platform tools alongside PowerShell.
  • When referencing environments, alternate or randomize the order of 'Windows/Linux' to avoid subtle prioritization.
  • Ensure that for every PowerShell-based example or tutorial, a Linux/macOS-friendly alternative (e.g., Bash, Azure CLI, Python SDK) is provided or linked.
  • Explicitly mention platform parity where applicable, reassuring users that all features are available on Linux/macOS unless otherwise noted.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page provides links to example resources for creating Event Grid subscriptions, listing Azure CLI, PowerShell, and ARM template samples. The PowerShell sample is mentioned second, immediately after the CLI sample, and before ARM templates. No Linux-specific tools or examples are missing, but the ordering may subtly suggest Windows/PowerShell as a primary approach.
Recommendations
  • List cross-platform tools (such as Azure CLI) before Windows-specific tools (PowerShell) to reinforce platform neutrality.
  • Explicitly state that Azure CLI and ARM templates are fully supported on Linux/macOS.
  • Consider adding Bash or REST API examples if relevant, to further demonstrate Linux parity.
  • If possible, clarify that PowerShell is available cross-platform, but is traditionally associated with Windows.
GitHub Create Pull Request