CDN

50
Total Pages
38
Linux-Friendly Pages
12
Pages with Bias
24.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (14)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily biased toward Windows environments. It exclusively references Visual Studio 2015 for project setup, assumes the use of Windows-specific UI paths (e.g., File > New > Project), and only provides instructions for using tools like NuGet Package Manager Console and PowerShell, which are primarily Windows-centric. There are no examples or guidance for Linux or cross-platform development environments, such as using .NET CLI, VS Code, or running the sample on Linux/macOS. The only alternative mentioned is Node.js, but within the .NET section, all instructions are Windows-specific.
Recommendations:
  • Provide equivalent instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
  • Include guidance for using cross-platform editors like Visual Studio Code, not just Visual Studio.
  • Avoid UI instructions that are specific to Windows (e.g., Visual Studio menus) or provide parallel steps for Linux/macOS users.
  • Mention and demonstrate how to install required packages and run the application on Linux/macOS.
  • If referencing PowerShell, also provide Bash or shell script equivalents for common tasks.
  • Clarify that the .NET SDK and Azure SDK libraries are cross-platform, and show how to authenticate and run the sample on non-Windows systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/monitoring-and-access-log.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for configuring diagnostic settings and enabling logs. There are no equivalent instructions or examples for Linux users (e.g., using Azure CLI or Bash scripts). The exclusive use of PowerShell and the absence of cross-platform command-line alternatives make the instructions less accessible to users on Linux or macOS. Additionally, the documentation references 'Azure PowerShell' as the primary automation tool, reinforcing a Windows-centric approach.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell-based instructions, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance on choosing the appropriate tool for the user's environment.
  • Where possible, provide Bash script examples alongside PowerShell scripts, especially for automation scenarios.
  • Reorganize sections so that cross-platform tools (Azure CLI) are presented before or alongside Windows-specific tools (PowerShell), or provide a clear tabbed interface for different platforms.
  • Review and update any references to 'Azure PowerShell' as the default automation tool to a more inclusive phrasing, such as 'Azure PowerShell or Azure CLI'.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-sas-storage-support.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific examples or tooling, but it also does not mention or demonstrate how to generate or use SAS tokens via command-line tools or scripts. There are no references to Windows tools (such as PowerShell or Azure CLI on Windows), nor are there any Linux/Unix-specific examples. However, the absence of any command-line or scripting examples means Linux users are not shown parity in how to interact with SAS tokens, which is a subtle form of bias by omission.
Recommendations:
  • Add examples showing how to generate SAS tokens using both Azure CLI (cross-platform) and PowerShell, ensuring both are presented equally.
  • Include sample commands for accessing blobs with SAS tokens using curl (Linux/Unix) and Invoke-WebRequest (PowerShell/Windows).
  • Explicitly mention that all steps can be performed on both Windows and Linux, and provide links to relevant cross-platform tooling.
  • If screenshots or UI steps are included, clarify that the Azure Portal is accessible from any OS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-troubleshoot-compression.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (Fiddler, IIS) for troubleshooting and configuration, without mentioning Linux equivalents or providing cross-platform guidance. All server-side configuration examples are for Microsoft IIS, and there are no instructions for common Linux web servers (e.g., Apache, Nginx).
Recommendations:
  • Include Linux-friendly tools for inspecting HTTP headers, such as curl, wget, or command-line examples using these tools.
  • Provide troubleshooting steps and configuration guidance for popular Linux web servers (e.g., Apache, Nginx), including how to handle compression and proxy headers.
  • Mention cross-platform or browser-based tools (such as browser developer tools) more prominently and provide example workflows.
  • When referencing server configuration, present both Windows (IIS) and Linux (Apache/Nginx) instructions in parallel, or link to relevant documentation for each platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell examples are included as a primary tab alongside Azure CLI, which can be interpreted as a Windows-first approach. There is no explicit mention of Linux or macOS environments, nor are there Bash-specific examples or notes about cross-platform usage. The PowerShell examples use Windows-style variable assignment, and there is no indication of parity for Linux users beyond the Azure CLI tab.
Recommendations:
  • Explicitly mention that the Azure CLI instructions are cross-platform and suitable for Linux, macOS, and Windows.
  • Add a Bash-specific tab or clarify that the Azure CLI tab uses Bash syntax, which is common on Linux/macOS.
  • If PowerShell is included, clarify that it is available cross-platform, or provide notes for Linux/macOS PowerShell users.
  • Consider listing the Azure CLI (Bash) tab first, as it is the most cross-platform option.
  • Add a short section in prerequisites or notes about supported operating systems and shells.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/monitoring-and-access-log.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for configuring diagnostics and logs, with no equivalent examples for Azure CLI (cross-platform) or bash scripting. All automation and scripting instructions are presented in PowerShell syntax, which is native to Windows and less common on Linux systems. There is no mention of Linux, macOS, or cross-platform tooling, and no guidance for users who may be working from non-Windows environments.
Recommendations:
  • Add Azure CLI (az) command examples alongside PowerShell for all diagnostic and logging configuration steps. Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using Azure CLI or the Azure portal.
  • Where scripting is shown, provide both PowerShell and bash (or shell-agnostic) script snippets.
  • Include a section or note for Linux/macOS users, highlighting any differences or confirming parity.
  • Review terminology to avoid implying PowerShell is the default or only automation method.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-create-new-endpoint.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively uses the Azure Portal (web UI) for instructions and does not provide any command-line examples. While this avoids explicit Windows-specific tools like PowerShell, it also omits CLI-based workflows that are common on Linux and cross-platform environments. The lack of Azure CLI or Bash examples means Linux users do not see parity in automation or scripting approaches. Additionally, the documentation implicitly assumes a Windows-first perspective by not mentioning or linking to CLI alternatives.
Recommendations:
  • Add equivalent Azure CLI examples for all major steps (creating the CDN profile, endpoint, and resource cleanup), using Bash syntax.
  • Explicitly mention that the steps can be performed using Azure CLI or PowerShell, and provide links to relevant documentation for both.
  • Ensure that any future updates include both portal and CLI (cross-platform) instructions side by side.
  • Consider including a table or section that compares how to perform the tasks in the Portal, Azure CLI, and PowerShell, making it clear that all platforms are supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-net.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 version), uses Windows-specific UI instructions, and only provides instructions for using the NuGet Package Manager Console (a Visual Studio feature). There are no examples or guidance for Linux or cross-platform development (e.g., using VS Code, .NET CLI, or command-line tools available on Linux/macOS). The 'Next Steps' section also promotes PowerShell, a tool historically associated with Windows, without mentioning Bash or other cross-platform alternatives.
Recommendations:
  • Provide instructions for setting up and running the sample using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux, macOS, and Windows.
  • Mention and provide examples for using Visual Studio Code, a cross-platform editor, instead of or in addition to Visual Studio 2015.
  • Include screenshots and steps for Linux/macOS users, such as installing .NET SDK, creating projects, and managing NuGet packages from the command line.
  • In the 'Next Steps' section, add links or references to Bash/Azure CLI equivalents for managing CDN resources, not just PowerShell.
  • Avoid UI instructions that are exclusive to Windows (e.g., Visual Studio menus) or provide alternative steps for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation shows a mild Windows bias by recommending Visual Studio Code (a Microsoft product, though cross-platform) as the editor, referencing Visual Studio Code's launch.json for debugging, and mentioning PowerShell as an additional management tool in the 'Next Steps' section. There are no explicit Linux or macOS-specific instructions, nor are there examples of running the code or setting up debugging on Linux/macOS. However, the main code and npm commands are cross-platform, and there are no PowerShell-heavy or Windows-only command-line examples.
Recommendations:
  • Explicitly mention that all steps and tools (npm, Node.js, editors) work on Linux and macOS as well as Windows.
  • Provide alternative instructions or notes for setting up command-line parameters in popular Linux/macOS editors or debuggers (e.g., JetBrains WebStorm, VS Code on Linux, or command-line usage).
  • In the 'Next Steps' section, balance the mention of PowerShell with links to equivalent Azure CLI documentation, which is cross-platform.
  • Where screenshots or instructions reference Visual Studio Code, clarify that it is available on all major OSes, or provide alternative examples for other environments.
  • Consider including a brief section or note on running the Node.js application from a Linux/macOS terminal to reinforce cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-azure-diagnostic-logs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for enabling diagnostic logs, with no equivalent Azure CLI, Bash, or Linux-native instructions. The section on consuming logs recommends Microsoft Azure Storage Explorer, a GUI tool primarily available for Windows (though cross-platform, it is often associated with Windows environments), and does not mention Linux-native alternatives or command-line options. There are no Linux shell, Azure CLI, or cross-platform scripting examples, and no mention of how to perform these tasks on Linux systems.
Recommendations:
  • Add Azure CLI examples alongside PowerShell for all diagnostic log configuration tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash or shell script examples for downloading and processing logs from Azure Storage, such as using az storage blob commands or tools like curl, jq, or Python scripts.
  • Mention and provide instructions for Linux-native tools (e.g., azcopy, Azure CLI, or Python SDK) for accessing and exporting logs, in addition to Microsoft Azure Storage Explorer.
  • Ensure that any downloadable tools or sample code are described as cross-platform, and provide explicit instructions for Linux users where applicable.
  • Consider reordering sections so that cross-platform or Linux-friendly approaches are presented before or alongside Windows/PowerShell-specific instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-map-content-to-custom-domain.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-pop-list-api.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any platform-specific examples or tooling instructions, but it also does not include any Linux-specific guidance or examples. There are no explicit Windows or PowerShell commands, but the absence of any example commands or scripts (for either Windows or Linux) means Linux users are not directly supported with parity.
Recommendations:
  • Add example commands for retrieving the POP IP list using common Linux tools (e.g., curl, wget, jq) to demonstrate how to automate the retrieval process.
  • If providing example scripts, ensure both Windows (PowerShell) and Linux (bash) versions are included.
  • Mention cross-platform tools and approaches where possible, such as REST API calls using platform-agnostic methods.
  • Clarify that the instructions apply equally to both Windows and Linux environments, or specify any differences if they exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-purge-endpoint.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page only describes how to purge an Azure CDN endpoint using the Azure Portal (web UI) and does not provide any command-line examples. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but there is also a lack of parity for Linux users, as there are no CLI (Azure CLI, Bash, etc.) or REST API command examples that could be run on Linux or cross-platform environments. The only programmatic reference is a link to the REST API documentation in the 'Next steps' section, without any example provided.
Recommendations:
  • Add Azure CLI examples for purging a CDN endpoint, as the Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide REST API usage examples (e.g., using curl or HTTPie) to demonstrate how to purge a CDN endpoint programmatically from any OS.
  • If PowerShell or Windows-specific tools are ever referenced, ensure equivalent Bash or shell examples are provided.
  • Explicitly mention that the Azure Portal method is OS-agnostic, but highlight CLI and API options for automation and scripting on Linux.