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 76-91 of 91 flagged pages
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-terraform.md ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell examples are presented immediately after the CLI examples and use Windows-centric syntax (e.g., `$variable=$(...)`, backticks for line continuation). There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific patterns or tools. The CLI examples are technically cross-platform, but the PowerShell section and its syntax are Windows-focused.
Recommendations
  • Add explicit bash/Linux shell examples for verification steps, showing how to run the same commands in a Linux environment.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands using bash syntax (e.g., export variables, use \ for line continuation).
  • If PowerShell is included, consider also including bash equivalents for each step, especially for variable assignment and command execution.
  • Mention cross-platform compatibility in the prerequisites and verification sections, guiding users on both Windows and Linux.
  • Avoid using Windows-specific syntax (e.g., backticks for line continuation) without providing Linux alternatives.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-create-new-endpoint.md ...docs/blob/main/articles/cdn/cdn-create-new-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by omitting CLI instructions that would be relevant for Linux users (such as Azure CLI or Bash). There is no mention of Linux tools, nor are cross-platform command-line alternatives provided.
Recommendations
  • Add Azure CLI examples for each step, showing how to create CDN profiles and endpoints from the command line.
  • Explicitly mention that the Azure CLI can be used on Linux, macOS, and Windows, and provide installation instructions or links.
  • Where possible, provide Bash script snippets for automation, highlighting cross-platform compatibility.
  • Ensure that any resource cleanup steps include CLI commands (e.g., az group delete) in addition to portal instructions.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-terraform.md ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 verification steps, but the PowerShell example is given equal prominence and detail as the CLI example. There is no explicit mention of Linux-specific patterns, nor are Linux shell commands (e.g., bash) highlighted. The use of PowerShell, which is traditionally associated with Windows, may suggest a Windows bias, especially since no Linux-specific verification workflow or troubleshooting is mentioned.
Recommendations
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide bash-specific examples where appropriate.
  • Clarify that PowerShell Core is available on Linux, or provide bash alternatives for verification steps.
  • Add troubleshooting notes or links for common Linux-specific issues when using Terraform and Azure CLI.
  • Ensure that any file creation or directory navigation steps use platform-neutral language or provide both Windows and Linux command examples (e.g., mkdir, cd, touch).
  • Consider listing Azure CLI (bash) examples before PowerShell to avoid implicit Windows-first ordering.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/create-profile-endpoint-terraform.md ...main/articles/cdn/create-profile-endpoint-terraform.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
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 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.
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-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
CDN Get started with the Azure CDN SDK for Node.js .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Low Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for 'Get started with the Azure CDN SDK for Node.js' demonstrates minor Windows bias by recommending Visual Studio Code (a Microsoft tool popular on Windows, though cross-platform) as the editor and referencing Visual Studio Code's launch.json for debugging and passing command-line parameters. The only explicit tool recommendation is for Visual Studio Code, and the tip about debugging is tailored to its configuration, which may be less familiar to Linux/macOS users. No Linux/macOS-specific editors, consoles, or debugging instructions are mentioned. However, all code and commands are cross-platform, and there are no PowerShell-only or Windows-only steps.
Recommendations
  • Mention alternative editors and debuggers commonly used on Linux/macOS, such as Vim, Emacs, Sublime Text, or JetBrains WebStorm.
  • Provide instructions for running and debugging the Node.js application from the command line on Linux/macOS, including how to pass command-line parameters.
  • Clarify that Visual Studio Code is available cross-platform, or provide links to setup guides for Linux/macOS.
  • Add a brief note or example showing how to run the Node.js script directly from a Bash or Terminal shell (e.g., `node app.js list profiles`).
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and the Portal. While Azure CLI is cross-platform and presented first, PowerShell examples are included in detail, which are primarily relevant for Windows users. There are no explicit Linux/macOS-specific instructions or notes, and PowerShell is presented as a main method rather than as a Windows-specific alternative.
Recommendations
  • Clarify that PowerShell instructions are primarily for Windows users and note cross-platform alternatives.
  • Add explicit notes or sections for Linux/macOS users, confirming that Azure CLI is fully supported and preferred for those platforms.
  • Consider including bash script examples or mentioning shell environments for Linux/macOS users.
  • If PowerShell Core is supported on Linux/macOS, clarify compatibility and installation steps.
GitHub Create Pull Request
CDN Get started with the Azure CDN SDK for Node.js .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by recommending Visual Studio Code as the text editor and debugger, and by providing tips specifically for configuring launch.json in Visual Studio Code. There is no mention of Linux/macOS-specific editors, shells, or debugging workflows. However, all code and commands are cross-platform and do not rely on Windows-only tools or patterns. The only reference to PowerShell is in the 'Next Steps' section, which is not central to the tutorial.
Recommendations
  • Explicitly mention that all steps and commands work on Linux and macOS, not just Windows.
  • Include alternative editor/debugger suggestions for Linux/macOS users (e.g., Vim, Emacs, JetBrains IDEs).
  • Provide tips for running and debugging the Node.js application in Linux/macOS terminals and IDEs.
  • Clarify that Visual Studio Code is cross-platform and works on Linux/macOS as well.
  • Balance the 'Next Steps' section by linking to Linux/macOS CLI guides (e.g., Azure CLI) alongside PowerShell.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Low Priority View Details →
Scanned: 2026-01-14 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 examples are included as a primary tab alongside Azure CLI, which can be interpreted as a Windows-first approach. The PowerShell section uses Windows-style variable assignment and command syntax, which may not be directly usable on Linux/macOS. However, the CLI instructions are cross-platform and appear first, and there are no steps that are Windows-only or that require Windows-specific tools.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash or shell script examples where relevant, especially for variable assignment and command usage.
  • If PowerShell is included, clarify that it is available cross-platform, or provide Bash equivalents for all PowerShell examples.
  • Ensure that any file creation or directory navigation steps use neutral or cross-platform commands (e.g., 'mkdir', 'cd') or provide both Windows and Linux/macOS variants if needed.
GitHub Create Pull Request
CDN Quickstart: Create a profile and endpoint - Resource Manager template .../main/articles/cdn/create-profile-endpoint-template.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions using Azure CLI, PowerShell, and Portal. While Azure CLI is cross-platform and presented first, PowerShell examples are included throughout, which are primarily relevant for Windows users. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash scripting or Linux-native tools. The presence of PowerShell instructions may imply a slight Windows bias, but the CLI instructions are sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Add explicit Bash shell examples (if any differences exist) or note that CLI commands are platform-agnostic.
  • Consider mentioning that PowerShell Core is available cross-platform, or clarify if examples are for Windows PowerShell only.
  • Provide troubleshooting notes for Linux/macOS users if there are known platform-specific issues.
GitHub Create Pull Request
CDN Get started with the Azure CDN SDK for Node.js .../azure-docs/blob/main/articles/cdn/cdn-app-dev-node.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by recommending Visual Studio Code as the editor and referencing the launch.json configuration for debugging, which is most commonly associated with Windows environments. However, all code and command-line instructions are cross-platform, and there are no Windows-only tools or examples. The only mention of PowerShell is in a 'Next Steps' link, not in the main tutorial. There are no missing Linux/macOS examples, and the instructions are generally applicable to all platforms.
Recommendations
  • Explicitly mention that Visual Studio Code and Node.js are available on Linux and macOS, and provide links or brief instructions for setting up the environment on those platforms.
  • Include a note or example showing how to run the Node.js application from a Linux/macOS terminal, to reinforce cross-platform compatibility.
  • If referencing launch.json, clarify that this configuration applies to Visual Studio Code on all platforms, not just Windows.
  • Consider adding alternative editor suggestions (e.g., Vim, Sublime Text, Atom) to avoid implying a Windows-centric workflow.
GitHub Create Pull Request
CDN Quickstart: Create an Azure CDN profile and endpoint using Terraform ...main/articles/cdn/create-profile-endpoint-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell examples use Windows-style variable assignment and syntax, and there is no explicit mention or example for Bash/Linux shell users beyond the Azure CLI tab. The PowerShell section is present and could be seen as Windows-centric, especially as it uses Windows-specific tools and syntax, while Linux/macOS users are expected to use only the CLI. There are no explicit Linux/macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add explicit Bash/Linux/macOS tabs or notes where relevant, especially for variable assignment and command usage.
  • Clarify that Azure CLI examples are cross-platform and can be run on Windows, Linux, or macOS.
  • Consider adding a note or section for common Linux/macOS shell environments, especially for users unfamiliar with CLI vs PowerShell distinctions.
  • Ensure parity in troubleshooting and cleanup instructions for both Windows (PowerShell) and Linux/macOS (Bash/CLI) users.
GitHub Create Pull Request
CDN https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/cdn-sas-storage-support.md ...docs/blob/main/articles/cdn/cdn-sas-storage-support.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
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
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
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
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →