Document Details
Enable Api Analysis Linting
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
Summary:
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently lists Bash first and then PowerShell, which is a positive sign for parity. However, there is a subtle Windows bias in the use of Visual Studio Code (a cross-platform tool but often associated with Windows) and the Azure Functions extension, and in the use of PowerShell-specific syntax in all CLI examples. The documentation does not provide Linux-specific troubleshooting, nor does it mention Linux-native tools or editors. All portal-based instructions assume the Azure Portal web UI, which is platform-neutral. There are no exclusive Windows tools, but the presence of PowerShell syntax throughout and the lack of explicit Linux-native guidance (such as using Vim, nano, or Linux package managers) suggest a mild Windows/PowerShell bias.
Recommendations:
- Explicitly state that Visual Studio Code and the Azure Functions extension are fully supported on Linux and macOS, and provide links to installation instructions for those platforms.
- Add Linux-native editor alternatives (e.g., Vim, nano) for editing YAML files, or at least mention that any editor can be used.
- Include troubleshooting steps or notes for common Linux-specific issues (such as file permissions or dependency installation).
- Where PowerShell syntax is provided, ensure that Bash syntax is equally prominent and clarify which is which.
- Consider including at least one example of running the function app locally on Linux, or mention that all steps are cross-platform.
- If referencing the Azure CLI, note that it is fully supported on Linux and provide a link to Linux installation instructions.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
| 2025-07-09 23:22 | #6 | cancelled | ✅ Clean |
Flagged Code Snippets
1. Get the resource ID of your API center. Substitute `<apic-name>` and `<resource-group-name>` with your API center name and resource group name.