CDN

50
Total Pages
35
Linux-Friendly Pages
15
Pages with Bias
30.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

91 issues found
Showing 51-75 of 91 flagged pages
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-map-content-to-custom-domain.md .../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and code samples for performing tasks using Azure PowerShell, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). The use of PowerShell as the only command-line automation example introduces a Windows-centric bias, potentially making it less accessible for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Where PowerShell is shown, provide a parallel tab or section for Bash/Azure CLI usage.
  • Clarify that PowerShell Core is cross-platform, but also mention and demonstrate Azure CLI as a first-class alternative.
  • Ensure that screenshots and portal instructions do not assume a Windows environment (e.g., avoid references to Windows-specific UI or terminology).
  • Review all automation and scripting sections to ensure Linux/macOS users have clear, tested guidance.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-overview.md ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only command-line management tool for Azure CDN endpoints, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or Bash. The 'Manage your content delivery network endpoints' section links exclusively to PowerShell documentation, and there are no Linux or cross-platform command-line examples or references. This may make it less accessible for Linux or macOS users.
Recommendations
  • Include Azure CLI examples and documentation links alongside PowerShell for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that management can be performed from Linux, macOS, and Windows, and provide parity in instructions and examples.
  • Where PowerShell is referenced, add equivalent Bash or shell command examples, or at least link to relevant Azure CLI documentation.
  • Review all 'Next steps' and 'Requirements' sections to ensure Linux users are not excluded or made to feel secondary.
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric tools (Fiddler, IIS) for troubleshooting and configuration. There are no Linux or macOS equivalents provided for inspecting HTTP headers or configuring compression on non-IIS origin servers. The examples and guidance focus on Windows environments, leaving Linux users without direct instructions or tool recommendations.
Recommendations
  • Include Linux/macOS alternatives to Fiddler, such as curl, wget, or command-line tools for inspecting HTTP headers.
  • Provide guidance for configuring compression on popular Linux web servers (e.g., Apache, Nginx) when dealing with proxy headers.
  • Add examples or links for troubleshooting on Linux/macOS platforms, ensuring parity in troubleshooting steps.
  • Mention cross-platform browser developer tools explicitly as available on all major operating systems.
GitHub Create Pull Request
CDN Get started with the Azure CDN Library for .NET ...s/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows, requiring Visual Studio 2015 and referencing Windows-specific UI and workflows. All examples assume use of Visual Studio and Windows, with no mention of Linux/macOS alternatives (e.g., VS Code, CLI, Mono). Package management instructions use the Package Manager Console (PowerShell-based), and the 'Next Steps' section highlights PowerShell for further management, with no Linux or cross-platform equivalents provided.
Recommendations
  • Add instructions for setting up and running the .NET application on Linux/macOS, including using VS Code or the 'dotnet' CLI.
  • Provide NuGet package installation examples using the 'dotnet add package' CLI command, which works cross-platform.
  • Include screenshots or guidance for non-Windows environments, or clarify that the steps can be adapted for other platforms.
  • Mention and link to cross-platform management tools (e.g., Azure CLI) in the 'Next Steps' section.
  • Clarify that .NET Core/.NET 5+ can be used, and update references to Visual Studio 2015 to include VS Code or JetBrains Rider.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line automation examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI or Bash alternatives that are cross-platform and preferred by many Linux/macOS users. The only graphical tool recommended for accessing Azure Storage is Microsoft Azure Storage Explorer, a Windows-centric application, with no mention of Linux-native or web-based alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI and Bash examples for enabling and configuring diagnostic logs, alongside PowerShell.
  • Mention and provide instructions for using cross-platform or Linux-native tools to access Azure Storage, such as the Azure CLI, azcopy, or web-based Azure Portal.
  • Reorder examples so that cross-platform solutions (CLI, REST API) are presented before or alongside Windows-specific tools.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI or REST API, and provide links to relevant documentation.
  • Include troubleshooting notes for Linux/macOS users where tool availability or behavior may differ.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides step-by-step instructions for adding and removing custom domains to Azure CDN endpoints using the Azure portal and Azure PowerShell. While the Azure portal is cross-platform, the only CLI/script examples given are for Azure PowerShell, which is primarily associated with Windows environments. There are no examples using Azure CLI, Bash, or other Linux/macOS-native tools. This creates friction for Linux/macOS users who may prefer or require non-PowerShell command-line solutions.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands (e.g., az cdn custom-domain create, az cdn custom-domain delete).
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide Bash/Azure CLI examples for Linux/macOS users.
  • Where scripting is shown, offer both PowerShell and Bash/CLI tabs or sections.
  • Clarify any platform-specific requirements or limitations for the tools used.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page references PowerShell as a primary management tool for Azure CDN endpoints and lists it before mentioning other automation options. There is no mention of Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform scripting), nor are there examples or guidance for non-Windows users. This creates a subtle but notable Windows bias, especially in the 'Next steps' section where PowerShell is highlighted for management tasks.
Recommendations
  • Add instructions and examples for managing Azure CDN endpoints using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the Azure portal and Azure CLI are available on all major operating systems.
  • Provide parity in automation examples, such as Bash scripts or references to REST API usage.
  • Reorder examples so that cross-platform tools (Azure CLI, portal) are listed before or alongside PowerShell.
  • Include a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed configuration steps and code samples exclusively using Azure PowerShell, which is most commonly used on Windows. There are no equivalent examples for Azure CLI, Bash, or other cross-platform tools. The PowerShell instructions are presented before any mention of alternative methods, and no Linux/macOS-specific guidance is offered. This creates friction for users on non-Windows platforms who may prefer or require CLI/Bash-based workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, with clear instructions for Linux/macOS users.
  • Include Bash script samples for diagnostic settings configuration.
  • Explicitly state cross-platform options and link to Azure CLI documentation.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Clarify that PowerShell Core is available on Linux/macOS, but recommend CLI for native experience.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions and examples for enabling and consuming Azure CDN diagnostic logs using the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or Bash scripting). The only automation examples are PowerShell-based, and the recommended tool for browsing storage is Microsoft Azure Storage Explorer, a GUI application primarily associated with Windows. No Linux-native or cross-platform alternatives are suggested, and PowerShell is presented as the sole scripting option for automation.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or Python sample scripts for downloading and processing logs from Azure Storage.
  • Mention and provide instructions for using cross-platform tools (e.g., azcopy, Azure CLI storage commands, or Python SDKs) to access and download blobs.
  • List open-source or Linux-native tools for browsing Azure Storage, such as using the Azure CLI or third-party file browsers.
  • Ensure that scripting and automation sections present both PowerShell and CLI/Bash options, or at least reference them.
  • When recommending tools, clarify their cross-platform support and suggest alternatives if a tool is Windows-centric.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell as a management tool for Azure CDN endpoints and lists it before mentioning other automation options. There are no explicit Linux/macOS CLI examples or mentions of cross-platform tools like Azure CLI or Bash. This creates a subtle Windows bias, as PowerShell is most commonly associated with Windows environments, and its mention before alternatives may suggest a Windows-first approach.
Recommendations
  • Add explicit instructions and examples for managing Azure CDN endpoints using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Mention Bash or shell scripting options for automation alongside PowerShell and .NET/Node.js.
  • Clarify that PowerShell Core is available cross-platform, or provide links to documentation for using PowerShell on Linux/macOS.
  • Ensure that all management and automation options are presented in a platform-neutral order, or grouped by platform.
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by recommending Windows-specific tools (Fiddler) for inspecting HTTP headers and providing IIS-only instructions for server-side compression configuration. No Linux or cross-platform alternatives (such as curl, wget, or Apache/Nginx configuration) are mentioned, and Windows solutions are presented first and exclusively.
Recommendations
  • Include Linux/macOS-friendly tools for inspecting HTTP headers, such as curl, wget, or httpie, with example commands.
  • Mention cross-platform browser developer tools explicitly, and clarify that Fiddler is Windows-only.
  • Provide guidance for configuring compression on popular Linux web servers (e.g., Apache, Nginx), including handling the Via header.
  • Structure troubleshooting steps to present platform-neutral solutions first, or offer parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for adding and removing custom domains to Azure CDN endpoints using the Azure portal and Azure PowerShell. However, it lacks equivalent CLI examples for Linux/macOS users (e.g., Azure CLI or Bash), and only PowerShell is presented as the automation/script option. This creates friction for users on non-Windows platforms who may not use PowerShell.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all automation/script steps (e.g., az cdn custom-domain create, az cdn custom-domain delete).
  • Explicitly mention that PowerShell commands can be run cross-platform, but provide Bash/CLI alternatives for Linux/macOS users.
  • Ensure that all code samples and instructions are available for both Windows and Linux/macOS environments.
  • Consider adding a note or tab for Bash scripting or Azure CLI in relevant sections.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed Azure PowerShell examples for configuring CDN raw logs and metrics, but does not include equivalent Azure CLI, Bash, or Linux/macOS shell instructions. All command-line automation is shown using PowerShell, which is primarily a Windows tool, and there is no mention of Linux/macOS-specific workflows or tools. This creates friction for users on non-Windows platforms who may prefer or require Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, with clear variable usage and output expectations.
  • Explicitly mention that Azure CLI is cross-platform and provide links to CLI documentation.
  • Where possible, show both PowerShell and CLI/Bash examples side-by-side, or indicate which steps are platform-agnostic.
  • Clarify any platform requirements for tools (e.g., PowerShell Core on Linux/macOS, or recommend Azure CLI for those platforms).
GitHub Create Pull Request
CDN Quickstart - Create an Azure Content Delivery Network profile and endpoint ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by omitting Linux-friendly CLI instructions (such as Azure CLI or Bash). There are no examples or references to Linux-specific workflows, and no parity for users who prefer or require command-line automation, which is common in Linux environments.
Recommendations
  • Add Azure CLI examples for all major steps (creating CDN profile, endpoint, and resource cleanup), with sample commands that work on Linux, macOS, and Windows.
  • Explicitly mention that the Azure CLI can be used from any platform and provide links to installation instructions for Linux.
  • Where possible, provide Bash script snippets for automation, and clarify cross-platform compatibility.
  • Ensure that any references to deleting resources or managing them include both portal and CLI options.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Visual Studio Code is mentioned as the preferred editor, and the only debugger setup example is for VS Code (which is most popular on Windows, though cross-platform). The 'Next Steps' section highlights PowerShell for further CDN management, with no mention of Linux-native tools (such as Bash, CLI, or shell scripting). No explicit Linux examples or references to Linux-specific workflows are provided.
Recommendations
  • Include examples of running the Node.js application from Linux/macOS terminals, such as Bash or zsh.
  • Mention and provide guidance for using other editors and debuggers common on Linux (e.g., Vim, Emacs, JetBrains IDEs).
  • Add instructions for passing command-line arguments in debuggers/editors on Linux/macOS.
  • In the 'Next Steps' section, provide links to Azure CLI or Bash scripting documentation for CDN management, alongside PowerShell.
  • Clarify that all steps are cross-platform and explicitly state compatibility with Linux/macOS environments.
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and Portal. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion as a primary method (with full example) may indicate a mild Windows bias. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The order of examples (CLI, then PowerShell, then Portal) is reasonable, but the PowerShell example could be perceived as Windows-centric, especially since no bash-specific guidance is given.
Recommendations
  • Add explicit bash shell examples for Linux users, demonstrating equivalent commands and environment setup.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary notes about platform differences.
  • If PowerShell is included, consider mentioning PowerShell Core (cross-platform) or clarifying its usage on Linux/macOS.
  • Review the documentation for any assumptions about the user's operating system and ensure parity for Linux users in instructions and troubleshooting.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is presented as a primary tab alongside CLI, suggesting parity. However, there is a subtle Windows bias: PowerShell is a Windows-centric tool, and its inclusion as a top-level tab (rather than, for example, Bash or Linux shell) may imply preference for Windows users. No explicit Linux shell or Bash examples are given, and the CLI examples use variable assignment syntax compatible with Bash but do not clarify Linux usage. There are no references to Linux-specific tools or workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for verification steps, clarifying compatibility with Linux environments.
  • Include notes or tabs for Mac/Linux users, specifying any differences in command syntax or environment setup.
  • Consider reordering tabs so that Azure CLI (cross-platform) appears first, or add Bash as a separate tab to emphasize Linux parity.
  • Mention that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for all platforms.
  • If PowerShell is included, clarify that PowerShell Core is cross-platform, or provide examples using native Linux tools where appropriate.
GitHub Create Pull Request
CDN Quickstart - Create an Azure Content Delivery Network profile and endpoint ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. There is no mention of platform-specific tools, but the absence of CLI instructions (such as Azure CLI or Bash) means Linux users are not given parity with Windows users, who may be more accustomed to GUI workflows. The documentation does not reference PowerShell or Windows-only tools, but it implicitly favors Windows by not providing Linux-friendly alternatives or examples.
Recommendations
  • Add Azure CLI examples for creating CDN profiles and endpoints, which can be run on Linux, macOS, and Windows.
  • Include Bash shell commands where appropriate to demonstrate cross-platform workflows.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity by showing how to accomplish the same tasks using CLI tools.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are also provided.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is given equal prominence to Azure CLI, which is typically used on Windows. There is no explicit mention of Linux-specific shell usage (e.g., bash), nor are there examples tailored to Linux environments. The variable assignment syntax in the PowerShell section uses Windows-style conventions, and there is no mention of Linux tools or patterns.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, showing variable assignment and command usage in a Linux context.
  • Clarify that Azure CLI commands work cross-platform, and provide examples of running them in bash or zsh.
  • If PowerShell is included, note its cross-platform availability, but avoid assuming Windows as the default environment.
  • Consider including a section or tab for Linux/macOS users, highlighting any differences or tips for those platforms.
  • Review variable assignment syntax to ensure it matches the conventions of the shell being used (e.g., $var=value for bash, $var = value for PowerShell).
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and Portal. While Azure CLI is cross-platform, PowerShell examples are given equal prominence, and there is no explicit mention of Linux-specific shell usage (e.g., Bash) or guidance for Linux users. The PowerShell section assumes familiarity with Windows tooling and does not clarify cross-platform compatibility. The ordering of examples (CLI, then PowerShell, then Portal) is common, but the PowerShell example may reinforce a Windows-centric approach for users unfamiliar with its Linux support.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes if needed.
  • Clarify that PowerShell Core is available cross-platform, or provide a Bash shell example alongside PowerShell.
  • Add a note or section for Linux users, confirming that all steps can be performed on Linux and referencing any platform-specific prerequisites (e.g., installation of Azure CLI on Linux).
  • Consider reordering or labeling examples to highlight cross-platform compatibility, reducing the implicit Windows-first impression.
GitHub Create Pull Request
CDN Quickstart - Create an Azure Content Delivery Network profile and endpoint ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows tools like PowerShell, it implicitly favors Windows users by omitting CLI instructions (such as Azure CLI or Bash), which are commonly used on Linux and macOS. There are no Linux-specific patterns, tools, or examples, nor is there mention of cross-platform command-line alternatives.
Recommendations
  • Add Azure CLI examples for creating CDN profiles and endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell commands where appropriate, especially for resource cleanup and automation.
  • Explicitly mention that all steps can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Ensure parity by presenting CLI instructions alongside portal steps, or at least referencing them.
  • Consider adding a section comparing portal vs. CLI workflows for users on different platforms.
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Bicep ...lob/main/articles/cdn/create-profile-endpoint-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is given equal prominence as CLI, despite being primarily a Windows tool, and is presented as a first-class option throughout. There are no Linux-specific shell examples (e.g., Bash), nor is there any mention of platform differences or guidance for Linux users. The use of PowerShell may implicitly favor Windows users, as PowerShell is not natively available on most Linux distributions.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
  • Consider providing Bash shell examples or explicitly noting that CLI commands work in Bash and other Linux shells.
  • Add a note or section for Linux/macOS users, including installation instructions for Azure CLI and PowerShell Core if needed.
  • If PowerShell examples are included, specify that PowerShell Core is available for Linux/macOS, or link to installation guides.
  • Ensure that CLI examples are presented first, as they are more universally applicable across platforms.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is presented as a primary tab alongside Azure CLI, which may indicate a Windows-first approach. There are no explicit Linux shell examples (e.g., bash), and the use of PowerShell commands may be less relevant for Linux users. The documentation does not mention Linux-specific patterns or tools, nor does it clarify cross-platform compatibility for the commands shown.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, showing how to use Azure CLI in a bash environment.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
  • Consider listing Azure CLI (bash) examples before PowerShell to avoid Windows-first bias.
  • Mention installation and usage of Azure CLI on Linux in the prerequisites section.
  • Ensure that all code snippets use cross-platform compatible syntax where possible, or provide alternatives for different platforms.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-create-new-endpoint.md ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web interface) for all instructions and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by not mentioning or demonstrating Azure CLI or Bash commands, which are more common on Linux and cross-platform environments. There are no Linux-specific instructions or parity for command-line usage.
Recommendations
  • Add equivalent steps using Azure CLI commands, which work on both Windows and Linux.
  • Include Bash shell examples for creating CDN profiles and endpoints.
  • Explicitly mention that the Azure portal is cross-platform, but provide links or sections for command-line alternatives.
  • Ensure that resource cleanup instructions include CLI commands (e.g., az group delete) as well as portal steps.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a subtle Windows bias: Visual Studio Code is recommended as the editor, and the only debugger setup example given is for Visual Studio Code (a Microsoft product popular on Windows). The 'Next Steps' section explicitly links to PowerShell documentation for CDN management, with no mention of Linux-native tools or CLI alternatives. There are no explicit Linux examples or references to Linux-specific editors, shells, or patterns, and PowerShell is mentioned as the next step for resource management, reinforcing a Windows-centric approach.
Recommendations
  • Include examples and instructions for running the Node.js application on Linux and macOS terminals, such as bash/zsh.
  • Mention alternative editors (e.g., Vim, Emacs, Sublime Text, Atom) alongside Visual Studio Code.
  • Provide debugger setup examples for non-Windows environments (e.g., using node CLI, VS Code on Linux/macOS, or other editors).
  • In the 'Next Steps' section, link to Azure CLI documentation for CDN management, and mention Bash scripting as an alternative to PowerShell.
  • Ensure screenshots and instructions are platform-neutral or include both Windows and Linux/macOS variants where relevant.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →