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 26-50 of 91 flagged pages
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: 2026-01-09 00:34
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 strong Windows bias. 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 consuming logs is Microsoft Azure Storage Explorer, a Windows-centric application. There are no Linux-specific instructions, nor are cross-platform alternatives (such as Azure CLI or REST API usage) provided. The ordering also places PowerShell and Windows tools before any mention of platform-neutral or Linux-friendly approaches.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell instructions, showing how to enable diagnostic logs using az commands.
  • Include instructions or sample scripts for Bash or shell environments, especially for downloading and processing logs from Azure Storage.
  • Mention and provide usage examples for cross-platform tools such as azcopy, or demonstrate how to use REST APIs directly from Linux/macOS.
  • Reference open-source or cross-platform storage explorers (e.g., command-line tools, web-based explorers) alongside Microsoft Azure Storage Explorer.
  • Ensure that Linux/macOS users are explicitly supported in all workflow steps, including log consumption and export.
  • Reorder sections so that platform-neutral or cross-platform methods are presented before Windows-specific tools.
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: 2026-01-09 00:34
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 development environments. It exclusively references Visual Studio (Windows-only), uses Windows UI terminology and screenshots, and provides instructions for using PowerShell. There are no examples or guidance for Linux or cross-platform development tools (such as VS Code or CLI), nor are alternative workflows for Linux users mentioned.
Recommendations
  • Add instructions for setting up and running the .NET application using cross-platform tools like Visual Studio Code or JetBrains Rider.
  • Include command-line examples for .NET CLI (dotnet new, dotnet add package, dotnet run) that work on Linux and macOS.
  • Provide screenshots and step-by-step instructions for Linux environments, including package installation and project setup.
  • Mention and link to Linux-compatible alternatives to PowerShell, such as Azure CLI, and provide equivalent examples.
  • Clarify that the Azure CDN .NET SDK is cross-platform and can be used outside of Visual Studio/Windows.
  • Reorder or balance references so that Windows and Linux tools are presented with parity, rather than Windows-first.
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: 2026-01-09 00:34
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 command-line tools such as Azure CLI or Bash scripts. The use of PowerShell, which is traditionally associated with Windows environments, and the absence of Azure CLI or Bash instructions, indicates a bias toward Windows tooling and patterns. There are no explicit Linux or cross-platform command-line examples, which may disadvantage users on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including adding and removing custom domains.
  • Include Bash script snippets where appropriate, especially for DNS record management or validation.
  • Explicitly mention that Azure CLI is cross-platform and provide links to installation and usage guides.
  • Ensure that instructions for DNS management are generic and not tied to Windows-specific tools or terminology.
  • Consider adding a section or tabs for Linux/macOS users, highlighting any differences or additional steps.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-overview.md ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing PowerShell as the only command-line management option for Azure CDN endpoints, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific examples or tools provided, and the management instructions implicitly prioritize Windows workflows. This may make Linux users feel unsupported or require them to seek additional resources.
Recommendations
  • Include Azure CLI examples alongside PowerShell for endpoint management, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that management can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform tooling.
  • Add Bash or shell script examples for common CDN tasks.
  • Ensure that references to the Azure portal and automation tools do not imply Windows exclusivity.
  • Review linked pages (e.g., 'cdn-manage-powershell.md') to ensure Linux parity in examples and instructions.
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: 2026-01-09 00:34
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, and omitting Linux equivalents or examples. The troubleshooting steps and server configuration guidance are focused on Microsoft IIS, with no mention of Apache, Nginx, or Linux-based workflows. Windows tools are mentioned first and exclusively, with no parity for Linux users.
Recommendations
  • Include Linux-based troubleshooting tools such as curl, wget, or command-line examples for checking HTTP headers.
  • Provide guidance for configuring compression on common Linux web servers (e.g., Apache, Nginx), including how to handle proxy headers and compression settings.
  • Mention cross-platform tools (e.g., Wireshark, browser developer tools) and provide examples for both Windows and Linux environments.
  • Add links or references to documentation for Linux server configuration regarding compression and proxy behavior.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and Portal. PowerShell examples are included alongside Azure CLI, which is cross-platform, but PowerShell is primarily a Windows tool. There is no mention of Linux-specific shell patterns (e.g., bash), nor are there explicit Linux examples or notes about cross-platform compatibility. The ordering of examples (CLI, PowerShell, Portal) is neutral, but the inclusion of PowerShell without a corresponding bash or Linux shell example introduces a subtle Windows bias.
Recommendations
  • Add explicit bash shell examples for Linux users, showing how to run Azure CLI commands in a typical Linux environment.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Note that PowerShell Core is available on Linux/macOS, or clarify that the PowerShell example is for Windows users.
  • Consider including instructions for running the template deployment from a Linux terminal, and mention any OS-specific prerequisites if relevant.
  • Where possible, avoid assuming PowerShell as the default scripting environment; provide parity for Linux shell users.
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: 2026-01-09 00:34
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, primarily by providing only Azure PowerShell examples for configuring diagnostic settings and log destinations. There are no CLI (az), Bash, or Linux-native instructions, and all automation examples use PowerShell cmdlets, which are most familiar to Windows users. The documentation also references the Azure portal UI, which is platform-agnostic but does not offer parity with Linux command-line workflows. The lack of Linux or cross-platform CLI examples makes the documentation less accessible to users on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to configure diagnostic settings, log destinations, and retention policies using Bash or shell scripting.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links to CLI reference documentation.
  • Where possible, provide sample scripts for both PowerShell and Bash, and indicate OS compatibility.
  • Include a section on cross-platform automation, highlighting tools and patterns that work on Linux, macOS, and Windows equally.
  • Review and update the documentation to ensure Linux users can follow all steps without needing PowerShell or Windows-specific tooling.
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: 2026-01-08 00:53
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 development environments. It exclusively references Visual Studio (Windows-only), uses Windows terminology (e.g., 'Windows' project type), and provides instructions and screenshots for Windows tools. There are no examples or guidance for Linux or cross-platform development environments, such as .NET CLI or VS Code. The 'Next Steps' section also prioritizes PowerShell, a Windows-centric tool, without mentioning Bash or other Linux-native alternatives.
Recommendations
  • Add instructions for creating and running the .NET application using the .NET CLI, which works on Linux, macOS, and Windows.
  • Include examples and screenshots for cross-platform editors like VS Code.
  • Provide Linux/macOS equivalents for package management (e.g., 'dotnet add package' instead of NuGet Package Manager in Visual Studio).
  • Mention Bash or Azure CLI alternatives alongside PowerShell for managing CDN resources.
  • Avoid using 'Windows' as the default project type; clarify that .NET Core/.NET 5+ projects are cross-platform.
  • Explicitly state platform requirements and offer parity for Linux/macOS users throughout the tutorial.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-overview.md ...Docs/azure-docs/blob/main/articles/cdn/cdn-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 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 management options are listed as 'Azure portal' and 'PowerShell', with no mention of Linux-native tools or workflows. There are no examples or instructions tailored for Linux users, and Windows-centric tools are mentioned before any cross-platform equivalents.
Recommendations
  • Add Azure CLI examples for managing CDN endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI and REST API can be used from Linux, macOS, and Windows, and provide links to relevant documentation.
  • Where PowerShell is referenced, also provide equivalent Bash or Azure CLI commands.
  • Include a section or note on Linux compatibility and best practices for Linux users managing Azure CDN.
  • Review all 'Next steps' and management instructions to ensure Linux parity and visibility.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and the Azure Portal. PowerShell examples are included alongside CLI, and references to PowerShell-specific commands (e.g., Remove-AzResourceGroup) are present. There is a subtle Windows bias: PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a prioritization of Windows environments. No explicit Linux shell (bash) examples or references to Linux-specific patterns are provided, and PowerShell is mentioned before the Portal option in each section.
Recommendations
  • Add explicit bash/Linux shell examples for all command-line instructions, showing parity with Azure CLI usage on Linux/macOS.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary platform-specific notes (e.g., environment variable syntax differences).
  • Consider reordering sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell), or provide a note about platform applicability.
  • If PowerShell is included, mention that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
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: 2026-01-08 00:53
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 providing only Azure PowerShell examples for command-line configuration, referencing Microsoft Azure Storage Explorer (a Windows-centric GUI tool) for log access, and omitting equivalent instructions for Linux users (such as Azure CLI, Bash, or cross-platform tools). There are no Linux-specific or cross-platform command-line examples, and Windows-oriented tools and patterns are mentioned exclusively or before alternatives.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux.
  • Include instructions for accessing and downloading logs using standard Linux tools (e.g., az storage blob download, curl, jq) and/or Python scripts.
  • Mention and provide examples for open-source, cross-platform storage explorers (such as the web-based Azure Portal or azcopy) alongside Microsoft Azure Storage Explorer.
  • Ensure that command-line examples are provided for both PowerShell and Bash/CLI, and present them in parallel or with clear parity.
  • Review all tool recommendations and ensure Linux-compatible options are referenced and documented.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively mentioning Windows tools (Fiddler, IIS) for troubleshooting and configuration, and by providing configuration steps only for Microsoft IIS web servers. There are no Linux or cross-platform equivalents (such as curl, wget, or Apache/Nginx configuration) referenced, nor are Linux-specific troubleshooting steps included.
Recommendations
  • Include examples using cross-platform tools such as curl or wget to check HTTP headers for compression.
  • Mention Linux web servers (e.g., Apache, Nginx) and provide equivalent configuration steps for handling compression and proxy headers.
  • List alternative tools for inspecting HTTP headers, such as tcpdump or Wireshark, which are available on Linux.
  • Present troubleshooting steps in a platform-neutral order, or provide parallel instructions for both Windows and Linux environments.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by recommending Visual Studio Code (a Microsoft product popular on Windows), referencing launch.json for debugging (a Windows-centric workflow), and mentioning PowerShell management in 'Next Steps' without equivalent Linux CLI references. There are no explicit Linux or macOS-specific instructions, examples, or tool recommendations. Console instructions are generic but lack Linux-specific context (e.g., bash/zsh, terminal setup).
Recommendations
  • Add explicit instructions and examples for running the Node.js app on Linux/macOS terminals (e.g., bash/zsh), including command-line usage and environment setup.
  • Mention and provide examples for using editors popular on Linux (e.g., Vim, Emacs, GNOME Builder) alongside Visual Studio Code.
  • Include references to Azure CLI for CDN management in 'Next Steps', and provide parity with PowerShell instructions.
  • Clarify that the instructions are cross-platform and note any OS-specific differences (e.g., file paths, environment variables).
  • Add screenshots or terminal output examples from Linux/macOS environments to balance the Windows-centric visuals.
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: 2026-01-08 00:53
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 (GUI) and Azure PowerShell. There are no CLI examples for Linux/macOS users (e.g., Azure CLI or Bash), and PowerShell is featured as the only scripting/automation option. This creates a bias toward Windows users, as PowerShell is native to Windows and less commonly used on Linux/macOS. No Linux-specific tools or patterns are mentioned, and the documentation does not offer parity for users who prefer or require cross-platform command-line solutions.
Recommendations
  • Add equivalent Azure CLI (az cdn ...) examples for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets or instructions for DNS record management using common Linux tools (e.g., dig, nsupdate) where appropriate.
  • Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to installation guides.
  • If PowerShell is retained, clarify that PowerShell Core is available cross-platform, but still provide CLI alternatives.
  • Review all automation steps to ensure Linux/macOS users are not excluded and can follow the tutorial without switching to Windows or PowerShell.
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-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and code samples for performing tasks using Azure PowerShell, but does not include equivalent examples for Linux/Unix command-line tools (such as Azure CLI or Bash). The only automation example is PowerShell, which is primarily a Windows tool, and there is no mention of cross-platform alternatives. This may disadvantage Linux/macOS users or those who prefer command-line interfaces other than PowerShell.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all automation steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available cross-platform, if PowerShell is to be retained, and provide installation links for non-Windows users.
  • Where possible, provide Bash script equivalents or reference how to perform the same actions using REST APIs or SDKs.
  • Ensure that the order of presentation does not prioritize Windows/PowerShell over cross-platform tools; consider presenting Azure CLI first or in parallel.
  • Clarify in the prerequisites or relevant sections that all steps can be performed from any OS using the Azure portal or Azure CLI.
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-08-24 00: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 (GUI) and Azure PowerShell, but does not include equivalent command-line examples for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell examples are presented as the only scripting/automation option, which may disadvantage users on non-Windows platforms. There is no mention of Linux-native tools or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all automation/scripted steps (e.g., adding/removing custom domains).
  • Explicitly mention that Azure CLI is cross-platform and provide Bash-compatible command samples.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS, but also offer native Bash/CLI alternatives.
  • Ensure that all code blocks and automation steps have parity between PowerShell and CLI, so Linux users are not required to use PowerShell.
  • Consider including a table or tabs for 'Azure CLI', 'PowerShell', and 'Portal' for each procedural section.
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-08-21 00:01
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 and Azure PowerShell, but does not include equivalent examples for Linux/Unix command-line users (e.g., Azure CLI or Bash). The only command-line automation shown is via PowerShell, which is primarily a Windows tool, though it is available cross-platform. There are no Bash, Azure CLI, or shell script examples, and no mention of Linux-native tools or workflows.
Recommendations
  • Add Azure CLI examples for all tasks currently demonstrated with PowerShell, including adding and removing custom domains.
  • Include Bash or shell script snippets where appropriate, especially for users managing DNS or CDN resources from Linux/macOS environments.
  • Explicitly mention that PowerShell is available cross-platform, but provide parity with Azure CLI to serve Linux-first users.
  • Consider including a table or section comparing how to accomplish the same tasks in PowerShell, Azure CLI, and the Azure portal.
  • Reference Linux-native DNS management tools (e.g., dig, nsupdate) for DNS verification steps, where relevant.
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-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for performing tasks via the Azure Portal (web UI) and Azure PowerShell, but does not include equivalent command-line examples for Linux users (e.g., Azure CLI or Bash). PowerShell is a Windows-centric tool, and its exclusive use in scripting examples may disadvantage Linux or cross-platform users. There are no references to Linux-native tools or shell environments, and no Azure CLI examples are provided.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all scripted operations, such as adding or removing custom domains.
  • Include Bash shell command examples where appropriate, especially for DNS record management or validation.
  • Explicitly mention that PowerShell Core is cross-platform if PowerShell is to be retained, but still provide Azure CLI as the primary or an equal alternative.
  • Ensure that any references to tools or commands are not Windows-specific unless absolutely necessary, and always provide Linux/macOS equivalents.
  • Consider reordering examples to present cross-platform (CLI) options before or alongside Windows-specific tools.
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-08-18 00: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 (GUI) and Azure PowerShell, but does not include equivalent examples for Linux users, such as Azure CLI or Bash scripts. The PowerShell examples are prominent, and there is no mention of cross-platform command-line alternatives, which may disadvantage users on Linux or macOS.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell Core is available cross-platform, if PowerShell examples are retained, and clarify compatibility.
  • Provide Bash script examples for DNS record creation and verification, especially for users managing DNS outside Azure.
  • Ensure that all steps and screenshots are not Windows-specific and clarify when instructions are OS-agnostic.
  • Consider a 'Choose your platform' tab structure (Portal, PowerShell, Azure CLI, Bash) to improve parity and user experience.
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-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
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.
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-07-13 21:37
Reviewed by: Unknown
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 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'.
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-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 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.
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-07-08 04:23
Reviewed by: Unknown
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 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.
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-07-08 04:23
Reviewed by: Unknown
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 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.
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-07-08 04:23
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 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.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →