API Center
108
Total Pages
92
Linux-Friendly Pages
16
Pages with Bias
14.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
41 issues found
Showing 26-41 of 41 flagged pages
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 given for every step and are formatted with Windows-specific syntax. Bash examples are present, but PowerShell versions are shown immediately after, suggesting parity but also a slight Windows-first bias. There are no missing Linux examples, but the PowerShell formatting and variable usage may create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell sections, possibly using tabs or headings for each platform.
- Ensure Bash examples are shown first, or alternate the order to avoid Windows-first bias.
- Add brief notes clarifying which example is for which OS/shell.
- Consider including macOS-specific notes if there are any platform differences.
- Review variable usage and syntax to ensure Bash examples are fully compatible with Linux/macOS environments.
Create Pull Request
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 equally alongside CLI, and references to Azure PowerShell requirements are present. There is a slight Windows-first bias in the ordering and inclusion of PowerShell, which is primarily a Windows tool, though Azure CLI is cross-platform and shown first in the deployment section. No Linux/macOS-specific instructions or troubleshooting are provided.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, such as file path conventions and shell usage.
- Provide troubleshooting tips for common Linux/macOS issues (e.g., file permissions, uploading files to Cloud Shell).
- Consider including Bash script examples or links to Linux/macOS setup guides.
- Mention that PowerShell Core is available cross-platform, if relevant, and clarify differences.
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 Azure CLI examples for both Bash and PowerShell, but PowerShell syntax is consistently shown first. There are no explicit Linux/macOS-specific instructions or screenshots, and some tooling references (Visual Studio Code, Azure portal) are platform-neutral but lack mention of Linux alternatives or considerations. The documentation does not mention any Linux-specific issues or troubleshooting, and the overall flow assumes parity but subtly prioritizes Windows/PowerShell users.
Recommendations
- Alternate Bash and PowerShell examples so that Bash (Linux/macOS) is shown first in some sections.
- Explicitly mention Linux/macOS compatibility for all tools (e.g., Visual Studio Code, Azure CLI, Azure Functions extension).
- Add Linux/macOS-specific troubleshooting tips or notes where relevant (e.g., file permissions, environment setup).
- Include screenshots or instructions from Linux/macOS environments, not just the Azure portal.
- Clarify that all CLI commands work equally on Linux/macOS, and highlight any differences if they exist.
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 consistently lists PowerShell examples immediately after bash, and sometimes refers to PowerShell formatting explicitly. There is a slight Windows-first bias in the ordering and explicit mention of PowerShell, but Linux/macOS users are not blocked from completing any tasks, as bash examples are present for all commands.
Recommendations
- Explicitly state Linux/macOS compatibility at the top, including supported shells.
- Alternate the order of bash and PowerShell examples, or group them together to avoid implicit prioritization.
- Add a note clarifying that all examples work on Linux/macOS and Windows, and that bash examples are suitable for Linux/macOS.
- Where variable syntax differs, consider providing a table or clear guidance rather than duplicating examples.
- Include troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path formats) if relevant.
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 given equal prominence and are explicitly formatted, which may suggest a slight Windows bias. The use of PowerShell-specific syntax and formatting can create friction for Linux/macOS users. However, Bash examples are present for all CLI commands, and no Windows-only tools are required.
Recommendations
- Clearly indicate which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows), using tabs or headings.
- Provide a brief note explaining the difference between Bash and PowerShell syntax for cross-platform users.
- Consider listing Bash examples first, as Bash is the default shell on most Linux/macOS systems.
- Ensure that all steps and commands are fully functional on Linux/macOS, and explicitly mention any platform-specific caveats.
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 metadata and prerequisites. There is no explicit Linux bias, but the presence of PowerShell examples and references may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool (though cross-platform now). The CLI example is shown first, which helps mitigate bias, but the documentation could better clarify Linux/macOS workflows and avoid unnecessary PowerShell emphasis.
Recommendations
- Explicitly state that Azure CLI works natively on Linux/macOS and is the recommended cross-platform tool.
- Clarify that PowerShell is available cross-platform, but CLI is more common for Linux/macOS.
- Add a note or section for Linux/macOS users, highlighting CLI usage and file handling specifics (e.g., uploading files in Cloud Shell, file paths).
- Review metadata and custom tags to ensure they do not overemphasize PowerShell.
- Consider removing or de-emphasizing PowerShell examples unless there is a clear use case for them.
API Center
Synchronize APIs from Azure API Management instance
...articles/api-center/synchronize-api-management-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 claims Azure CLI examples work in both PowerShell and bash, the only explicit shell distinction is for variable syntax, and no Linux/macOS-specific examples or screenshots are provided. The portal instructions and CLI commands are platform-neutral, but the mention of PowerShell before bash and lack of explicit Linux/macOS guidance or troubleshooting tips suggest a subtle Windows-first approach.
Recommendations
- Provide explicit bash and PowerShell command examples where syntax differs, and show both side-by-side.
- Include screenshots or instructions for Linux/macOS environments where relevant (e.g., Azure CLI installation, managed identity configuration).
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, CLI path).
- Ensure variable syntax examples are shown for both shells, not just mentioned.
- Consider listing bash examples before PowerShell or alternating order.
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, and PowerShell-specific formatting is explicitly called out. There is no mention of Linux/macOS-specific considerations, nor is there any indication of prioritizing cross-platform parity. The presence of PowerShell examples may suggest a slight Windows bias, but Bash examples are present and complete.
Recommendations
- Clarify that Bash examples work on Linux/macOS and most Windows environments (e.g., WSL, Git Bash).
- Explicitly state cross-platform compatibility for Azure CLI commands.
- Consider showing Bash examples first, as Bash is the default shell on Linux/macOS.
- Add notes for users on how to run Azure CLI on different platforms (Linux, macOS, Windows).
- If PowerShell examples are included, also mention alternative shells for Linux/macOS users.
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 instructions for deploying the Bicep file, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is referenced in metadata and prerequisites. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples of using Bash or other native Linux tools. The Azure CLI example is cross-platform, but the presence and emphasis on PowerShell may create a perception of Windows bias.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- Add explicit notes or examples for Linux/macOS users, such as using Bash or zsh in Azure Cloud Shell or local terminals.
- Reorder examples to present Azure CLI first, emphasizing its cross-platform nature.
- Remove or de-emphasize PowerShell unless there are Windows-specific steps.
- Include troubleshooting notes for Linux/macOS users if there are known issues (e.g., file paths, permissions).
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 consistently shown immediately after Bash, with explicit formatting notes. There is a slight bias towards Windows/PowerShell users, as the PowerShell examples are given equal prominence and special formatting, whereas Linux/macOS users are expected to use Bash. No Linux-specific tools or patterns are missing, but the ordering and explicit PowerShell support indicate a mild Windows-first approach.
Recommendations
- Clarify that Bash examples apply to Linux/macOS and WSL users, and PowerShell examples are for Windows users.
- Consider listing Bash (Linux/macOS) examples first, or grouping examples by platform.
- Explicitly mention cross-platform compatibility and provide guidance for macOS users if there are any platform-specific caveats.
- Add a note that Azure CLI works identically on all platforms, and that users should choose the shell that matches their environment.
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 given immediately after Bash in every case, and the PowerShell formatting is explicitly called out. There is no explicit Linux/macOS example section, and the structure may imply a slight preference for Windows/PowerShell users.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Add a note at the top of the CLI section specifying which examples are for which platforms.
- Consider providing a dedicated tab or section for Linux/macOS users if platform-specific nuances exist.
- Ensure parity in explanations for both Bash and PowerShell, and avoid implying that PowerShell is the default or preferred shell.
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 explicit notes mention PowerShell compatibility. There is a slight Windows-first bias in the ordering and inclusion of PowerShell examples, but Linux/macOS users are not blocked from completing any tasks. All tooling (Azure CLI, azd, VS Code) is cross-platform, and bash examples are present throughout.
Recommendations
- Alternate the order of bash and PowerShell examples, or group them in tabs so neither is prioritized.
- Explicitly mention Linux/macOS compatibility for all steps, especially for local testing and deployment.
- Add a short section or note confirming that all tools (Azure CLI, azd, VS Code) are supported on Linux/macOS.
- Where possible, provide screenshots or terminal output from Linux/macOS environments as well as Windows.
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 sometimes with additional formatting notes. There is a slight Windows-first bias in the explicit inclusion and formatting of PowerShell examples, which may suggest a prioritization of Windows users. However, bash examples are present for all commands, and there are no Windows-only tools or steps.
Recommendations
- Present bash and PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
- Explicitly mention macOS compatibility where relevant, as only bash and PowerShell are referenced.
- Add a note clarifying that all Azure CLI commands work equally on Linux/macOS and Windows, and that bash examples apply to both Linux and macOS.
- Consider including zsh or other popular Linux/macOS shells if relevant.
API Center
Synchronize APIs from Azure API Management instance
...articles/api-center/synchronize-api-management-apis.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates minor Windows bias by mentioning that Azure CLI commands can run in PowerShell or bash, but lists PowerShell first and refers to variable syntax differences. There are no explicit Linux/macOS examples, and no Linux-specific tools or instructions are provided. However, the CLI commands themselves are cross-platform and can be run in bash, mitigating most friction for non-Windows users.
Recommendations
- Provide explicit bash and PowerShell command examples where variable syntax differs, ensuring Linux/macOS users see relevant instructions.
- Add notes or sections clarifying any OS-specific prerequisites or behaviors, such as installation steps for the Azure CLI on Linux/macOS.
- Avoid listing PowerShell before bash unless there is a technical reason; consider alternating or listing bash first to balance representation.
- Include screenshots or references to Linux/macOS environments where appropriate.
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 deployment examples for both Azure CLI and Azure PowerShell, but PowerShell is given equal prominence to CLI and is mentioned in prerequisites and examples. There is a slight Windows-first bias as PowerShell is a Windows-centric tool, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. However, Azure CLI is cross-platform and shown first in the example tabs, mitigating the bias.
Recommendations
- Clarify that Azure CLI commands work natively on Linux/macOS and Windows.
- Add explicit Bash shell examples for Linux/macOS users, especially for file handling and environment setup.
- Mention that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Ensure that instructions for uploading files in Azure Cloud Shell are clear for both Windows and Linux/macOS users.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/agent-to-agent-overview.md
...ob/main/articles/api-center/agent-to-agent-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or demonstrate parity for Linux or cross-platform usage. There are no explicit Windows or PowerShell examples, but the absence of any mention of Linux tools, commands, or considerations may leave Linux users uncertain about support or usage patterns.
Recommendations
- Add explicit statements clarifying that the agent registry and related features are platform-agnostic, or specify supported platforms.
- Provide examples or references for registering and managing agents using both Windows and Linux environments, if applicable.
- If any CLI or scripting is involved in agent registration or management, include both PowerShell (Windows) and Bash (Linux/macOS) examples.
- Mention any platform-specific prerequisites or considerations to ensure Linux users are equally informed.