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 151-175 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
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell syntax throughout, but PowerShell examples are consistently shown after bash examples. There is a clear statement that Azure CLI commands can run in either shell, and separate examples are provided where syntax differs. No Windows-only tools or patterns are used, and Visual Studio Code is recommended as the editor, which is cross-platform. All deployment and configuration steps are accessible from Linux/macOS, and no critical functionality is Windows-only.
Recommendations
- Continue to provide both bash and PowerShell examples where syntax differs.
- Consider alternating the order of bash and PowerShell examples, or explicitly state that bash examples are shown first for consistency.
- Ensure that any screenshots or references to Visual Studio Code clarify its cross-platform support.
- If possible, include a brief note confirming Linux/macOS parity for all steps.
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. However, PowerShell examples are given alongside Bash, and in some cases, PowerShell syntax is shown first or receives special formatting. There is a mild bias toward Windows/PowerShell users, but Linux users can complete all tasks using the Bash examples.
Recommendations
- Ensure Bash examples are shown first, as Bash is the default shell for Azure CLI and most cross-platform users.
- Clearly label Bash and PowerShell sections, and avoid implying PowerShell is required unless there is a Windows-specific need.
- Consider providing macOS-specific notes if there are any unique considerations.
- Review variable naming for consistency between Bash and PowerShell examples.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but the PowerShell examples are presented immediately after each Bash example, indicating a slight Windows-first bias. The PowerShell formatting is explicitly called out, which may subtly prioritize Windows users. However, Linux users are not missing any information, and the Bash examples are present and correct.
Recommendations
- Consider explicitly labeling Bash examples as suitable for Linux/macOS and PowerShell examples for Windows, to clarify parity.
- If possible, present Bash (Linux/macOS) and PowerShell (Windows) examples side-by-side, rather than always Bash first then PowerShell.
- Add a brief note at the start of the CLI section explaining that both Bash and PowerShell are supported, and Linux/macOS users should use Bash examples.
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 mentioned alongside CLI throughout, and PowerShell examples are given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is presented as a primary option, which may create friction for Linux/macOS users unfamiliar with PowerShell. However, Azure CLI (cross-platform) is also fully supported and documented, and no Windows-only tools or patterns are used.
Recommendations
- Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell examples to reduce perceived Windows bias.
- Add a brief note clarifying that PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- Ensure prerequisites sections for Azure CLI and PowerShell are equally detailed and clear about platform compatibility.
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 presented immediately after Bash, indicating a slight Windows-first and PowerShell-heavy bias. There are no Linux-specific tools or patterns missing, but the inclusion and formatting of PowerShell examples may create minor friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell sections to help users quickly find the relevant example for their platform.
- Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows) examples to reduce perceived Windows-first bias.
- Add a note clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, improving clarity for cross-platform users.
- Ensure variable naming consistency between Bash and PowerShell examples to avoid confusion.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell versions are shown immediately after the Bash ones, and the formatting and comments explicitly call out PowerShell. This may create a perception of Windows-first bias, though Linux/macOS users are not blocked from completing the task.
Recommendations
- Clearly label Bash and PowerShell examples with headings or tabs to help users quickly find their preferred shell.
- Consider presenting Bash (Linux/macOS) and PowerShell (Windows) examples in parallel tabs or sections, rather than one after the other.
- Add a note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, to improve clarity for cross-platform users.
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
Summary
The documentation provides Azure CLI examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown after bash examples. There is no evidence of exclusive use of Windows tools, PowerShell-heavy bias, or missing Linux/macOS examples. The page is cross-platform in its approach, but bash examples are always shown first, which is a minor 'windows_first' bias (since PowerShell is primarily used on Windows, but also available on other platforms).
Recommendations
- Consider alternating the order of bash and PowerShell examples, or explicitly state that both shells are supported equally.
- Add a note clarifying that all examples work on Linux, macOS, and Windows, as long as Azure CLI is installed.
- If possible, include a table or toggle to switch between bash and PowerShell examples for improved parity and user experience.
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 shown immediately after Bash. This creates a slight Windows-first impression and emphasizes PowerShell usage, which is primarily relevant for Windows users.
Recommendations
- Clearly label Bash and PowerShell examples as 'Linux/macOS (Bash)' and 'Windows (PowerShell)' to help users identify which to use.
- Consider showing Bash examples first, as Bash is the default shell on Linux/macOS and is also available on Windows via WSL.
- Add a brief note explaining that Bash examples are suitable for Linux/macOS and Windows users using WSL, while PowerShell examples are for native Windows environments.
- Ensure variable naming and usage is consistent between examples to reduce confusion.
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 versions are shown immediately after Bash for each step, which may suggest a slight Windows-first bias. There is no mention of Linux-specific tools or workflows, but the Bash examples ensure Linux/macOS users are supported. The presence of PowerShell examples is helpful for Windows users but could be perceived as unnecessary duplication if not balanced with Linux/macOS context.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with a short note at the top of the CLI section.
- If possible, use tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make it clear which environment each example targets.
- Consider listing Bash examples first, as Azure CLI is cross-platform and Bash is the default shell on many systems.
- Add a note that Azure CLI commands work in Bash on Windows (e.g., via WSL) to further support cross-platform users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are shown immediately after Bash for every step, rather than grouping them or indicating platform parity. The PowerShell examples are labeled as 'Formatted for PowerShell', but there is no explicit mention of Linux/macOS users or guidance for Bash on those platforms. The ordering and labeling may subtly prioritize Windows/PowerShell users.
Recommendations
- Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows.
- Consider grouping examples by platform (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') rather than alternating for each command.
- Add a short note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, ensuring both user groups know which to use.
- If possible, provide a tabbed interface or clearer separation to reduce confusion.
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 and referenced in metadata and prerequisites. The page does not mention Linux/macOS-specific considerations, nor does it provide shell-specific guidance for those platforms. The order of presentation sometimes places PowerShell before or alongside CLI, which may subtly favor Windows users.
Recommendations
- Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Add notes or links for Linux/macOS users about prerequisites for Bicep and Azure CLI (e.g., installation instructions, file path conventions).
- Ensure CLI examples are shown first, as CLI is platform-agnostic.
- Clarify that PowerShell examples are primarily for Windows users, and suggest Bash or shell alternatives for Linux/macOS where 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 the PowerShell examples are shown immediately after the Bash ones, and some variable assignment syntax is specifically labeled 'Formatted for PowerShell.' This may suggest a slight preference for Windows/PowerShell users, though Linux users are not blocked from completing the task.
Recommendations
- Clearly separate Bash and PowerShell examples using tabs or callouts, so users can easily find their platform-specific instructions.
- Provide a brief note explaining which example is for which platform (Linux/macOS vs. Windows), and clarify that Bash syntax applies to Linux/macOS and PowerShell to Windows.
- Ensure that the Bash examples are complete and correct for Linux/macOS users, and consider listing Bash examples first if the majority of Azure CLI users are on Linux/macOS.
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
Summary
The documentation provides Azure CLI examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown second. There is no evidence of Windows-only tools, PowerShell-heavy bias, or missing Linux/macOS examples. All commands are cross-platform and the documentation explicitly states that commands can be run in either shell, providing syntax for both.
Recommendations
- Maintain the current parity by continuing to provide both bash and PowerShell examples.
- Consider alternating the order of examples (sometimes showing bash first, sometimes PowerShell) to avoid subtle perception of Windows-first bias.
- Explicitly mention macOS compatibility where relevant, to reassure users on that platform.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given immediately after Bash, and the formatting and comments explicitly highlight PowerShell usage, suggesting a slight preference for Windows/PowerShell environments. There is no mention of Linux-specific tools or workflows, but Bash examples are present and correct.
Recommendations
- Clarify that both Bash and PowerShell examples are equivalent and suitable for Linux/macOS and Windows, respectively.
- Consider listing Bash (Linux/macOS) examples first to reduce perceived Windows-first bias.
- Add a short note at the top of the CLI section explaining which examples are for which platforms.
- Ensure parity in explanation and troubleshooting steps for both Bash and PowerShell users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are always shown immediately after Bash, and are labeled as 'Formatted for PowerShell'. There is a minor bias in that PowerShell is given explicit formatting, but Linux/macOS users are not given additional context or troubleshooting. However, all critical steps are covered for both platforms.
Recommendations
- Clarify that the Bash examples are suitable for Linux/macOS and WSL users, and PowerShell is for Windows users.
- Consider using tabs or explicit headings for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make platform targeting clearer.
- Add a brief note about which shell to use on each platform, and mention that Azure CLI commands work cross-platform.
- Ensure variable naming is consistent between Bash and PowerShell examples to avoid confusion.
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
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and some notes clarify differences in variable syntax. There are no Windows-specific tools or patterns used, and Linux/macOS users are not blocked from completing any tasks. However, the presence of PowerShell examples alongside Bash may create a slight perception of Windows-first bias.
Recommendations
- Ensure Bash examples are shown first, as is currently done.
- Clarify in the prerequisites that Azure CLI is fully cross-platform and all examples work on Linux, macOS, and Windows.
- Consider grouping Bash and PowerShell examples together visually, or using tabs to allow users to select their shell preference.
- Explicitly mention that all commands are supported on Linux/macOS unless otherwise noted.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are shown immediately after Bash in each step, and PowerShell-specific formatting is explicitly called out. This creates a slight Windows-first impression, though Linux/macOS users are not blocked from completing the task.
Recommendations
- Clearly label Bash and PowerShell examples with headings or tabs, so users can easily find the example relevant to their platform.
- Consider presenting Bash (Linux/macOS) examples first, or in parallel tabs, to avoid implicit prioritization of Windows/PowerShell.
- Add a brief note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, to help users choose appropriately.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell (Windows) examples for Azure CLI commands, but the PowerShell examples are always shown after the Bash examples. There are no exclusive Windows tools or patterns, and Linux/macOS users are fully supported.
Recommendations
- Maintain the current approach of providing both Bash (Linux/macOS) and PowerShell (Windows) examples.
- Optionally, clarify at the top of the CLI section that both Bash and PowerShell examples are provided for user convenience.
- If possible, provide a tabbed interface or clearer separation to help users quickly find their preferred shell.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are shown immediately after Bash for every step, rather than grouping them separately or indicating platform parity. There is a slight Windows-first bias in the formatting and example presentation, but Linux users are not blocked from completing the task.
Recommendations
- Clearly label Bash and PowerShell examples with platform tags (e.g., 'Linux/macOS' and 'Windows') to help users quickly find relevant instructions.
- Consider grouping Bash and PowerShell examples under separate headings or tabs for clarity.
- Ensure that Bash examples are shown first or equally, to avoid implicit prioritization of Windows/PowerShell.
- Add a brief note clarifying that both Bash and PowerShell are supported and that users should choose the appropriate example for their platform.
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 the PowerShell examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. There is a slight bias toward Windows/PowerShell by including PowerShell-specific syntax, which is primarily relevant for Windows users. However, Bash examples are present and shown first, ensuring Linux/macOS users are not blocked.
Recommendations
- Clarify in the documentation that both Bash and PowerShell examples are provided for user convenience.
- Consider labeling the Bash examples as 'Bash (Linux/macOS)' and the PowerShell examples as 'PowerShell (Windows)' for clarity.
- If possible, group the examples under tabs (e.g., 'Bash', 'PowerShell') to make it easier for users to find the relevant syntax for their platform.
- Ensure that any PowerShell-specific variables or syntax are explained for users who may be less familiar with PowerShell.
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
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown second. There is no exclusive use of Windows tools or patterns, and Linux/macOS users are given parity in command examples and instructions.
Recommendations
- Maintain the current parity by continuing to provide both bash and PowerShell examples.
- Consider explicitly mentioning macOS compatibility alongside Linux when referencing bash shell usage.
- If future updates add troubleshooting or environment setup steps, ensure Linux/macOS instructions are included and not Windows-first.
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 sometimes with explicit 'PowerShell syntax' labels. There is a slight tendency to mention PowerShell in command notes and examples, and the phrase 'Azure CLI command examples in this article can run in PowerShell or a bash shell' puts PowerShell first. However, all core steps and tooling (Azure CLI, Azure Developer CLI, Visual Studio Code) are cross-platform, and Linux/macOS users are not blocked or disadvantaged in completing the tasks.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them together under clear headings for each shell.
- Explicitly mention Linux/macOS compatibility for all tools and steps, especially in prerequisites.
- Add a short section or note confirming that all steps are fully supported on Linux/macOS, and that Visual Studio Code and Azure CLI are cross-platform.
- Where possible, provide a single generic CLI example and refer to shell-specific variable syntax only if necessary.
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 immediately after Bash for every step, and PowerShell-specific formatting is explicitly called out. This creates a slight Windows-first impression, as Linux/macOS users are expected to use Bash, but the PowerShell examples are given equal prominence. There are no Linux-specific tools or patterns missing, and the Azure CLI is cross-platform.
Recommendations
- Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under separate tabs or headings to reduce clutter and clarify platform relevance.
- If possible, show Bash examples first, as Bash is the default shell on Linux/macOS and Azure Cloud Shell.
- Add a brief note explaining which shell to use on each platform.
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 for every step, and some variable assignment patterns (e.g., $scope=$apimID.substring(1)) are PowerShell-specific. There is a slight bias toward Windows/PowerShell users, as PowerShell examples are always present and shown alongside Bash, which is standard for Linux/macOS. However, Linux users are not blocked from completing the task, as Bash examples are provided for all steps.
Recommendations
- Clarify that Bash examples are for Linux/macOS and PowerShell for Windows, possibly with tabbed sections or explicit OS labels.
- Ensure variable naming consistency between Bash and PowerShell examples to avoid confusion (e.g., $apimID vs $apicObjID).
- Consider listing Bash (Linux/macOS) examples before PowerShell (Windows) examples, or use tabs to let users select their environment.
- Add a brief note for users on macOS/Linux that Bash is the recommended shell for Azure CLI.
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 listed immediately after CLI. There is no explicit Linux/macOS bias, but the presence of PowerShell examples and references (including a custom metadata tag 'devx-track-azurepowershell') may signal a slight Windows bias. No Linux-specific shell (bash) or OS-specific guidance is provided, though the Azure CLI example is cross-platform.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend it as the preferred cross-platform method.
- Add a note for Linux/macOS users about using Azure CLI in their native terminal environments.
- Consider listing Azure CLI examples first, and PowerShell second, to emphasize cross-platform parity.
- If relevant, mention how to upload the template file from Linux/macOS (e.g., using scp or curl) in Cloud Shell.