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 1-25 of 91 flagged pages
CDN Get started with the Azure CDN Library for .NET ...s/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows users, requiring Visual Studio 2015 and referencing Windows-specific UI steps and screenshots. All examples and instructions assume use of Windows tools (Visual Studio, NuGet Package Manager Console, PowerShell), with no mention of Linux/macOS alternatives (e.g., VS Code, CLI, dotnet CLI, or cross-platform editors). Linux users are left without guidance for setting up or running the sample, and PowerShell is suggested for further management tasks without Bash or CLI equivalents.
Recommendations
  • Include instructions for using cross-platform tools such as Visual Studio Code or JetBrains Rider.
  • Provide alternative setup steps using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Add screenshots and guidance for Linux/macOS environments.
  • Mention and link to Azure CLI or Bash scripts for CDN management alongside PowerShell.
  • Clarify that the .NET SDK and Azure CDN libraries are cross-platform and provide explicit Linux/macOS support notes.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary CLI management tool for Azure CDN endpoints, without mentioning Linux-friendly alternatives such as Azure CLI or Bash. The 'Next steps' section lists PowerShell before other automation options and omits explicit Linux or cross-platform command-line examples, which may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Include Azure CLI examples alongside PowerShell for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that management tasks can be performed from Linux, macOS, and Windows, and provide links to relevant documentation for each platform.
  • Add Bash script examples or references for common CDN management tasks.
  • Reorder or parallelize tool mentions so that PowerShell and Azure CLI are presented together, rather than PowerShell first.
  • Clarify that the Azure portal is accessible from any OS with a web browser.
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
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows development environments. It exclusively references Visual Studio 2015 for project creation and management, assumes use of Windows-specific UI elements and workflows, and provides no guidance or examples for Linux or cross-platform development. The only alternative tool mentioned is PowerShell, which is primarily a Windows technology, and there are no references to Linux equivalents (e.g., VS Code, CLI, or cross-platform .NET workflows). There are no instructions for running the sample on Linux or macOS, nor any mention of .NET Core/SDK usage outside Visual Studio.
Recommendations
  • Add instructions for creating and running the .NET project using the .NET CLI (dotnet new, dotnet run), which works on Linux, macOS, and Windows.
  • Include examples for using VS Code or other cross-platform editors instead of only Visual Studio.
  • Provide guidance for installing required NuGet packages via the CLI (dotnet add package) as an alternative to the Visual Studio UI.
  • Mention how to run the sample on Linux and macOS, including any platform-specific considerations.
  • Reference Azure CLI or REST API alternatives for CDN management, alongside PowerShell.
  • Clarify that the code is compatible with .NET Core/.NET 5+ and not just .NET Framework, if applicable.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias through exclusive use of PowerShell for CLI examples, reliance on Microsoft Azure Storage Explorer (a Windows-centric GUI tool), and lack of Linux or cross-platform command-line alternatives. There are no Bash, Azure CLI, or Linux-native instructions for enabling or consuming diagnostic logs. The ordering also presents Windows/PowerShell methods before mentioning any other automation or scripting options.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logs, which are cross-platform and work natively on Linux and macOS.
  • Include Bash or Python sample scripts for downloading and processing logs from Azure Storage, in addition to the PowerShell examples.
  • Mention and provide instructions for using cross-platform tools such as azcopy or the Azure CLI storage commands to access blobs, instead of only referencing Microsoft Azure Storage Explorer.
  • Clearly indicate which tools and scripts are cross-platform, and provide parity in documentation for Linux users.
  • Reorder sections so that cross-platform or platform-neutral options (Azure CLI, REST API) are presented before or alongside PowerShell and Windows GUI tools.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for using the Azure portal and Azure PowerShell to manage custom domains for Azure CDN endpoints. PowerShell examples are given for both adding and removing custom domains, but there are no equivalent examples for Linux-native tools (such as Azure CLI or Bash scripts). The use of PowerShell as the only command-line automation option reflects a Windows bias, and there is no mention of Linux-specific workflows or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, including adding and removing custom domains.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash script samples where appropriate.
  • Ensure that command-line instructions are not limited to Windows tools; include Linux and macOS parity in all automation sections.
  • Where PowerShell is referenced, clarify that it is available on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider adding a section or tab for 'Azure CLI' alongside 'Azure PowerShell' and 'Azure portal' in all relevant steps.
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority View Details →
Scanned: 2026-01-12 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 primarily referencing Windows-centric tools (Fiddler, IIS), providing troubleshooting steps only for Microsoft IIS web servers, and omitting equivalent Linux/Apache/Nginx examples or guidance. No Linux-specific tools or server configuration instructions are given, and Windows solutions are presented first and exclusively.
Recommendations
  • Include troubleshooting steps for popular Linux web servers such as Apache and Nginx, detailing how to handle compression and proxy headers.
  • Mention Linux-compatible tools (e.g., curl, wget, tcpdump, Wireshark) for inspecting HTTP headers and compression.
  • Provide configuration examples for enabling compression and handling proxy headers on Linux servers.
  • Present Windows and Linux solutions side-by-side or in parallel sections to ensure parity and avoid platform-first bias.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a strong Windows bias in its configuration and automation sections. All command-line examples are provided exclusively using Azure PowerShell, a tool most commonly used on Windows and not natively available on Linux. There are no examples using Azure CLI, Bash, or other Linux-native tools. The documentation refers to the Azure portal and PowerShell before mentioning any cross-platform alternatives, and does not provide Linux-specific guidance or parity in automation examples.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash scripting examples for automation tasks, especially for enabling diagnostics and configuring log destinations.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, or provide installation instructions for non-Windows platforms.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Add notes or links to documentation for Linux users, including troubleshooting and environment setup guidance.
  • Ensure screenshots and UI instructions do not assume a Windows environment (e.g., avoid references to Windows-specific UI elements or terminology).
GitHub Create Pull Request
CDN About Azure CDN from Microsoft (classic) to Azure Front Door migration ...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Dev-ops' section, where it mentions updating 'Azure PowerShell module' before CLI commands and APIs, suggesting a Windows-first approach. There are no examples or instructions for Linux-specific tools, shell scripts, or cross-platform automation. The page does not provide parity for Linux users in terms of migration scripting or tool usage.
Recommendations
  • Explicitly mention Azure CLI and REST API as cross-platform alternatives alongside PowerShell.
  • Provide example migration scripts for both PowerShell (Windows) and Bash (Linux/macOS) environments.
  • Clarify that all migration steps can be performed using Azure CLI on Linux/macOS, not just PowerShell on Windows.
  • Include links to documentation for Azure CLI and REST API usage in migration scenarios.
  • Avoid listing PowerShell before CLI in instructions to prevent implicit Windows-first bias.
GitHub Create Pull Request
CDN About Azure CDN from Microsoft (classic) to Azure Front Door migration ...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the 'Dev-ops' section, where it references updating Azure PowerShell modules before mentioning CLI commands and APIs. There are no Linux-specific examples, nor is Bash or cross-platform scripting discussed. The page does not provide parity in tooling guidance for Linux users, and the ordering of tools suggests a Windows-first approach.
Recommendations
  • Explicitly mention and provide examples for Azure CLI (cross-platform) alongside or before PowerShell.
  • Include Bash scripting examples for migration automation.
  • Clarify that both PowerShell and CLI are supported on Windows, Linux, and macOS.
  • Add links to documentation for Azure CLI and Bash usage in migration scenarios.
  • Avoid listing Windows-specific tools (e.g., PowerShell) before cross-platform alternatives unless contextually necessary.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias by exclusively referencing Windows development tools (Visual Studio), providing only Windows-centric instructions for project creation, and omitting any mention of Linux-compatible development environments or workflows. All examples and screenshots are based on Visual Studio for Windows, and there are no alternatives or parity for Linux users. The 'Next Steps' section further reinforces this bias by suggesting PowerShell (primarily a Windows tool) for CDN management, without mentioning cross-platform or Linux-native options.
Recommendations
  • Add instructions for setting up and running .NET console applications using cross-platform tools such as Visual Studio Code, JetBrains Rider, or the .NET CLI on Linux and macOS.
  • Include example commands for creating and managing projects using the .NET CLI (e.g., 'dotnet new console') instead of only Visual Studio GUI steps.
  • Provide screenshots or terminal output examples from Linux environments to illustrate parity.
  • Mention and link to Linux-compatible package managers (e.g., 'dotnet add package') for NuGet dependencies.
  • In the 'Next Steps' section, reference cross-platform management options such as Azure CLI or REST API, and provide links or examples for those tools.
  • Explicitly state that the Azure CDN .NET library and management tasks can be performed on Linux and macOS, not just Windows.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias. Visual Studio Code is recommended as the editor, and the only debugger setup example is for VS Code (a Microsoft product popular on Windows, though cross-platform). The 'Running the program' section provides tips specifically for VS Code, with no mention of Linux-native editors or debugging tools. The 'Next Steps' section links to PowerShell management documentation, but does not mention Linux CLI or Bash alternatives. There are no explicit Linux-specific instructions or examples, and Windows tools are referenced before any Linux equivalents.
Recommendations
  • Include examples for running and debugging the Node.js application using Linux-native editors (e.g., Vim, Emacs, GNOME Builder) and debugging tools (e.g., node-inspect, CLI debugging).
  • Add instructions for passing command-line parameters when running the script from Bash or other Linux shells.
  • Provide links to Azure CLI documentation for CDN management alongside the PowerShell link, and mention Bash scripting alternatives.
  • Explicitly state that the instructions and tools are cross-platform, and highlight any platform-specific considerations (such as file paths or environment setup).
  • Show screenshots or terminal output from Linux environments in addition to Windows/VS Code.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively providing PowerShell examples for enabling diagnostic logs, referencing Microsoft Azure Storage Explorer (a Windows-centric GUI tool) for log consumption, and omitting any Linux or cross-platform CLI (e.g., Azure CLI, Bash) instructions. There are no examples or guidance for Linux users or those preferring command-line tools available on non-Windows platforms. Windows tools and patterns are mentioned first and exclusively, with no parity for Linux equivalents.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell instructions, showing how to enable diagnostic logs via command-line on Linux/macOS.
  • Include instructions for using cross-platform tools (e.g., azcopy, Azure CLI, REST API) to access and download logs from Azure Storage, alongside or instead of Microsoft Azure Storage Explorer.
  • Provide sample Bash scripts or Python code for exporting and processing diagnostic logs, ensuring Linux users have clear, actionable guidance.
  • Explicitly mention platform compatibility for all tools and scripts, and recommend cross-platform alternatives where available.
  • Structure examples so that Windows and Linux approaches are presented with equal prominence, or group them by platform for clarity.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for using the Azure portal (GUI) and Azure PowerShell to manage custom domains for Azure CDN endpoints. PowerShell examples are given for both adding and removing custom domains, but there are no equivalent examples for Linux-friendly tools such as Azure CLI or Bash scripts. The use of PowerShell, which is traditionally a Windows-centric tool (despite cross-platform support), and the absence of Azure CLI or shell-based instructions, indicates a bias towards Windows environments and tooling.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including adding and removing custom domains.
  • Include Bash script snippets for common tasks, where appropriate.
  • Explicitly mention cross-platform compatibility for all command-line tools used.
  • Provide guidance for Linux/macOS users, such as installation links for Azure CLI and notes on using the portal from non-Windows systems.
  • Ensure that examples and screenshots do not assume a Windows-only environment.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by mentioning PowerShell as the only command-line management option for Azure CDN endpoints, without referencing Azure CLI or Bash alternatives. The 'Manage your content delivery network endpoints' section lists the Azure portal and PowerShell, omitting Linux-friendly tools. No Linux-specific examples, tools, or workflows are provided, and Windows-centric patterns (PowerShell) are mentioned before any cross-platform or Linux-native equivalents.
Recommendations
  • Include Azure CLI examples for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Mention Bash scripting or Linux shell options alongside PowerShell for automation tasks.
  • Ensure that management instructions reference both Windows and Linux tools, ideally presenting cross-platform options first.
  • Add explicit Linux usage scenarios or links to Linux-specific documentation where relevant.
  • Review all referenced tutorials and modules to confirm Linux parity in examples and tooling.
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority View Details →
Scanned: 2026-01-11 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 exclusively referencing Windows tools (Fiddler, IIS) for troubleshooting and configuration, without mentioning Linux equivalents or providing Linux-specific guidance. The examples and configuration steps are focused on Microsoft IIS, with no discussion of Apache, Nginx, or other common Linux web servers.
Recommendations
  • Include Linux-based troubleshooting tools such as curl, wget, or command-line examples for checking HTTP headers.
  • Provide guidance for configuring compression on popular Linux web servers (e.g., Apache, Nginx), including how to handle proxy headers and compression settings.
  • Mention cross-platform tools (e.g., Wireshark, browser dev tools) and ensure examples are not limited to Windows-only solutions.
  • Add links to official documentation for Linux web servers regarding compression and proxy header handling.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for configuring diagnostics and logging, with no equivalent examples for Azure CLI, Bash, or Linux-native tools. The use of PowerShell commands and references to Windows-centric tooling occurs before any mention of cross-platform alternatives. There is no guidance for Linux users or those working in Bash or with Azure CLI, and the documentation assumes familiarity with PowerShell and Windows workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sections, showing how to perform the same configuration tasks in Bash or on Linux/macOS.
  • Include notes or sections highlighting cross-platform compatibility and how Linux/macOS users can achieve the same results.
  • Reference both PowerShell and CLI documentation equally, and avoid assuming PowerShell as the default automation tool.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is cross-platform, and provide CLI alternatives for automation.
  • Consider reordering examples so that CLI and PowerShell are presented together, or alternate which is shown first, to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and cleaning up resources, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and no Linux-specific shell examples (such as Bash) are provided. The use of PowerShell and references to PowerShell cmdlets may be less familiar or accessible to Linux users. There is no explicit mention of Linux environments or tools, and no guidance for Linux users beyond the Azure CLI.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend Bash or other shells for Linux users.
  • Add explicit Bash shell examples for Linux users, showing variable assignment and command usage in Bash syntax.
  • De-emphasize PowerShell as a primary method, or move PowerShell examples after CLI/Bash examples to avoid Windows-first impression.
  • Mention installation and usage of Azure CLI on Linux, and provide links to relevant documentation.
  • Where possible, avoid Windows-specific terminology or tools unless necessary, and always provide Linux equivalents.
GitHub Create Pull Request
CDN About Azure CDN from Microsoft (classic) to Azure Front Door migration ...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Dev-ops' section, where it mentions updating Azure PowerShell modules before CLI commands and APIs, suggesting a Windows-first approach. There are no Linux-specific examples, nor is Bash or shell scripting referenced. The page does not mention Linux tools or provide parity in migration instructions for Linux users.
Recommendations
  • Explicitly mention Azure CLI and REST API usage alongside PowerShell, and provide examples for both Windows (PowerShell) and Linux/macOS (Bash/CLI).
  • Add a section or note for Linux users, outlining any platform-specific considerations or migration steps.
  • Ensure that all command-line instructions are cross-platform, or provide alternatives for both PowerShell and Bash.
  • Avoid listing Windows tools or patterns before their Linux equivalents unless there is a technical reason; strive for equal prominence.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias: Visual Studio Code is mentioned as the editor of choice, and the only debugger setup guidance is for Visual Studio Code (a Microsoft tool popular on Windows). The 'Running the program' section provides tips for Visual Studio Code specifically, with no mention of Linux-native editors or debugging tools. The 'Next Steps' section links to PowerShell documentation for CDN management, but does not mention Linux CLI equivalents or Bash scripting. There are no explicit Linux examples, nor are Linux tools or patterns discussed.
Recommendations
  • Add explicit instructions for running and debugging the Node.js application on Linux and macOS, including examples using editors like Vim, Emacs, or JetBrains WebStorm.
  • Provide guidance for passing command-line parameters when running the script from Bash or other Linux shells.
  • Include links to Azure CLI documentation for CDN management alongside the PowerShell link.
  • Mention cross-platform editors and tools in addition to Visual Studio Code.
  • Ensure screenshots and examples are not Windows-specific, or provide Linux/macOS equivalents.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments. It exclusively references Visual Studio (Windows-only), uses Windows terminology and screenshots, and provides instructions based on Windows tools (NuGet Package Manager Console, Visual Studio UI). There are no Linux or cross-platform alternatives mentioned for project setup, package management, or running the application. The 'Next Steps' section also highlights PowerShell, another Windows-centric tool, without mentioning Bash, CLI, or Linux equivalents.
Recommendations
  • Add instructions for creating and running the .NET application using cross-platform tools such as Visual Studio Code, JetBrains Rider, or the 'dotnet' CLI.
  • Include Linux/macOS-specific steps for project creation, package installation (e.g., 'dotnet new console', 'dotnet add package'), and running the application.
  • Replace or supplement Visual Studio screenshots with cross-platform alternatives.
  • Mention and provide examples for managing CDN resources using Azure CLI or Bash scripts, not just PowerShell.
  • Clarify that the .NET SDK and Azure CDN libraries are cross-platform and can be used outside of Windows.
  • Ensure parity in troubleshooting and environment setup guidance for Linux/macOS users.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias in several ways: all command-line examples for enabling diagnostic logs use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. The only graphical tool referenced for accessing logs is Microsoft Azure Storage Explorer, a Windows-centric application. There are no Linux-specific instructions, examples, or tool recommendations. The order of presentation also places PowerShell and Windows tools before any cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, with explicit Bash syntax and Linux usage notes.
  • Include instructions for accessing and downloading logs using Linux-native tools (e.g., azcopy, curl, jq, or Azure CLI's storage commands).
  • Mention and provide examples for open-source or cross-platform storage explorers (e.g., using azcopy or third-party tools) alongside Microsoft Azure Storage Explorer.
  • Ensure that cross-platform and Linux-compatible methods are presented either before or alongside Windows/PowerShell methods, not only after.
  • Clarify in tool recommendations which options are available for Linux, macOS, and Windows, and provide installation instructions for each.
GitHub Create Pull Request
CDN Tutorial: Add a custom domain to your endpoint .../main/articles/cdn/cdn-map-content-to-custom-domain.md
High Priority View Details →
Scanned: 2026-01-10 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. PowerShell is featured as the only CLI example, with no mention of cross-platform or Linux-native tools (such as Azure CLI, Bash, or shell scripts). This creates a bias toward Windows users, as PowerShell is primarily associated with Windows environments, and Linux users may prefer or require Azure CLI or Bash-based instructions. The documentation does not offer equivalent Linux-friendly command-line examples or note PowerShell Core's cross-platform capabilities.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., az cdn custom-domain create, az cdn custom-domain delete).
  • Explicitly mention that PowerShell Core is cross-platform, or provide installation links for Linux/Mac users.
  • Include Bash or shell script snippets where appropriate, especially for DNS record management or verification steps.
  • Ensure that instructions and screenshots do not assume a Windows-only environment (e.g., avoid referencing Windows-specific UI elements or terminology).
  • Add a note or section for Linux/Mac users, outlining recommended tools and approaches for each step.
GitHub Create Pull Request
CDN What is a content delivery network? - Azure ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where management of Azure CDN endpoints is described as possible via the Azure portal or PowerShell, with no mention of Linux-native tools or CLI alternatives. PowerShell is a Windows-centric tool, and its exclusive mention suggests a preference for Windows environments. There are no examples or guidance for Linux users (e.g., Azure CLI, Bash scripts), nor is there parity in tool recommendations. The documentation also lists .NET (Windows-preferred) before Node.js in automation examples.
Recommendations
  • Include Azure CLI examples for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Mention Bash scripting or other Linux-native automation options alongside PowerShell.
  • Provide explicit instructions or links for Linux/macOS users to manage Azure CDN resources.
  • List cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Ensure automation examples are balanced between Windows (.NET, PowerShell) and Linux-friendly options (Node.js, Python, Bash).
GitHub Create Pull Request
CDN Troubleshooting file compression in Azure Content Delivery Network ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively referencing Windows-centric tools (Fiddler, IIS) for troubleshooting and configuration. There are no Linux or cross-platform equivalents mentioned for inspecting HTTP headers or configuring compression at the origin server. The troubleshooting steps and examples prioritize Windows environments, leaving out guidance for users running Linux-based origins or using Linux tools.
Recommendations
  • Include Linux-friendly tools for inspecting HTTP headers, such as curl, wget, or command-line examples using these tools.
  • Provide guidance for configuring compression on popular Linux web servers (e.g., Apache, Nginx), including how to handle proxy headers and compression settings.
  • Mention cross-platform alternatives to Fiddler, such as Wireshark or browser extensions, and clarify which steps apply regardless of operating system.
  • Add explicit Linux examples and instructions alongside Windows/IIS steps to ensure parity and inclusivity for non-Windows users.
GitHub Create Pull Request
CDN Monitoring, metrics, and raw logs for Azure CDN ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for configuring diagnostic settings and enabling logs, with no equivalent examples for Azure CLI, Bash, or Linux-native tools. The use of PowerShell commands and references to Windows-centric tooling is prevalent, and there is no mention of Linux or cross-platform alternatives. The configuration steps and automation guidance are tailored to users familiar with Windows environments, potentially excluding or inconveniencing Linux users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Explicitly mention that all operations can be performed using Azure CLI or REST API, and provide links or references to those methods.
  • Include Bash script samples where appropriate, especially for automation scenarios.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented together, rather than PowerShell-only sections.
  • Clarify that the Azure portal and Log Analytics are cross-platform, but scripting and automation should be accessible to all OS users.
  • Review and update any references to Windows-specific tools or terminology to ensure parity and inclusivity for Linux users.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →