CDN

100
Total Pages
84
Linux-Friendly Pages
16
Pages with Bias
16.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

33 issues found
Showing 1-25 of 33 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-12 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, requiring Visual Studio 2015 and referencing Windows-specific UI steps and screenshots. All examples assume use of Visual Studio and Windows tools (e.g., NuGet Package Manager Console, PowerShell), with no mention of Linux/macOS alternatives such as VS Code, .NET CLI, or cross-platform package management. There are no instructions or guidance for Linux/macOS users to complete the tutorial.
Recommendations
  • Provide instructions for using .NET CLI (dotnet new, dotnet add package) to create and manage projects/packages on Linux/macOS.
  • Include guidance for using VS Code or other cross-platform editors instead of only Visual Studio.
  • Add screenshots and steps for Linux/macOS environments, or clarify which steps are platform-agnostic.
  • Offer alternative commands for package installation (e.g., dotnet add package) and running the application from the terminal.
  • Explicitly state platform requirements and offer parity where possible.
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 06:20
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 Windows-centric, requiring Visual Studio 2015 and referencing Windows-specific UI elements and workflows. All examples and instructions assume a Windows environment, with no mention of Linux/macOS alternatives for .NET development (such as Visual Studio Code, JetBrains Rider, or CLI tools). The only command-line example is for PowerShell (NuGet Package Manager Console), and there are no Linux/macOS shell equivalents. The 'Running the program' section assumes use of Visual Studio's Start button, which is not available on Linux/macOS.
Recommendations
  • Add instructions for setting up .NET development on Linux/macOS, such as using Visual Studio Code or JetBrains Rider.
  • Include CLI-based project creation and NuGet package installation steps (e.g., using 'dotnet new' and 'dotnet add package') that work cross-platform.
  • Provide guidance for compiling and running the application from the command line, not just via Visual Studio.
  • Mention cross-platform authentication options and any OS-specific caveats.
  • Reorder or parallelize examples so Linux/macOS instructions are given equal prominence.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md ...s/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio (Windows-only), using Windows-specific UI instructions, and relying on PowerShell/NuGet Package Manager Console for package installation. There are no examples or guidance for Linux or cross-platform development environments (e.g., VS Code, JetBrains Rider, or CLI-based workflows). The documentation does not mention or provide parity for Linux users, such as using the .NET CLI or alternative editors.
Recommendations
  • Add instructions for creating and managing .NET projects using the cross-platform .NET CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Mention and provide examples for using cross-platform editors like Visual Studio Code or JetBrains Rider.
  • Clarify that Visual Studio is only required if using Windows-specific features, and provide Linux/macOS alternatives.
  • Include screenshots or descriptions relevant to Linux/macOS environments.
  • Provide a section or callout for Linux/macOS users, outlining any differences or additional steps.
  • Ensure that PowerShell/NuGet Package Manager Console commands are accompanied by equivalent Bash or shell commands where possible.
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a subtle Windows bias by recommending Visual Studio Code as the editor (which is often associated with Windows, though cross-platform), referencing the Visual Studio Code debugger and its launch.json for parameter passing, and concluding with a link to PowerShell-based management. There are no explicit Linux-specific instructions, examples, or references to Linux-native tools or editors. All command-line instructions are generic, but the only editor/debugger guidance is for Visual Studio Code, and the only alternative management tool mentioned is PowerShell.
Recommendations
  • Add explicit instructions or tips for running and debugging the Node.js application on Linux and macOS, such as using terminal commands or editors like Vim, Emacs, or GNOME Builder.
  • Provide equivalent examples for configuring command-line parameters in popular Linux-based editors or IDEs (e.g., JetBrains WebStorm, Atom, or using plain terminal).
  • Include a section or link for managing CDN resources using Azure CLI (which is cross-platform and popular on Linux), not just PowerShell.
  • When referencing editors or tools, clarify their cross-platform availability and suggest alternatives for Linux users.
  • Ensure screenshots and file path examples use neutral or Linux-style paths (e.g., forward slashes) where possible.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for enabling diagnostic logs, with no equivalent Azure CLI, Bash, or cross-platform scripting examples. Additionally, it recommends Microsoft Azure Storage Explorer (a GUI tool primarily associated with Windows, though available cross-platform) for log access, without mentioning Linux-native or command-line alternatives. There are no Linux-specific instructions or parity in tooling or workflow.
Recommendations
  • Add Azure CLI examples for all PowerShell workflows, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash or shell script examples where applicable, especially for tasks like downloading and processing logs.
  • Mention and provide examples using cross-platform tools such as azcopy, Azure CLI storage commands, or open-source alternatives for accessing and exporting logs.
  • Clarify that PowerShell Core is available cross-platform, if retaining PowerShell examples, and provide installation guidance for Linux/macOS.
  • Ensure that any tool recommendations (such as Storage Explorer) are clearly marked as cross-platform, and suggest command-line alternatives for headless or server environments.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-troubleshoot-compression.md ...blob/main/articles/cdn/cdn-troubleshoot-compression.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) for troubleshooting and configuration, and omitting Linux equivalents or examples. The guidance for server-side configuration is focused solely on Microsoft IIS, with no reference to common Linux web servers such as Apache or Nginx. Troubleshooting steps and tool recommendations are Windows-centric, and Linux alternatives are not provided.
Recommendations
  • Include Linux-based troubleshooting tools such as curl, wget, or command-line examples for checking HTTP headers.
  • Add instructions for configuring compression on popular Linux web servers (e.g., Apache: mod_deflate, Nginx: gzip/brotli modules).
  • Mention cross-platform tools (e.g., Wireshark, Postman) alongside Fiddler.
  • Provide examples and guidance for both Windows and Linux environments, ensuring parity in troubleshooting steps.
  • Clarify that IIS-specific instructions apply only to Windows servers, and provide equivalent steps for Linux-based origins.
GitHub Create Pull Request
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-12-29 18:00
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 the Azure portal (web UI) and Azure PowerShell. There are no examples or instructions for using Azure CLI (which is cross-platform and preferred by many Linux users), nor are there bash or shell script equivalents. All command-line automation is shown with PowerShell, which is a Windows-centric tool, despite its availability on Linux. This may disadvantage Linux users or those who prefer bash/CLI workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line tasks, such as adding or removing custom domains.
  • Include bash/shell script snippets where appropriate, especially for DNS record management or validation steps.
  • Explicitly mention that PowerShell is available cross-platform, but recommend Azure CLI for Linux/macOS users.
  • Ensure that any references to tools or scripts are balanced between Windows and Linux environments.
  • Consider adding a 'Choose your environment' or 'Choose your tool' tab set for PowerShell, Azure CLI, and possibly REST API.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-template.md .../main/articles/cdn/create-profile-endpoint-template.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 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 the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary automation method alongside the CLI, which may suggest a Windows bias. Additionally, there are no mentions of Linux-specific tools or workflows, and the PowerShell section appears before the Portal section, reinforcing the Windows-first pattern.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, especially for common tasks like setting variables and running Azure CLI commands.
  • Clarify that Azure CLI commands can be run on Windows, Linux, and macOS, and consider providing bash-specific syntax (e.g., export instead of read -p for variable assignment).
  • If PowerShell is included, note that PowerShell Core is cross-platform, or clarify when examples are Windows-specific.
  • Consider listing Azure CLI (bash) as the default or first automation method, as it is cross-platform and more common for Linux users.
  • Mention or link to documentation for using ARM templates with Linux-native tools (e.g., bash scripts, cloud-init, etc.) if relevant.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/managed-identity.md .../azure-docs/blob/main/articles/cdn/managed-identity.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively describing configuration steps using the Azure Portal GUI, which is most familiar to Windows users. There are no CLI-based examples (such as Azure CLI or Bash scripts) that would be more accessible to Linux users. No PowerShell commands are shown, but the lack of Linux-friendly command-line instructions and the assumption of GUI usage reflects a Windows-centric approach.
Recommendations
  • Add Azure CLI examples for all configuration steps, including enabling managed identity and configuring Key Vault access policies.
  • Include Bash script snippets where appropriate to automate tasks for Linux users.
  • Explicitly mention that all steps can be performed using cross-platform tools (Azure CLI, REST API) and provide links or examples.
  • Ensure parity by presenting CLI instructions before or alongside GUI instructions, not just after.
  • Clarify that the Azure Portal is web-based and platform-agnostic, but supplement with command-line alternatives for users who prefer or require them.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/monitoring-and-access-log.md ...cs/blob/main/articles/cdn/monitoring-and-access-log.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides detailed configuration steps and examples exclusively using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform scripting. The focus on PowerShell and lack of Linux or cross-platform alternatives demonstrates a Windows bias in the operational guidance.
Recommendations
  • Add equivalent configuration instructions and code samples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include Bash script examples for common tasks, such as enabling diagnostic settings and exporting logs.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but recommend Azure CLI for Linux users.
  • Reorder or parallelize example sections so that both PowerShell and CLI/Bash options are presented together, giving equal prominence.
  • Add notes or links to official documentation for Azure CLI and Bash usage for monitoring and logging tasks.
GitHub Create Pull Request
CDN Diagnostic logs ...cs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md
Medium 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 notable Windows bias. All command-line automation examples are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The only graphical tool recommended for accessing logs is Microsoft Azure Storage Explorer, a Windows-centric application, and there are no instructions for using Linux-native tools or workflows. Additionally, Windows/PowerShell approaches are presented before any consideration of Linux/macOS usage, and Linux-specific examples or guidance are absent throughout.
Recommendations
  • Add equivalent Azure CLI (az) command examples for enabling and configuring diagnostic logs, which work natively on Linux/macOS.
  • Include instructions for accessing and downloading logs using Linux-native tools (e.g., az storage blob download, curl, jq, or Python scripts).
  • Mention and document open-source, cross-platform alternatives to Microsoft Azure Storage Explorer, such as using the Azure CLI or third-party tools.
  • Present examples for both Windows and Linux/macOS platforms side-by-side, or in separate tabs/sections, to ensure parity.
  • Clarify that PowerShell Core is available cross-platform, but also provide Bash/CLI alternatives for users who do not use PowerShell.
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-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 mentions managing Azure CDN endpoints via the Azure portal or PowerShell, but does not mention or provide examples for Linux/macOS-friendly tools such as Azure CLI, Bash, or REST API. PowerShell is Windows-centric and is listed before any cross-platform alternatives. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Add instructions and examples for managing Azure CDN endpoints using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for automation, which are OS-agnostic.
  • Where PowerShell is referenced, clarify that Azure CLI is also available and provide links or examples.
  • Ensure that any automation or scripting guidance includes both PowerShell and CLI/Bash examples.
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-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 step-by-step instructions for managing Azure CDN custom domains via the Azure portal and Azure PowerShell, but does not offer equivalent examples for Linux/macOS command-line users (e.g., Azure CLI, Bash). PowerShell is a Windows-centric tool, and its exclusive use in command-line examples creates friction for users on other platforms. No Linux or macOS-specific instructions or CLI alternatives are provided.
Recommendations
  • Add Azure CLI examples for all PowerShell-based tasks, such as adding and removing custom domains.
  • Explicitly mention cross-platform tools (Azure CLI, Bash) and provide usage instructions for Linux/macOS users.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS, but recommend CLI as the primary cross-platform solution.
  • Ensure that all command-line instructions are presented in both PowerShell and CLI formats, or link to equivalent CLI documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) for troubleshooting and configuration. There are no Linux/macOS equivalents or examples provided for checking compression headers or configuring origin server compression. Windows-specific server configuration steps (IIS) are described in detail, while Apache/Nginx or other common Linux web servers are not addressed.
Recommendations
  • Include Linux/macOS tools for inspecting HTTP headers, such as curl, wget, or command-line examples.
  • Add troubleshooting steps for common Linux web servers (e.g., Apache, Nginx), including how to configure compression and handle proxy headers.
  • Present cross-platform tools and examples (e.g., browser developer tools, curl) before or alongside Windows-specific tools.
  • Provide links or references to documentation for configuring compression on non-Windows origin servers.
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 instructions for verifying results, but the PowerShell section is presented immediately after the CLI section and uses Windows/PowerShell-specific syntax. There are no explicit Linux/macOS-specific instructions or notes, and the CLI examples use syntax compatible with Bash but do not clarify cross-platform usage. PowerShell is a Windows-centric tool, and its inclusion without equivalent Linux/macOS shell examples may create friction for non-Windows users.
Recommendations
  • Explicitly state that Azure CLI examples use Bash syntax and are suitable for Linux/macOS users.
  • Add notes clarifying cross-platform compatibility for all CLI commands.
  • If PowerShell examples are included, also provide equivalent Bash/zsh commands for Linux/macOS users.
  • Consider listing CLI (Bash) instructions before PowerShell to reduce perceived Windows-first bias.
  • Include troubleshooting notes or links for common Linux/macOS issues when using Terraform and Azure CLI.
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-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 provides detailed configuration steps and code samples exclusively using Azure PowerShell, which is most commonly used and best supported on Windows. There are no equivalent examples for Azure CLI, Bash, or Linux/macOS shell environments. The use of PowerShell is presented as the primary (and only) automation method, and the portal instructions are also Windows-centric (e.g., screenshots, navigation patterns). This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including diagnostic settings configuration and log management.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide installation and usage notes for Linux/macOS.
  • Reorder or parallelize automation sections so that CLI and PowerShell instructions are presented together, not PowerShell-only.
  • Include Bash or shell script examples where appropriate.
  • Clarify tool prerequisites for each platform (Windows, Linux, macOS) and link to installation guides.
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-11 06:20
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 via the Azure portal and Azure PowerShell. However, it lacks equivalent examples for Linux/macOS users, such as Azure CLI or Bash scripts, and relies solely on PowerShell for command-line automation. This creates friction for users on non-Windows platforms who may not have access to or prefer not to use PowerShell.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., adding/removing custom domains).
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure that code tabs or sections are available for both PowerShell and CLI/Bash where applicable.
  • 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-11 06:20
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 code samples for enabling 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 tool recommended for browsing storage (Azure Storage Explorer) is a GUI application with a Windows-centric history. No Linux-specific workflows or parity examples are given, and PowerShell is presented as the sole scripting option.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell automation tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be used on Linux/macOS, or clarify platform requirements.
  • Provide sample Bash scripts or Python code for downloading and processing logs from Azure Storage.
  • Include instructions for using command-line tools like azcopy or Azure CLI's storage commands to access and download blobs.
  • List Linux-native alternatives to Azure Storage Explorer (e.g., azcopy, rclone, or CLI usage) for browsing and downloading blobs.
  • Ensure that example order alternates or is grouped by platform, rather than presenting Windows/PowerShell first and exclusively.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page mentions managing Azure CDN endpoints via the Azure portal or PowerShell, with no mention of Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive mention suggests a Windows-first approach. There are no Linux/macOS-specific instructions or examples, nor is there mention of cross-platform management tools like Azure CLI.
Recommendations
  • Add instructions and examples for managing Azure CDN endpoints using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples where appropriate.
  • Explicitly state that management can be performed from any OS using the Azure portal or Azure CLI.
  • If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or provide links to installation guides for Linux/macOS.
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-11 06:20
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 CDN compression issues. There are no Linux/macOS equivalents or examples provided, and Windows-specific server configuration steps are described without mentioning Apache, Nginx, or other common Linux web servers.
Recommendations
  • Include Linux/macOS troubleshooting tools such as curl, wget, or command-line examples for checking HTTP headers.
  • Mention and provide configuration guidance for popular Linux web servers like Apache (mod_deflate, mod_brotli) and Nginx (gzip, brotli modules) when discussing compression and proxy headers.
  • List cross-platform tools (e.g., Wireshark, HTTPie) alongside Fiddler, and avoid presenting Windows tools first or exclusively.
  • Add explicit notes or sections for Linux/macOS users to ensure parity in troubleshooting steps.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
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 cross-platform scripting, and the PowerShell section is presented as the only programmatic method. This creates friction for Linux/macOS users who may not use PowerShell or prefer Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for configuring diagnostic settings and log destinations.
  • Include Bash shell scripting samples where appropriate.
  • Explicitly mention that Azure CLI is cross-platform and provide links to CLI documentation.
  • Reorder sections so that portal and CLI instructions are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Clarify that PowerShell can be used on Linux/macOS, but provide guidance for users who prefer CLI.
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: 2025-12-29 18:00
Reviewed by: Unknown
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 tooling, it implicitly favors Windows users by omitting CLI-based workflows (such as Azure CLI or Azure PowerShell), which are commonly used on Linux and macOS. There are no Linux-specific instructions or parity examples.
Recommendations
  • Add Azure CLI examples for creating CDN profiles and endpoints, as the Azure CLI is cross-platform and widely used on Linux.
  • If including PowerShell examples, ensure Azure CLI equivalents are provided and shown first or side-by-side.
  • Mention that all steps can be performed from any OS using the Azure Portal, but highlight CLI options for users who prefer or require command-line workflows.
  • Include a section or links to documentation for automating these tasks via CLI or scripts, which is important for Linux users.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-custom-ssl.md ...cs/azure-docs/blob/main/articles/cdn/cdn-custom-ssl.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web GUI) and does not provide any command-line examples. There are no instructions or examples using cross-platform tools such as Azure CLI, PowerShell, or Bash scripts. This omission leaves Linux and automation-focused users without guidance for non-GUI or non-Windows environments.
Recommendations
  • Add Azure CLI examples for all major steps (enabling/disabling HTTPS, certificate management, domain validation) to provide parity for Linux and macOS users.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI commands are also present and shown first or side-by-side.
  • Reference automation and scripting options (e.g., REST API, ARM templates, Bicep) for users who prefer or require non-GUI workflows.
  • Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and link to relevant cross-platform documentation.
  • Include troubleshooting steps or notes relevant to Linux environments, such as certificate format handling or DNS tools.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-pop-list-api.md .../azure-docs/blob/main/articles/cdn/cdn-pop-list-api.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation does not provide any platform-specific examples or commands, but it references a downloadable IP list (from microsoft.com) that is typically provided as a CSV or XML file, often with usage patterns and tooling more familiar to Windows users. There are no explicit examples for retrieving or parsing the IP list using Linux tools (e.g., curl, wget, grep, jq), nor are there any PowerShell or Windows command examples. However, the lack of Linux-specific guidance or parity in examples constitutes a subtle Windows bias.
Recommendations
  • Add explicit examples for retrieving and parsing the IP list using common Linux command-line tools (e.g., curl, wget, grep, awk, jq).
  • Provide sample scripts or command snippets for both Windows (PowerShell) and Linux (bash) environments.
  • Clarify the format of the downloadable IP list and suggest cross-platform tools for parsing it.
  • Ensure that references to tools or methods are balanced between Windows and Linux, or are platform-agnostic where possible.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-purge-endpoint.md ...zure-docs/blob/main/articles/cdn/cdn-purge-endpoint.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation only describes how to purge an Azure CDN endpoint using the Azure Portal, a graphical tool primarily accessed via web browsers, which are equally available on Windows, Linux, and macOS. However, there are no command-line examples provided (such as Azure CLI, PowerShell, or REST API usage). The 'Next steps' section links to the REST API, but there are no explicit Linux-friendly (e.g., Azure CLI, Bash) examples or instructions. There is also no mention of PowerShell, but the absence of Linux-specific command-line examples may disadvantage Linux users who prefer CLI workflows.
Recommendations
  • Add examples for purging a CDN endpoint using the Azure CLI, which is cross-platform and commonly used on Linux.
  • Provide sample REST API calls using curl or HTTPie, with example commands that can be run from a Linux shell.
  • If PowerShell examples are added in the future, ensure that Azure CLI or Bash equivalents are also included and presented with equal prominence.
  • Explicitly mention that all operations can be performed from any OS via the Azure Portal, and highlight CLI options for users who prefer command-line tools.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →