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 26-33 of 33 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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but PowerShell is given equal prominence and is included as a dedicated tab, which may indicate a slight Windows bias. There are no explicit Linux shell examples (e.g., bash), and the CLI instructions use variable assignment syntax compatible with bash but do not clarify Linux usage. PowerShell is featured as a first-class option, which may not be relevant for Linux users. No Windows-specific tools are mentioned, but the lack of explicit Linux shell instructions and the inclusion of PowerShell suggest a mild Windows-first orientation.
Recommendations
- Add explicit bash/Linux shell examples for verification steps, clarifying compatibility and usage on Linux/macOS.
- Clearly indicate which instructions are cross-platform and which are Windows-specific.
- Consider providing a 'Linux/macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to ensure parity.
- Mention that Azure CLI is available on all platforms and provide installation guidance for Linux/macOS if appropriate.
- Review variable assignment syntax to ensure it is correct for both bash and PowerShell, or provide separate examples.
Create Pull Request
CDN
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cdn/tier-migration.md
...cs/azure-docs/blob/main/articles/cdn/tier-migration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references updating DevOps scripts to use the new API, Azure PowerShell module, and CLI commands, but only mentions PowerShell (a Windows-centric tool) explicitly. There are no Linux-specific tools, commands, or examples provided, nor is there mention of Bash, Azure CLI on Linux, or cross-platform scripting. The documentation assumes familiarity with Windows tooling and does not provide parity for Linux users.
Recommendations
- Explicitly mention Azure CLI (az) commands alongside PowerShell, and provide examples for both.
- Include Bash or shell scripting examples for common migration tasks.
- Clarify that migration can be performed from any OS, and link to cross-platform tooling documentation.
- Ensure that any references to scripting or automation cover both Windows and Linux environments equally.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by recommending Visual Studio Code (a Microsoft product popular on Windows, though cross-platform) and mentioning PowerShell management in the 'Next Steps' section without referencing Linux/macOS CLI alternatives. There are no explicit Linux/macOS examples or mentions of platform-specific setup, and Windows-centric tools are referenced before Linux equivalents (if any). However, the Node.js SDK usage itself is cross-platform, and most instructions are generic.
Recommendations
- Add explicit instructions or tips for running the Node.js application on Linux and macOS, such as using the terminal and passing command-line arguments.
- Mention cross-platform editors (e.g., VS Code, Atom, Sublime) and clarify that VS Code is available on Linux/macOS.
- In the 'Next Steps' section, include links to Azure CLI or Bash management guides for CDN resources, not just PowerShell.
- Provide screenshots or terminal output examples from Linux/macOS environments alongside Windows examples.
- Clarify that all steps are platform-agnostic unless otherwise noted.
CDN
Quickstart: Create a profile and endpoint - Resource Manager template
.../main/articles/cdn/create-profile-endpoint-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented before Linux-native alternatives like Bash scripting. There are no explicit Linux/macOS-specific instructions or examples, and PowerShell is referenced without noting its limited support on non-Windows platforms. No Linux-specific tools or patterns are mentioned.
Recommendations
- Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is primarily a Windows tool (with limited cross-platform support).
- Consider providing Bash script examples alongside Azure CLI, especially for Linux/macOS users.
- Explicitly mention that Azure CLI is the recommended cross-platform tool for deployment.
- If PowerShell is included, note its cross-platform status and any limitations for non-Windows users.
- Ensure that Linux/macOS users are guided to install and use Azure CLI, and provide troubleshooting tips for common platform-specific issues.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by recommending Visual Studio Code (a Microsoft product popular on Windows) as the editor and referencing PowerShell management in the 'Next Steps' section, without mentioning Linux/macOS equivalents or alternatives. There are no explicit Linux/macOS examples, but the Node.js instructions are generally cross-platform and do not rely on Windows-specific tools or patterns.
Recommendations
- Add explicit notes confirming that all steps work on Linux and macOS, and mention any platform-specific caveats if present.
- Include alternative editor suggestions (e.g., Vim, Sublime Text, Atom) to avoid implying Visual Studio Code is required.
- In the 'Next Steps' section, provide links to CLI-based management (e.g., Azure CLI) and documentation for Linux/macOS users, not just PowerShell.
- If screenshots or instructions reference Windows paths or UI, add Linux/macOS equivalents.
- Clarify that npm and Node.js commands are cross-platform.
CDN
Quickstart: Create a profile and endpoint - Resource Manager template
.../main/articles/cdn/create-profile-endpoint-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after the CLI in each section. There are no Linux/macOS-specific instructions or notes, and no mention of Bash or shell scripting alternatives. The PowerShell examples may be less relevant for Linux/macOS users, and their inclusion without clarification could suggest a Windows bias.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for non-Windows users.
- Add explicit notes or sections for Linux/macOS users, confirming that all steps can be completed using Azure CLI in Bash or other shells.
- Consider moving PowerShell examples to a separate section or after CLI/portal instructions, or label them as 'Windows/PowerShell users only'.
- If relevant, provide Bash script equivalents for automation.
- Add a brief note about installing Azure CLI on Linux/macOS, if not already covered in prerequisites.
CDN
Quickstart: Create a profile and endpoint - Bicep
...lob/main/articles/cdn/create-profile-endpoint-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS shell alternatives (e.g., Bash), nor are there any Linux-specific instructions or notes. The CLI examples are cross-platform, but the documentation does not clarify this, and PowerShell is presented as an equivalent option, which may confuse Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are recommended for cross-platform use.
- Add notes indicating that Azure PowerShell is primarily for Windows users, and suggest Bash or shell for Linux/macOS users.
- Consider showing CLI examples first, as they are cross-platform, and move PowerShell examples to a secondary position or an 'alternative for Windows users' section.
- Explicitly mention that no additional steps are required for Linux/macOS users when using Azure CLI.
- If relevant, provide instructions for installing Azure CLI on Linux/macOS.
CDN
Quickstart: Create an Azure CDN profile and endpoint using Terraform
...main/articles/cdn/create-profile-endpoint-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell section is given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. There is no explicit Linux/macOS bias, but the presence of PowerShell examples may suggest a slight Windows bias. However, the Azure CLI examples are cross-platform and shown first, mitigating the impact.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend it as the default for cross-platform usage.
- Add explicit notes or tabs for Linux/macOS users where relevant, especially if any commands or steps differ.
- Consider demoting PowerShell examples to a secondary position or marking them as Windows-specific.
- Ensure all file creation and shell commands use syntax compatible with bash/zsh as well as PowerShell, or provide both.