API Center
60
Total Pages
43
Linux-Friendly Pages
17
Pages with Bias
28.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
186 issues found
Showing 176-186 of 186 flagged pages
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and the text explicitly mentions PowerShell as a supported shell. There are no Linux-specific tools or workflows discussed, but Bash is included throughout. Visual Studio Code is recommended for all platforms, and no Windows-only tools are required. However, the ordering and explicit mention of PowerShell may subtly prioritize Windows users.
Recommendations
- Alternate the order of Bash and PowerShell examples, or provide Bash examples first to reflect the prevalence of Linux/macOS in cloud development.
- Explicitly mention support for Linux/macOS environments in prerequisites and examples.
- Add a short section confirming that all steps are cross-platform and provide troubleshooting tips for Linux/macOS users if relevant.
- Where possible, include screenshots or instructions from Linux/macOS environments (e.g., VS Code on Ubuntu, Azure CLI in a Linux terminal).
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are included for every step and are formatted and labeled explicitly. Bash examples are present, but PowerShell is given equal or slightly more prominence, which may suggest a Windows bias. There are no Linux-specific tools or patterns mentioned, but the presence of PowerShell examples throughout may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clearly label Bash examples as the default for cross-platform use, and PowerShell as optional for Windows users.
- Provide explicit instructions or notes for Linux/macOS users, confirming that Bash examples are fully supported.
- Consider placing Bash examples first, with PowerShell as a secondary tab or section.
- Add a note clarifying that Azure CLI works natively in Bash on Linux/macOS and that PowerShell examples are for Windows users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell (Windows) examples are shown immediately after Bash in every step, and PowerShell-specific syntax is explicitly highlighted. There is no mention of Linux/macOS-specific considerations, nor are Bash examples prioritized or explained in more detail. The presence of PowerShell examples throughout may signal a Windows-first approach.
Recommendations
- Clearly indicate which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows), possibly using tabs or headings.
- Provide parity in explanations for both Bash and PowerShell, including notes on platform differences if any.
- Consider showing Bash (Linux/macOS) examples first, or defaulting to Bash unless there is a Windows-specific need.
- Add a brief note confirming that all CLI commands work cross-platform and clarify any OS-specific caveats.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-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 deploying the Bicep file. However, Azure PowerShell is highlighted as a primary option alongside CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash or shell scripting, which are common on non-Windows platforms. The order of presentation is mostly neutral, but the inclusion of PowerShell as a main path may create mild friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add explicit Bash/shell examples for common tasks, such as file copying or uploading in Cloud Shell.
- Mention that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Consider listing CLI examples before PowerShell to reinforce cross-platform parity.
- Add a note about platform compatibility for each tool.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides Azure CLI examples for both bash and PowerShell throughout, but PowerShell examples are consistently shown immediately after bash, and are explicitly formatted for Windows users. There is a slight Windows-first bias in the order and presence of PowerShell examples, which may suggest Windows as a primary platform. However, all CLI commands are cross-platform and Linux/macOS users are not blocked from completing any tasks.
Recommendations
- Explicitly state that all Azure CLI commands work equally on Linux, macOS, and Windows.
- Alternate the order of bash and PowerShell examples, or group them together to avoid implicit prioritization.
- Add a short section at the beginning clarifying platform parity and noting any platform-specific caveats if they exist.
- Ensure that any referenced file paths or environment variables use platform-neutral notation or provide both formats.
API Center
Synchronize APIs from Amazon API Gateway - Azure API Center
...in/articles/api-center/synchronize-aws-gateway-apis.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates mild Windows bias. While it states that Azure CLI commands can run in both PowerShell and bash, examples and screenshots are portal-centric (Windows-oriented), and CLI examples use syntax compatible with both but do not show explicit bash/Linux alternatives. There is no mention of Linux-specific tools or workflows, and Windows/PowerShell is referenced first when discussing command execution.
Recommendations
- Provide explicit bash/Linux shell examples alongside PowerShell, especially where variable syntax or command structure differs.
- Include screenshots or instructions for Azure CLI usage in Linux/macOS terminals.
- Clarify any platform-specific prerequisites or differences, such as authentication or environment setup steps for Linux/macOS.
- Avoid listing Windows/PowerShell first by default; alternate order or present both equally.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell (Windows) examples are given equal prominence and appear immediately after Bash. The PowerShell examples are explicitly labeled and formatted, which may suggest a slight preference for Windows users. There are no Linux-specific tools or patterns mentioned, but the Bash examples do cover Linux/macOS users. No critical functionality is missing for Linux/macOS users.
Recommendations
- Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows.
- Consider listing Bash (Linux/macOS) examples before PowerShell (Windows) examples to reflect platform prevalence in cloud/CLI usage.
- Add a brief note clarifying that Bash examples work on Linux/macOS and WSL, while PowerShell examples are for Windows.
- Ensure variable naming and command formatting are consistent and correct for each platform (e.g., $apimID in PowerShell example should match earlier variable names).
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-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 deploying the Bicep file, but PowerShell is featured prominently and referenced in metadata and prerequisites. Azure PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a Windows-first approach. However, the CLI examples are present and shown before PowerShell, and no critical steps are Windows-only.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Add explicit notes or examples for Linux/macOS users, such as file path conventions or shell usage.
- Consider de-emphasizing Azure PowerShell in metadata and prerequisites, or balance with Bash/Linux shell references.
- Ensure that all instructions (such as uploading files in Cloud Shell) are platform-agnostic or include platform-specific guidance.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown after bash, and some command blocks are labeled 'PowerShell syntax' rather than 'Linux/macOS'. There are no explicit Linux/macOS-specific instructions, and tooling references (Visual Studio Code, Azure CLI, Azure Developer CLI) are cross-platform but the portal screenshots and instructions are Windows-centric. There is no mention of Linux-specific editors, shell environments, or troubleshooting for non-Windows platforms.
Recommendations
- Clearly indicate that both bash and PowerShell examples work on Linux, macOS, and Windows, and avoid labeling PowerShell as the only alternative to bash.
- Add explicit Linux/macOS instructions or troubleshooting notes where platform differences may occur (e.g., file paths, environment setup).
- Include screenshots or references for Linux/macOS users (e.g., using VS Code on Ubuntu, Azure CLI in a Linux terminal).
- Where possible, provide parity in examples, such as showing how to run the function app locally on Linux/macOS.
- Avoid assuming the Azure portal is accessed from Windows; clarify that it is web-based and platform-agnostic.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell (Windows) examples are always shown immediately after Bash, and PowerShell-specific formatting is explicitly called out. There are no macOS-specific notes or examples, and the CLI instructions are not explicitly marked as cross-platform. The portal instructions are platform-neutral, but the CLI section subtly prioritizes Windows by including PowerShell syntax and comments.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add a note that Bash examples apply to Linux/macOS terminals and Windows WSL/Git Bash.
- Consider showing Bash examples first, or alternating the order.
- Explicitly mention macOS compatibility where relevant.
- If PowerShell examples are included, consider also including zsh/fish examples or notes for macOS users.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence and is mentioned in prerequisites and example sections. There is a slight Windows bias as PowerShell is traditionally a Windows tool, and its inclusion may suggest Windows as a primary platform. However, Azure CLI is cross-platform and shown first in the example tabs, and no Windows-only tools or steps are present.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid implying Windows exclusivity.
- Add explicit notes or examples for Linux/macOS users, such as file path conventions or shell commands for uploading files in Azure Cloud Shell.
- Ensure that any references to uploading or saving files (e.g., 'upload the file to your home directory') include platform-specific guidance if needed.
- Consider including Bash or other Linux-native shell examples if relevant.