Scan Details - Linux-first Docs for Azure

1621

Pages Scanned

56

Pages Flagged

1621

Changed Pages

3.5%

% Pages Flagged

Scan Information

Started At: 2025-08-08 00:00:07

Finished At: 2025-08-08 00:35:09

Status: completed

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no mention or examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). The instructions for scripting and automation reference only PowerShell cmdlets and installation, and there are no Bash or Linux-native shell examples. The structure presents PowerShell before ARM templates, and there is no guidance for Linux users or mention of Linux-specific workflows.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell command sequences, including resource group creation, managed identity assignment, and updates.
Include Bash shell snippets for scripting scenarios, especially for Linux/macOS users.
Where installation of tools is referenced, provide links and instructions for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash).
Consider presenting Azure CLI examples before or alongside PowerShell to avoid the perception of Windows-first bias.
Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide troubleshooting notes for common cross-platform issues.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. In the automation section, Azure PowerShell is given equal prominence to Azure CLI, which is more cross-platform, but PowerShell is traditionally associated with Windows. Throughout, the Azure portal (a web UI) is used, which is platform-neutral, but there are no explicit Linux shell or scripting examples beyond the CLI. There are no Linux-specific tools or shell script examples, and PowerShell (a Windows-centric tool) is featured as a primary automation option.

Recommendations:

Present Linux and Windows options in parallel, or alternate which is listed first to avoid 'windows_first' ordering.
Provide Bash shell scripting examples for automation, especially for Linux users, in addition to Azure CLI and PowerShell.
Clarify that Azure CLI is cross-platform and recommend it as the default for scripting, with PowerShell as an alternative.
Where possible, include Linux-native tooling or workflows, such as Bash scripts or integration with Linux package managers.
Explicitly state that all examples work on both Windows and Linux unless there are platform-specific caveats.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates subtle Windows bias by listing Windows SKU availability before Linux, referencing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and using Windows terminology (e.g., 'Windows SKU', 'Azure PowerShell') without equal emphasis on Linux-native tools or shell environments. While Linux is mentioned and supported, examples and instructions are not always presented with Linux parity or in a Linux-first manner.

Recommendations:

Present Linux and Windows examples side-by-side or alternate their order to avoid always listing Windows first.
Include Bash or shell script automation examples in addition to Azure CLI and PowerShell, especially for Linux users.
Clarify that Azure CLI commands are cross-platform and can be run natively on Linux, macOS, and Windows.
Where PowerShell is referenced, mention that PowerShell Core is cross-platform, or provide equivalent Bash commands.
Use neutral terminology (e.g., 'Platform SKU availability') instead of 'Windows SKU availability' unless a distinction is necessary.
Explicitly state Linux support and provide Linux-specific guidance where platform differences exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias, particularly in the guidance for identifying impacted Azure Traffic Manager endpoints. The only provided script for this scenario is a PowerShell script, with explicit instructions for downloading and running it in PowerShell. There are no equivalent Bash, Azure CLI, or cross-platform alternatives, and no mention of how Linux or Mac users should proceed. Elsewhere, examples and instructions focus on REST API and Azure CLI, which are cross-platform, but the only concrete script-based automation is Windows-centric.

Recommendations:

Provide a Bash or Azure CLI script alternative for identifying non-Azure Traffic Manager endpoints, or at least mention how Linux/Mac users can achieve the same result.
When referencing scripts, clarify platform compatibility and offer guidance for non-Windows users.
Where possible, prefer Azure CLI or REST API examples for automation tasks, as these are cross-platform.
Explicitly state if a scenario or tool is only supported on Windows, and provide a workaround or alternative for Linux/Mac users.
Consider including a table or section summarizing all available tools/scripts for each OS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by featuring PowerShell as the only explicit scripting example in the 'Automate with scripts' section, with no corresponding Bash or Linux shell script. Additionally, while Azure CLI is mentioned, it is only linked and not shown inline, and the PowerShell example is presented more prominently. There are no Linux-specific instructions or screenshots, and the workflow assumes use of the Azure Portal or Windows-centric tools, with no mention of Linux command-line workflows or file handling (e.g., .pfx file creation on Linux).

Recommendations:

Add explicit Bash/Azure CLI script examples inline, similar to the PowerShell example.
Include Linux-specific guidance for certificate creation, upload, and management (e.g., using OpenSSL to create .pfx files on Linux).
Ensure that screenshots and instructions are not Windows-centric; consider including Linux terminal screenshots or notes.
Present Azure CLI and Bash examples before or alongside PowerShell to avoid a 'Windows-first' impression.
Reference Linux documentation or workflows where relevant, such as for inspecting headers or configuring HTTPS in Linux-hosted apps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell examples for per-app scaling, referencing Azure PowerShell cmdlets exclusively, and omitting equivalent CLI or scripting instructions for Linux users. There are no Bash, Azure CLI, or cross-platform examples, and the PowerShell approach is presented first and exclusively, which may disadvantage users on Linux or macOS.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell commands to support Linux and macOS users.
Include Bash script examples for configuring per-app scaling where appropriate.
Present cross-platform (CLI or ARM template) approaches before or alongside PowerShell to avoid the impression of Windows-first tooling.
Explicitly mention that all operations can be performed from any OS using Azure CLI or ARM templates, not just PowerShell.
Consider adding a table or section comparing PowerShell and CLI commands for common tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing several features and tools that are either exclusive to Windows apps or are described in detail only for Windows. Sections such as 'Investigation of application code problems', 'Proactive CPU monitoring', 'Proactive auto-healing', and 'Navigator' are marked as Windows-only, with no Linux equivalents or alternatives discussed. Linux support is mentioned only in passing, and there are no Linux-specific troubleshooting examples or screenshots. This may leave Linux users with less guidance and fewer actionable steps.

Recommendations:

Provide Linux-specific troubleshooting steps and examples, especially for diagnostics and advanced tools.
Where a feature is Windows-only, explicitly mention Linux alternatives or workarounds, or clarify if there is no equivalent.
Include screenshots and walkthroughs for Linux-based App Service apps, not just Windows.
Ensure parity in documentation by highlighting which diagnostic tools and features are available for Linux, and link to relevant Linux documentation where appropriate.
Consider a comparison table summarizing feature availability and differences between Windows and Linux App Service environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio deployment to Windows App Service, without providing equivalent Linux examples or explicitly mentioning Linux deployment options. References to Kudu and Visual Studio are present, but there is no guidance for Linux users or parity in deployment tooling and monitoring.

Recommendations:

Add explicit examples and instructions for deploying WebJobs to Linux-based App Service plans, including command-line (CLI) and cross-platform tooling.
Provide parity in deployment guidance by including VS Code, Azure CLI, and GitHub Actions examples that work on both Windows and Linux.
Clarify which features (such as Kudu or Visual Studio deployment) are available or different on Linux App Service plans.
Include Linux-specific troubleshooting and monitoring guidance, such as using App Service diagnostics or log streaming, especially where Kudu is not available.
Ensure that references to Windows-specific tools (like Visual Studio) are balanced with cross-platform alternatives.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are included alongside CLI without clarifying platform parity. There is no explicit mention of Linux-specific tools or shell environments, and PowerShell is a Windows-first tool (though now cross-platform, it is still most familiar to Windows users). The documentation does not provide any Linux shell-specific examples (e.g., bash scripting, jq usage, or curl for REST API), and in the outbound IPv6 section, it notes that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. The overall structure does not prioritize Linux or cross-platform parity in examples or explanations.

Recommendations:

Clearly indicate which commands are cross-platform and which are Windows-specific (e.g., label PowerShell examples as such).
Provide Linux-native shell examples where possible (e.g., using curl or jq to retrieve properties via the Azure REST API).
When listing command examples, present Azure CLI (which is cross-platform) before PowerShell, or group them under clear headings for each platform.
Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide troubleshooting notes for common Linux environments if needed.
For sections where functionality is Windows-only (such as outbound IPv6), provide a clear roadmap or alternatives for Linux users, or note when parity is expected.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing installation instructions first for the .NET Core CLI (cross-platform), but then immediately following with instructions for the Visual Studio Package Manager Console, which is Windows-specific and uses PowerShell syntax. There are no explicit Linux or macOS-specific instructions or examples, and the only GUI tool mentioned is Visual Studio, which is primarily a Windows application. No mention is made of Linux-native editors or package managers.

Recommendations:

Explicitly mention that the .NET Core CLI instructions work on Linux and macOS, not just Windows.
Include examples for installing the NuGet packages using Linux-native package managers or editors (e.g., JetBrains Rider, VS Code).
Avoid referencing only Windows-specific tools like Visual Studio and the Package Manager Console; if mentioned, provide parity by referencing cross-platform alternatives.
Add a note clarifying that the PowerShell-based Package Manager Console is only available on Windows, and suggest equivalent steps for Linux users.
Consider including screenshots or terminal examples from Linux/macOS environments to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as IIS, Procdump, and PowerShell), focusing on .NET/ASP.NET examples, and linking to Windows-centric resources. The Kudu Debug Console section highlights PowerShell and DOS commands, with no mention of Bash or Linux shell support. Diagnostic and profiler instructions are tailored for Windows, and there are no Linux-specific examples or guidance for troubleshooting on Linux-based App Service environments.

Recommendations:

Include Linux-specific troubleshooting steps and examples, such as using Bash in the Kudu console, Linux log file locations, and Linux-compatible diagnostic tools.
Provide parity in profiler and diagnostic instructions for Linux-based App Service plans (e.g., Application Insights Profiler for Linux, or alternatives).
Mention Linux equivalents for tools like Procdump (such as gcore or dotnet-dump) and provide links to relevant documentation.
Balance references to PowerShell with Azure CLI and Bash examples for managing and restarting apps.
Clarify when instructions or features are Windows-only, and provide alternative steps or notes for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows-first bias by providing more detailed instructions and features for Windows App Service apps, such as web server logging, detailed error messages, and failed request tracing, which are not available or not documented for Linux apps. Linux instructions are present but less detailed, and some features are explicitly marked as Windows-only. Additionally, Windows tools and log formats (e.g., W3C, Log Parser) are mentioned without Linux equivalents.

Recommendations:

Provide equivalent Linux examples and instructions wherever possible, especially for enabling and accessing logs.
Clearly indicate feature parity or lack thereof between Windows and Linux App Service plans, and suggest alternative approaches for Linux where features are missing.
Include Linux-native tools or commands for accessing and analyzing logs (e.g., using tail, grep, less, or Azure Storage Explorer on Linux).
Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group them under clear subheadings.
If certain logging features are unavailable on Linux, explicitly state this and provide recommended workarounds or alternatives.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for configuring Azure RBAC, with no mention or examples of cross-platform tools such as Azure CLI or Bash scripting. The PowerShell section is detailed and includes multiple cmdlet examples, while there is no equivalent section for Linux/macOS users. The only command-line automation path described is via PowerShell, which is primarily a Windows tool, though available cross-platform. There is also no mention of Bash, shell, or Azure CLI commands, and the portal instructions do not address OS-specific nuances.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax where appropriate.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Structure the 'Configure Azure RBAC' section to present both PowerShell and Azure CLI options, or provide a table comparing both approaches.
Ensure that troubleshooting and automation guidance is not limited to Windows/PowerShell, but also addresses Linux/macOS environments.
Where possible, use neutral language such as 'command-line tools' and clarify when instructions are OS-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples use PowerShell syntax, and the deployment script is a PowerShell script (.ps1) with no alternative for Bash or native Linux shell. The instructions explicitly start with 'Open Windows PowerShell,' and while there is a tip about installing PowerShell on Linux/macOS, there are no native Linux shell or Bash examples. Additionally, references to tools and commands (such as Get-AzLocation) are PowerShell-specific, with no mention of Azure CLI or cross-platform alternatives.

Recommendations:

Provide equivalent Bash or native Linux shell examples for all steps, especially for cloning the repo and running deployment scripts.
Offer a Bash or shell script alternative to the PowerShell deployment script, or document how to perform the deployment using Azure CLI commands.
Present cross-platform instructions first, or at least in parallel with Windows/PowerShell instructions, to avoid the 'Windows-first' impression.
Reference Azure CLI commands (which are cross-platform) instead of or in addition to PowerShell-specific commands like Get-AzLocation.
Clearly indicate which steps are platform-specific and provide guidance for both Windows and Linux/macOS users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by providing PowerShell-based commands and examples (e.g., AzureCLI@2 with scriptType: 'pscore', PowerShell@2 tasks, and explicit PowerShell code blocks) without offering equivalent bash or Linux shell alternatives. Windows tools and patterns (such as AzPowershell, PowerShell tasks, and .NET/NUnit focus) are mentioned and used throughout, often without parallel Linux-native instructions. In several places, PowerShell is the only scripting language shown, and there are no bash or sh examples for Linux users, especially in CI/CD pipeline steps. This may hinder Linux users or those using non-Windows runners.

Recommendations:

Provide bash/sh equivalents for all PowerShell commands and scripts, especially in CI/CD pipeline examples.
When showing Azure CLI or login steps, include both PowerShell and bash variants, or use cross-platform CLI commands where possible.
Avoid using Windows-specific terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; instead, present both Windows and Linux options side by side.
Explicitly mention compatibility with Linux runners and provide examples using Ubuntu or other Linux environments.
For .NET/NUnit examples, clarify that they are cross-platform and, if possible, show how to run them on Linux (e.g., using dotnet CLI on Ubuntu).
In code blocks and workflow YAML, use shell-agnostic syntax or provide both shell and PowerShell versions.
Review all sections for implicit Windows-first assumptions and add Linux parity throughout.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no CLI (cross-platform) or Linux-specific instructions or examples provided, and the only explicit tooling reference is to PowerShell, which is traditionally associated with Windows environments. This may give the impression that Windows or PowerShell is the preferred or only supported environment for these operations.

Recommendations:

Include equivalent Azure CLI (az) instructions and tutorials alongside PowerShell examples to ensure cross-platform accessibility.
In the 'Next steps' section, provide links to both PowerShell and CLI-based tutorials for creating and managing autoscaling Application Gateways.
Explicitly mention that all features are available via both PowerShell and CLI, and provide parity in documentation coverage.
If possible, add Bash script examples or references for Linux users.
Avoid listing Windows/PowerShell tools before their cross-platform or Linux equivalents, or present them together.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. While the Azure CLI is used (which is cross-platform), the instructions mention using PowerShell commands to deploy the sample application, and Visual Studio Code is recommended without noting Linux alternatives. There are no explicit Linux/macOS terminal examples or references to Bash, and the deployment steps do not clarify if the commands are compatible with Linux shells. The documentation also does not provide Linux-specific troubleshooting or environment validation steps.

Recommendations:

Provide explicit Bash/Linux shell command examples alongside PowerShell where applicable, or clarify that the Azure CLI commands are cross-platform and show syntax for both environments.
When referencing Visual Studio Code, mention that it is available on Windows, Linux, and macOS, and provide links or notes for Linux installation.
If PowerShell is required for deployment, provide equivalent Bash scripts or instructions for Linux/macOS users.
Include notes or troubleshooting steps for common Linux/macOS issues (e.g., permissions, path differences) when using the Azure CLI or Git.
Explicitly state that the tutorial is cross-platform, and ensure screenshots or UI references are not Windows-specific unless unavoidable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell as the primary method for configuration and details, mentioning PowerShell before CLI, and lacking any explicit Linux or Bash examples. The 'Next steps' section links only to a PowerShell-based configuration guide, and throughout the document, PowerShell is consistently listed before CLI or REST. There are no Linux-native command examples or references to Bash/Unix shell usage, which may disadvantage Linux users.

Recommendations:

Provide parallel Linux/Bash examples alongside PowerShell, especially in configuration and 'Next steps' sections.
Ensure Azure CLI examples are given equal prominence to PowerShell, and mention them first or together.
Link to both PowerShell and Azure CLI/Bash configuration guides in 'Next steps' and throughout the documentation.
Explicitly state that all operations can be performed on Linux/macOS using Azure CLI, and provide sample commands.
Avoid listing PowerShell before CLI unless there is a technical reason; alternate ordering or group them together.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. It consistently references Visual Studio Code (a Microsoft product popular on Windows), the Azure Portal (web-based but often associated with Windows-centric workflows), and .NET/NUnit (commonly used in Windows environments). There are no explicit Linux or macOS-specific instructions, nor are there terminal commands or screenshots showing Linux shells or file paths. The CLI instructions are generic (e.g., 'npx', 'dotnet'), but there is no mention of Linux-specific setup, environment variables, or troubleshooting. The documentation does not provide parity for Linux users in terms of examples, tooling, or environment setup.

Recommendations:

Include explicit Linux/macOS instructions and screenshots where relevant, such as using Bash or Zsh shells, and showing file paths in Linux format.
Add notes or examples for setting environment variables in Linux/macOS shells (e.g., 'export PLAYWRIGHT_SERVICE_URL=...') alongside the .env approach.
Mention Linux package managers (e.g., apt, yum, brew) for installing prerequisites like Node.js, .NET, or Azure CLI.
Provide parity in troubleshooting tips for Linux users (e.g., permissions, path issues).
Balance references to Visual Studio Code with mentions of other editors or CLI-only workflows, or clarify that VS Code is cross-platform.
Ensure screenshots and instructions do not assume a Windows environment by default.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by using PowerShell syntax for all command-line examples (e.g., git, npm, npx), omitting Linux/macOS shell equivalents, and not clarifying cross-platform compatibility. There are no explicit Linux or macOS instructions or screenshots, and the command-line instructions assume a Windows environment. This may confuse or exclude users on Linux or macOS.

Recommendations:

Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) command examples, or use a neutral shell syntax where possible.
Explicitly state that the commands work on all platforms, or note any platform-specific differences.
Use generic 'terminal' or 'shell' terminology instead of 'command window', and clarify that instructions apply to all major OSes.
Include Linux/macOS-specific installation or troubleshooting notes where relevant.
Add screenshots or notes for Linux/macOS environments, not just Windows/Azure Portal.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for installation. There are no Linux or cross-platform alternatives or examples provided for these tasks, and Windows tools and patterns are mentioned before any platform-neutral options.

Recommendations:

Provide equivalent Azure CLI or Azure Cloud Shell examples for checking Application Gateway settings, as these are cross-platform and work on Linux, macOS, and Windows.
Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, and provide instructions or examples for their use.
When referencing file paths, commands, or installation steps, include Linux/macOS equivalents (e.g., use 'sudo' instead of 'Run as administrator').
When suggesting tools like Fiddler, mention cross-platform alternatives and clarify that Fiddler is primarily for Windows, while other tools are available for Linux/macOS.
Structure troubleshooting steps and tool recommendations to be platform-neutral or to present Windows and Linux options side-by-side.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only PowerShell-based automation examples for configuring Azure Application Gateway with Key Vault certificates. There are no CLI/bash/Linux shell examples, and PowerShell is referenced as the primary automation tool. The 'Next steps' section links exclusively to a PowerShell guide, and there is no parity for Linux or cross-platform users. Azure CLI is mentioned in passing, but no concrete CLI or bash examples are provided.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside PowerShell scripts for all configuration steps, especially for certificate referencing and listener configuration.
Where automation is discussed, present both PowerShell and bash/CLI options, and clarify that Azure CLI is cross-platform.
In the 'Next steps' section, provide links to both PowerShell and Azure CLI guides.
Avoid referencing PowerShell steps as the default or only automation path; instead, present both PowerShell and CLI equally.
Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide sample commands.
Where ARM/Bicep templates are referenced, include CLI deployment examples (e.g., az deployment group create) in addition to PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows-first and PowerShell-centric bias. Windows instructions, tools, and examples are consistently presented before Linux equivalents. PowerShell and Windows-specific tools (e.g., Control Panel, cert store paths, Windows event logs) are emphasized, and most code samples are PowerShell-based. Linux instructions are present but often less detailed, and there are few, if any, Linux shell or Python script examples for runbook operations or authentication. Some features (like Hybrid Worker credentials) are not supported on Linux, but this is not always clearly highlighted up front.

Recommendations:

Alternate the order of Windows and Linux sections/examples to avoid always presenting Windows first.
Provide equivalent Linux shell (bash) and Python examples for all PowerShell/Windows examples, especially for runbook authentication, starting runbooks, and certificate/key management.
Include Linux-specific troubleshooting and logging details at parity with Windows (e.g., mention Linux event logs or syslog integration if available).
Where features are Windows-only (e.g., Hybrid Worker credentials), clearly state this at the start of the relevant section and suggest Linux alternatives if possible.
Add more Linux-focused guidance for common tasks, such as using managed identities, environment variable management, and runbook signing.
Where PowerShell is used as the only example, provide Python or bash alternatives, especially for Linux users.
Ensure that links and references are balanced between Windows and Linux documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure PowerShell commands and references to PowerShell scripts for migration and preview registration. Azure CLI is mentioned, but the examples provided are all PowerShell-based, and there are no Linux shell/bash equivalents. The migration tooling is described as a PowerShell script, and the documentation custom metadata includes 'devx-track-azurepowershell', further emphasizing the focus on Windows tooling. There are no explicit Linux or cross-platform examples, and PowerShell is presented as the default or only automation method.

Recommendations:

Provide equivalent Azure CLI (bash/shell) examples alongside PowerShell commands for all operations, including preview registration and unregistration.
Mention and link to cross-platform tools and scripts (e.g., Azure CLI, ARM templates, Bicep) wherever PowerShell scripts are referenced.
Ensure that migration tooling is available and documented for both PowerShell and Azure CLI users.
Adjust language to refer to 'Azure CLI or PowerShell' instead of only PowerShell when discussing automation or scripting.
Include explicit Linux/macOS instructions or notes where platform-specific steps may differ.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions and tools (winget, PowerShell) are presented before Linux equivalents. The Windows instructions are more detailed and reference Windows-specific package managers, while the Linux instructions are less prominent and less detailed. The rest of the guide uses cross-platform tools (Azure CLI, Helm, kubectl) and Bash-style scripting, which are generally Linux-friendly, but the initial ordering and emphasis favor Windows.

Recommendations:

Present Linux and Windows installation instructions for Helm with equal prominence and detail, possibly starting with Linux or providing both side-by-side.
Include explicit Bash and PowerShell examples where relevant, or clarify that all CLI commands are cross-platform unless otherwise noted.
Avoid referencing Windows-specific tools (like winget) before more universal installation methods.
In general, ensure that Linux instructions are not treated as secondary or afterthoughts, and provide parity in troubleshooting and usage notes for both platforms.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for disabling local authentication in Azure Automation. All command-line guidance is given using PowerShell cmdlets or Azure PowerShell modules, with no mention of Bash, Azure CLI, or Linux-native tooling. The documentation assumes the use of Windows tools and patterns, and does not provide equivalent steps or examples for Linux or cross-platform environments.

Recommendations:

Provide equivalent Azure CLI (az) commands for checking and updating the DisableLocalAuth property, as Azure CLI is cross-platform and widely used on Linux.
Include REST API examples using curl or HTTPie to demonstrate how to update the flag from Linux or non-Windows environments.
Explicitly mention that the steps can be performed from any platform using REST API calls, and provide sample scripts for Bash.
Balance the documentation by presenting both PowerShell and non-PowerShell (e.g., Bash, CLI) examples side by side.
Clarify any platform dependencies or limitations, and guide users on how to perform the same operations from Linux/macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation presents configuration methods in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is more detailed, with extensive code samples and a dedicated cmdlet reference, while the Azure CLI section is less detailed and lacks parity in explanation and references. There are no explicit Linux or Bash shell examples, and the documentation does not mention or provide guidance for Linux-specific environments or tools. This structure and content may unintentionally favor Windows users and PowerShell workflows.

Recommendations:

Present Azure CLI instructions before or alongside PowerShell to avoid implying Windows/PowerShell as the primary method.
Ensure CLI and PowerShell sections have equivalent depth, including references and explanations.
Add explicit Bash/Linux shell examples or notes, especially for CLI commands, to clarify cross-platform compatibility.
Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Where possible, provide troubleshooting or environment setup notes for Linux users (e.g., package installation, permissions).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally provides cross-platform OpenSSL instructions for certificate generation and covers web server configuration for both Windows (IIS) and Linux (Apache, NGINX). However, there is a Windows-first bias in several areas: (1) Windows tools and patterns (e.g., IIS, PowerShell, C:\ paths) are mentioned before Linux equivalents; (2) the Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example; (3) references to editing the hosts file and certificate import are Windows-centric, with no Linux-specific guidance.

Recommendations:

Provide Azure CLI examples alongside or before Azure PowerShell examples for uploading certificates to Application Gateway, as Azure CLI is cross-platform.
When referencing file paths (e.g., C:\Users\...), include Linux path equivalents (e.g., /home/user/...).
For instructions on importing root certificates into the trusted store, include Linux-specific steps (e.g., update-ca-certificates on Ubuntu) in addition to Windows instructions.
When mentioning editing the hosts file, provide the Linux path (/etc/hosts) and editing instructions.
Consider presenting web server configuration sections (IIS, Apache, NGINX) in a neutral or rotating order, or group them by platform to avoid implicit prioritization.
Where possible, avoid assuming the user is on Windows, and explicitly state when steps differ between platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by recommending Azure Cloud Shell (which defaults to Bash or PowerShell, but is often associated with Windows users), visually highlighting the Azure PowerShell icon, and not providing explicit Linux shell or terminal instructions. The instructions and screenshots prioritize Windows-centric tools and workflows, and there is no mention of Linux-specific environments or alternative Linux-native tools. All command-line examples are generic Bash/Azure CLI, but the visual cues and tool recommendations are Windows-oriented.

Recommendations:

Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify that all instructions work equally well in Linux terminals.
Add screenshots or references to Linux terminal environments (e.g., GNOME Terminal, Konsole) alongside the Azure PowerShell icon.
Provide a brief note for Linux users on how to install and use the required tools (az, kubectl, helm, jq) natively on Linux, with links to Linux-specific installation guides.
Avoid using only Windows/PowerShell icons or imagery; include cross-platform visuals.
Where possible, add a section or callout confirming that all steps are cross-platform and tested on Linux, macOS, and Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exhibits a strong Windows and PowerShell bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in the most detail, with extensive examples and troubleshooting focused on Windows-specific paths, cmdlets, and behaviors. Many code samples and known issues reference Windows file paths (e.g., C:\modules), Windows environment variables, and Windows-centric tools. Linux support is mentioned only in passing, often as a limitation (e.g., certain runbooks cannot run on Linux Hybrid Runbook Workers), and there are no Linux-specific examples or troubleshooting guidance. Python runbooks receive less coverage, and Linux-specific considerations are minimal or absent.

Recommendations:

Provide Linux-specific examples for PowerShell and Python runbooks, including file paths, environment variables, and troubleshooting steps relevant to Linux Hybrid Runbook Workers.
Balance the order of presentation so that Python and Linux support are not always secondary to Windows/PowerShell.
Explicitly document any differences or additional steps required for Linux Hybrid Runbook Workers, including module management, file system access, and environment setup.
Include sample scripts and known issues that are relevant to Linux environments, not just Windows.
Where limitations exist for Linux, provide workarounds or alternative approaches where possible.
Ensure that references to tools, paths, and environment variables are cross-platform or clearly indicate when they are Windows-specific.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively references Azure PowerShell scripts for migration, with no mention of Azure CLI, Bash, or Linux-native tools. All automation and scripting guidance is centered on PowerShell, which is traditionally associated with Windows environments. There are no examples or instructions for users who may prefer or require Linux-based workflows.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for all migration steps, alongside PowerShell examples.
Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or cross-platform PowerShell Core.
Include Bash script examples or references for common migration tasks.
Clarify any platform dependencies or prerequisites for the provided scripts.
Ensure documentation parity by presenting both Windows and Linux options side-by-side where automation or scripting is discussed.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by emphasizing PowerShell and Windows-centric tools and patterns throughout. PowerShell and DSC (Desired State Configuration, a Windows technology) are mentioned repeatedly, often without equivalent Linux examples or references to Linux-native automation tools. The 'Modules gallery' and integration examples focus on PowerShell, and the configuration management section centers on PowerShell DSC. Although Linux is mentioned as supported, there are no concrete Linux-specific examples, tools, or workflows provided. Windows technologies (e.g., Active Directory, SQL Server, SharePoint) are listed in scenarios, while Linux equivalents are absent.

Recommendations:

Add Linux-specific examples for runbooks, such as using Bash or Python scripts to automate Linux tasks.
Mention and provide guidance for Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) where appropriate, or clarify integration options.
Balance scenario examples by including Linux workloads and services (e.g., Apache, NGINX, MySQL, systemd services) alongside Windows-centric ones.
Expand on how Python runbooks can be used for Linux automation, with sample use cases.
In the 'Modules gallery' and shared resources sections, highlight modules/packages relevant to Linux management.
Ensure that references to configuration management do not exclusively focus on PowerShell DSC; discuss cross-platform or Linux-native alternatives where possible.
Where Windows tools or technologies are mentioned, provide Linux equivalents or parallel guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples and references are presented as the only scripting/automation option, and there is no mention of Linux-native tools or workflows. The structure also presents PowerShell before any mention of CLI or REST API, and the only detailed automation example is for PowerShell.

Recommendations:

Add Azure CLI (az) command examples alongside PowerShell for all automation and deletion tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Include Bash script snippets or instructions where relevant, especially for unlinking and deleting resources.
Explicitly mention that PowerShell is available on Linux and macOS, but also provide CLI alternatives for users who prefer native Linux tools.
Reorder sections so that Azure CLI examples are presented alongside or before PowerShell, or use tabs to allow users to select their preferred platform.
Where REST API is mentioned, provide curl or HTTP request examples that can be run from any OS.
Review all screenshots and UI instructions to ensure they are not Windows-specific, or clarify when steps are platform-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong bias toward Windows and PowerShell. Most examples, screenshots, and REST API payloads focus on PowerShell runbooks and the Az PowerShell module. There is extensive mention of Windows/PowerShell-specific tools and patterns (e.g., PowerShell Gallery, .zip modules, Get-Module cmdlet), while Linux/Python equivalents are only briefly mentioned or omitted. Linux-specific details (e.g., .whl files for Python) are present but minimal, and there are no practical Linux/Python runbook examples or screenshots. The documentation consistently presents PowerShell/Windows options first and in more detail.

Recommendations:

Provide parallel, detailed examples for Python runbooks, including REST API payloads and portal screenshots.
Include Linux/Python-specific instructions and troubleshooting steps, not just brief notes.
When referencing package formats (e.g., .zip for PowerShell), also explain and show .whl or other Linux-native formats for Python.
Demonstrate how to view installed Python packages in a runbook, similar to the PowerShell 'Get-Module' example.
Balance the order of presentation so that Python/Linux options are given equal prominence to PowerShell/Windows.
Reference both PowerShell Gallery and PyPI (Python Package Index) for package sources.
Clarify when a feature or limitation applies only to PowerShell/Windows or Python/Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Windows and Linux troubleshooting steps for Hybrid Runbook Workers, but there is a noticeable Windows bias. Windows examples, tools, and registry paths are often presented first or in greater detail. Several scenarios (e.g., registry edits, event log checks, PowerShell scripts) are Windows-specific, with Linux equivalents either less detailed or missing. PowerShell and Windows event log troubleshooting are emphasized, while Linux log and troubleshooting methods are less thoroughly covered.

Recommendations:

Alternate the order of Windows and Linux instructions so that Linux is presented first in some sections.
Ensure Linux troubleshooting steps are as detailed as Windows, including equivalent commands for log collection, service status, and error investigation.
Provide Linux equivalents for all Windows-specific tools and scripts (e.g., PowerShell scripts, registry edits, event log checks).
Where Windows registry or event log locations are mentioned, include corresponding Linux configuration or log file locations, or explicitly state if not applicable.
For each scenario that is Windows-only, clarify if there is no Linux equivalent or provide a comparable Linux troubleshooting path.
Balance the use of PowerShell examples with Bash or Python examples for Linux.
Review the language to avoid implying Windows is the default or primary platform.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page focuses exclusively on configuration instructions for Visual Studio and Visual Studio Code, both of which are primarily associated with Windows development environments. There are no instructions or examples for configuring the Roslyn Analyzer in Linux-native editors or workflows (such as JetBrains Rider, Vim, or CLI-based setups), nor is there mention of cross-platform command-line usage. The ordering and content implicitly prioritize Windows-centric tools and workflows.

Recommendations:

Add instructions for configuring and running the Roslyn Analyzer using .NET CLI commands (e.g., dotnet build, dotnet format) that work on all platforms, including Linux.
Include guidance for using the analyzer in other popular cross-platform editors such as JetBrains Rider, Vim, or Emacs.
Explicitly mention that Visual Studio Code is cross-platform and provide Linux/macOS-specific notes or screenshots where applicable.
Provide troubleshooting or configuration steps for users developing on Linux or macOS, such as environment variable settings or dependencies.
Reorder or supplement the documentation to present cross-platform or Linux-friendly options before or alongside Windows-specific instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows-specific instructions, tools, and examples are often presented before or more prominently than their Linux equivalents. Windows tools (such as Visual Studio and PowerShell) are mentioned first or exclusively in several sections, and some CLI commands are shown with Windows-centric parameters or context. There are also places where Linux-specific guidance is less detailed or omitted, and PowerShell is referenced without equal emphasis on Bash or other Linux shells.

Recommendations:

Ensure that all command-line instructions (such as Azure CLI examples) are shown with both Windows (PowerShell/CMD) and Linux (Bash) syntax, using tabs or side-by-side presentation.
When listing tools or workflows (e.g., Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell), alternate the order or present them in a neutral way, rather than always listing Windows-first options.
Provide Linux-specific examples and troubleshooting steps wherever Windows-specific ones are given (e.g., for debugging, deployment, and configuration).
Explicitly mention Linux support and any differences in behavior, especially in sections about deployment, debugging, and performance optimizations.
Where PowerShell is referenced, also provide Bash equivalents, and clarify when a step is OS-specific.
Add more explicit Linux container deployment examples, and ensure parity in instructions for both OSes.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are consistently present and sometimes shown first or exclusively in advanced scenarios. There are no explicit Linux shell (bash) or platform-agnostic scripting examples outside of Azure CLI. The documentation assumes familiarity with PowerShell cmdlets, which are more common in Windows environments, and does not highlight Linux-native tooling or workflows beyond Azure CLI.

Recommendations:

Ensure that for every PowerShell example, an equivalent Azure CLI (bash-friendly) example is provided and shown with equal prominence.
Where possible, provide bash script snippets or explicit Linux shell usage, especially for advanced scenarios (e.g., multi-source rules, HTTP header filtering), not just PowerShell.
In tabbed code sections, alternate the order so that Azure CLI is not always after PowerShell, or default to Azure CLI as the first tab to avoid Windows-first perception.
Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux), and encourage their use for Linux users.
If certain features are only available via PowerShell, clearly state this and provide workarounds or alternatives for Linux users where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation only provides instructions for cleaning up resources via the Azure portal, which is a GUI-based method commonly associated with Windows users. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or Bash, which are preferred by many Linux users. This omission may make it less accessible for Linux users or those who prefer command-line interfaces.

Recommendations:

Add equivalent instructions for deleting the resource group using Azure CLI (az group delete) with example commands.
Provide both Windows (PowerShell) and Linux (Bash) command-line examples where relevant.
Explicitly mention that the Azure portal method is cross-platform, but highlight command-line alternatives for users on Linux or those who prefer automation.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally platform-neutral, focusing on Azure portal steps and DNS configuration. However, in the troubleshooting section, the only example for clearing the DNS cache is for Windows (`ipconfig /flushdns`), with no equivalent command or mention for Linux or macOS users. This presents a subtle 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps such as clearing the DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
Explicitly mention that the instructions apply to all platforms, and provide platform-specific notes where appropriate.
Review other troubleshooting and automation sections to ensure parity of examples and commands for Linux, macOS, and Windows users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but the PowerShell example is presented first and in greater detail, which may indicate a slight Windows-first and PowerShell-heavy bias. There are no explicit Linux shell or bash examples, and the PowerShell script is more prominent, which could disadvantage Linux users who are less familiar with PowerShell.

Recommendations:

Present Azure CLI (bash/shell) examples before PowerShell, or at least give them equal prominence.
Explicitly mention that Azure CLI commands work cross-platform (Linux, macOS, Windows) to encourage non-Windows users.
Consider providing bash script examples where appropriate, especially for steps that involve scripting.
Add a note clarifying that PowerShell Core is cross-platform, but that Azure CLI is generally preferred for Linux environments.
Ensure that screenshots and UI instructions are not specific to Windows environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing App Service pricing details specifically for Windows (e.g., linking to 'app-service/windows/' in pricing), and does not provide any Linux-specific guidance or examples. There are no command-line or scripting examples (PowerShell, CLI, Bash), but the absence of Linux-specific information and the use of Windows-centric links indicate a lack of parity.

Recommendations:

Include links and references to both Windows and Linux App Service pricing details where appropriate.
Add explicit notes or sections clarifying any differences in scaling behavior or features between Windows and Linux App Service plans.
Provide examples or screenshots for both Windows and Linux App Service plans if the portal experience or options differ.
Ensure related documentation (e.g., scaling databases) also covers both Windows and Linux hosting scenarios where relevant.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section for clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is provided, with no mention of Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps that involve OS-level commands, include equivalent instructions for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo service nscd restart`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
Explicitly state that the instructions apply to all platforms, or provide platform-specific tabs or notes where relevant.
Review other troubleshooting or command-line sections to ensure parity for non-Windows users.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes a development environment that is compatible with .NET and Azure App Service, but it does not provide explicit Linux or cross-platform instructions. All terminal commands and deployment steps are generic (e.g., 'dotnet run', 'azd up'), which work on both Windows and Linux, but there are no Linux-specific examples or mentions of Linux tools. The workflow references GitHub Codespaces (which is Linux-based), but does not clarify this or provide parity guidance for local Linux development. There is no mention of PowerShell or Windows-only tools, but the lack of explicit Linux instructions or troubleshooting tips may create an implicit bias toward Windows users.

Recommendations:

Explicitly state that all commands work on both Windows and Linux, and clarify any OS-specific prerequisites.
Add a section or notes for users developing on local Linux or macOS environments, including any differences in setup or troubleshooting.
Provide example shell commands using bash/zsh where appropriate, especially for common Linux workflows (e.g., using curl to test endpoints).
Mention that GitHub Codespaces runs on Linux, and provide guidance for replicating the environment locally on Linux.
If referencing deployment or development tools, ensure both Windows and Linux equivalents are mentioned (e.g., Azure CLI usage in bash vs PowerShell).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page focuses exclusively on Azure Pipelines and the Azure portal, with all instructions and screenshots based on the web UI. There are no command-line examples, but the workflow implicitly assumes a Windows-centric environment by referencing Azure DevOps and omitting any mention of Linux, macOS, or cross-platform CLI alternatives. There are no references to Powershell or Windows-specific tools, but Linux users are not provided with parity guidance or examples. The only nod to alternatives is a link to a separate guide for GitHub Actions, which is not integrated into the main flow.

Recommendations:

Include explicit instructions or examples for configuring CI/CD pipelines using cross-platform tools such as the Azure CLI, Bash scripts, or YAML files that can be run on Linux or macOS agents.
Provide parity examples for Linux environments, such as how to trigger or manage load tests from a Linux shell or using platform-agnostic tools.
Mention and demonstrate how to use self-hosted Linux agents in Azure Pipelines for running load tests.
Integrate references to GitHub Actions and other CI/CD platforms more directly in the main flow, not just as a 'next steps' or separate guide.
Clarify that the instructions are platform-agnostic if that is the case, or explicitly state any platform dependencies.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation exclusively describes using the Azure portal (a web UI) for all actions, with no mention of command-line or scripting alternatives. There are no CLI, PowerShell, or Bash examples, and no references to Linux-native tools or workflows. This can disadvantage Linux users who often prefer or require CLI-based automation and scripting. The documentation implicitly assumes a GUI-first workflow, which is more common in Windows-centric environments.

Recommendations:

Add equivalent instructions for using the Azure CLI (az), which is cross-platform and commonly used on Linux.
Provide Bash shell script examples for automating test profile creation and load test execution.
Explicitly mention that all steps can be performed from any OS via the Azure portal, but highlight CLI alternatives for Linux users.
If PowerShell examples are added in the future, ensure Bash or Azure CLI equivalents are provided alongside.
Reference relevant documentation for using Azure Load Testing and Azure Functions from the command line, not just the portal.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents Azure PowerShell instructions before Azure CLI in all code tabbed sections, and references PowerShell-specific cmdlets (e.g., Get-AzProviderFeature) for status checks, even in the CLI sections. While Azure CLI is included, there is a subtle prioritization of Windows/PowerShell workflows, which may suggest a Windows-centric approach. No explicit Linux-only tools or examples are provided, and the CLI examples could be more clearly tailored for Linux environments.

Recommendations:

Alternate the order of PowerShell and CLI tabs, or present CLI first to balance platform representation.
In CLI sections, use CLI-native commands for all steps (e.g., use 'az feature show' instead of referencing PowerShell cmdlets for status checks).
Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Where possible, include screenshots or terminal output from Linux environments to reinforce cross-platform applicability.
Add a brief note or section highlighting parity between PowerShell and CLI, and direct Linux users to CLI as the preferred tool.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page does not provide any OS-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is primarily a Windows tool. There are no references to Linux tools, Bash, or cross-platform CLI usage, and no parity in example links or guidance for non-Windows users.

Recommendations:

Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
When referencing command-line configuration, provide both PowerShell and Bash/Azure CLI examples side-by-side.
Ensure that 'Next steps' and other guidance sections offer parity for Linux users, not just Windows/PowerShell users.
Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or the Azure portal, and provide links to those resources.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for all major platforms (Windows Command Prompt, PowerShell, macOS/Linux), but consistently lists Windows (cmd and PowerShell) before Linux/macOS. PowerShell and Windows command prompt commands are given equal or greater prominence than bash equivalents, and Windows-specific tools (setx) are mentioned. However, Linux/macOS instructions are present and not omitted.

Recommendations:

Alternate the order of platform instructions so that Linux/macOS examples are sometimes listed first, especially for Go, which is popular on Linux.
Group environment variable instructions by platform or provide tabs for each OS to avoid implicit prioritization.
Consider using cross-platform language in introductory text (e.g., 'On Linux, macOS, or Windows...') rather than always leading with Windows.
Where possible, avoid Windows-specific tools like 'setx' in favor of universally available commands, or clearly indicate their platform specificity.
Ensure parity in troubleshooting and advanced sections, if present, so Linux users are not left out.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both setx (cmd) and PowerShell commands, which may suggest a Windows-first perspective. However, Linux/macOS instructions are present and correct. There are no missing Linux examples, and no exclusive mention of Windows-only tools beyond environment variable setup.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabs or in a consistent order (e.g., Linux/macOS first, or alphabetical).
Consider using tabbed sections for OS-specific instructions to avoid implying priority.
Ensure that all CLI examples (such as az login) are clearly marked as cross-platform.
If possible, provide a single cross-platform command (e.g., using the Azure CLI or Go itself) for setting environment variables, or explain the differences succinctly.
Review future documentation for subtle ordering or emphasis that may suggest Windows is the primary or default platform.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on ASP.NET Core and C# in the context of Azure App Configuration and Key Vault, with all code and workflow examples tailored to .NET developers. There are no references to Linux-specific workflows, tools, or cross-platform command-line instructions. The instructions assume use of the Azure Portal and Visual Studio-style project structures, which are more common in Windows environments. No Linux shell, CLI, or cross-platform automation examples are provided.

Recommendations:

Include equivalent examples for Linux environments, such as using the Azure CLI or Bash scripts to automate certificate and secret management.
Provide guidance for developers using non-Windows platforms (e.g., how to set up and run the sample code on Linux or macOS).
Mention cross-platform development environments and editors (such as VS Code) and ensure instructions are not tied to Windows-specific tools.
Add notes or sections on how to perform App Configuration and Key Vault operations using command-line tools available on Linux.
Clarify that the instructions are applicable cross-platform, or explicitly provide parity for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally strives for cross-platform parity, but there is a subtle Windows bias in the ordering and presentation of examples. 'Windows' is often mentioned before Linux/macOS in tabbed instructions, and PowerShell is given a dedicated programming language pivot, which may not be as relevant for Linux users. However, Linux/macOS instructions are present and complete, and most commands are cross-platform.

Recommendations:

Alternate the order of platform tabs (e.g., sometimes list Linux/macOS before Windows) to avoid always privileging Windows.
Where possible, use neutral terms like 'terminal' instead of 'command prompt' unless specifically referring to Windows Cmd.
Clarify that PowerShell examples are primarily for Windows, and consider providing Bash equivalents for Linux users where PowerShell scripting is shown.
Ensure that all code snippets and instructions are validated on both Windows and Linux/macOS, and explicitly mention any platform-specific differences.
In sections where multiple platforms are supported, consider grouping instructions by task rather than by OS to reinforce parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation exhibits a mild 'windows_first' bias: in the Playwright (TypeScript) example, the 'os' setting is shown with 'ServiceOS.WINDOWS' in the code sample, even though the default is 'ServiceOS.LINUX'. Similarly, in the .NET/NUnit example, 'OSPlatform.Linux' is used, but both platforms are mentioned. There are no PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples, but Windows is sometimes presented first or as the example value.

Recommendations:

Ensure that code samples use the default (Linux) OS setting, or provide both Windows and Linux examples side by side.
When listing options, alternate which OS is presented first, or use alphabetical order.
Explicitly mention parity and support for both Windows and Linux in introductory sections.
If possible, add brief notes about any OS-specific considerations or limitations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is generally cross-platform, focusing on Visual Studio Code and Azure Functions, which are available on both Windows and Linux. However, there is a subtle Windows-first bias in the troubleshooting section, where a specific issue and solution for Windows users (regarding WSL Bash as the default terminal) is mentioned before any Linux-specific troubleshooting. There are no explicit PowerShell-heavy examples, exclusive use of Windows tools, or missing Linux examples, but the only OS-specific troubleshooting tip is for Windows.

Recommendations:

Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell environments, or dependencies on those platforms.
When mentioning Windows-specific issues (e.g., WSL Bash), provide equivalent guidance for Linux/macOS users, or clarify that the step is only relevant for Windows.
Explicitly state that all steps work on Windows, Linux, and macOS, and highlight any platform-specific differences where applicable.
Consider including a table or section summarizing any known OS-specific behaviors or requirements for full parity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric technologies) libraries and examples before those for Java, Python, JavaScript, and Go. There are no explicit PowerShell examples or Windows-only tools, but the ordering and emphasis on .NET frameworks may implicitly prioritize Windows development environments. There are no missing Linux examples, but the documentation could better highlight cross-platform parity.

Recommendations:

Reorder the 'Configuration Provider Libraries' table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than listing all .NET/Windows-centric libraries first.
Explicitly mention that all libraries are cross-platform where applicable, and provide sample links or notes for Linux/macOS usage if any differences exist.
Add a short section or note clarifying that Azure App Configuration providers are supported on both Windows and Linux, and that the .NET libraries work on .NET Core/.NET 5+ (which are cross-platform), not just on Windows.
If possible, provide at least one example or sample link that demonstrates usage on Linux (e.g., running a .NET Core app on Ubuntu, or a Java/Python/Go example on Linux).

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation presents environment variable setup instructions in the order of Windows CMD, PowerShell, and then macOS/Linux, which is a 'windows_first' bias. However, all platforms are ultimately covered, and there are no missing Linux examples or exclusive use of Windows tools.

Recommendations:

Present environment variable instructions for all platforms in parallel (e.g., a table or side-by-side code blocks) rather than listing Windows first.
Consider rotating the order of platform instructions or starting with the platform most likely used by the target audience (e.g., Linux for Python development).
Explicitly state that the instructions apply equally to all platforms to reinforce cross-platform parity.

Create pull request

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