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
262 issues found
Showing 151-175 of 262 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 Azure CLI examples for both Bash and PowerShell, but PowerShell syntax is consistently shown immediately after Bash, sometimes with explicit 'PowerShell syntax' labels. There are no Windows-only tools or patterns, but the order and labeling may subtly favor Windows users. All CLI commands are cross-platform, and Visual Studio Code is recommended (which is available on Linux/macOS). No Linux-specific examples or tools are missing, but Windows/PowerShell syntax is always shown alongside Bash, sometimes first.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them so neither is consistently first.
- Explicitly mention that all Azure CLI commands work on Linux/macOS as well as Windows.
- Add a brief note clarifying that Visual Studio Code and Azure CLI are fully supported on Linux/macOS.
- Consider including screenshots or references to Linux/macOS environments in portal instructions.
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 shown immediately after Bash for every command, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), indicating a Windows-centric approach. There are no macOS-specific notes, and Linux/Bash examples are not given priority or additional context.
Recommendations
- Consider showing Bash (Linux/macOS) examples first, as Bash is the default shell on most non-Windows platforms.
- Add a note clarifying that Bash examples work on Linux and macOS, and PowerShell examples are for Windows users.
- If possible, provide parity in explanations for both shells, and mention any differences in behavior or prerequisites for Linux/macOS users.
- Explicitly state that Azure CLI commands can be run on any OS with the Azure CLI installed.
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 shown immediately after Bash in each step, and the PowerShell formatting is explicitly called out, which may indicate a slight Windows-first bias. There is no evidence of missing Linux examples, as Bash is included, and no exclusive mention of Windows tools or patterns.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to improve parity and reduce friction.
- Ensure that Bash examples are not presented as secondary or less complete than PowerShell examples.
- Add a brief note at the start of the CLI section indicating which shell is appropriate for each platform.
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 Bicep files. However, PowerShell is featured equally alongside CLI, and references to PowerShell are present in prerequisites and deployment instructions. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since PowerShell is listed in prerequisites and deployment steps. The CLI example is present and shown first, mitigating some bias. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Explicitly state that Azure PowerShell is available cross-platform (via PowerShell Core), but CLI is often simpler for Linux/macOS.
- Consider adding a note or section for Linux/macOS users, highlighting CLI usage and file handling (e.g., uploading files in Cloud Shell).
- Ensure that CLI examples are always shown first and that PowerShell is presented as an alternative, not a primary method.
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 Azure CLI command examples for both bash and PowerShell, but PowerShell syntax is consistently shown immediately after bash, and the note on shell support mentions PowerShell first. There are no Windows-only tools or patterns, but the ordering and emphasis slightly favor Windows/PowerShell users. All steps are achievable on Linux/macOS, but minor bias exists in example ordering.
Recommendations
- Alternate the order of bash and PowerShell examples, or show bash first where appropriate.
- Explicitly mention that all steps are fully supported on Linux/macOS, not just 'can run in PowerShell or bash'.
- Add a short section or note highlighting Linux/macOS compatibility and any prerequisites (e.g., Azure CLI installation on Linux).
- Consider grouping shell examples together, or using tabs to let users select their preferred shell.
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 shown immediately after Bash for every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may signal a Windows-first bias. There are no missing Linux examples, but the repeated inclusion and labeling of PowerShell commands could create friction for Linux/macOS users.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to avoid overwhelming users with both formats inline.
- Ensure Bash examples are presented first or equally, and clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a short note explaining which shell to use on each platform, helping users select the appropriate example.
- If possible, minimize duplication by referencing the shell-specific syntax only where it differs significantly.
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 shown immediately after Bash for every command, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'). This creates a slight bias toward Windows users, as Linux/macOS users are not given additional context or troubleshooting tips. The Bash examples are present and correct, so Linux parity is mostly maintained.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS, and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under explicit OS tabs (e.g., 'Linux/macOS', 'Windows') for clarity.
- Add a note indicating that Azure CLI commands work cross-platform, and provide troubleshooting tips for common shell differences.
- Ensure variable naming and syntax are consistent and correct for each shell (e.g., check for variable name mismatches like $apimID vs $apicObjID).
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 PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no explicit Linux/macOS bias. The instructions reference uploading files to Azure Cloud Shell, which is cross-platform, but do not mention Linux-specific shell usage or tools (e.g., Bash). The order of examples does not consistently favor Windows, but PowerShell is present throughout, which may create minor friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, or clarify that Azure CLI commands work in Bash and other shells.
- Mention that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- Consider providing a note or section for Linux/macOS users about uploading files and running CLI commands from their native environments.
- If PowerShell is not required, clarify that it is optional and that CLI is recommended for cross-platform scenarios.
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 Bicep files. However, PowerShell is presented as a primary alternative to Azure CLI, and PowerShell requirements are mentioned alongside CLI prerequisites. The examples are split into CLI and PowerShell tabs, but there is no explicit mention of Bash or Linux-specific shell environments, nor are there instructions tailored for Linux/macOS users (e.g., file path conventions, shell-specific notes). The documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Add explicit notes or examples for Bash or other Linux/macOS shell environments, especially regarding file paths and uploading files.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux/macOS shells.
- Include a brief section or note for Linux/macOS users about using Azure CLI in their native environments.
- Ensure that prerequisites and environment setup instructions mention Linux/macOS options (e.g., installing Azure CLI on Linux/macOS, using Cloud Shell from a browser).
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 examples for both Bash and PowerShell, with Bash shown first in nearly all cases. There are no Windows-specific tools or patterns prioritized, and Linux parity is maintained throughout. Visual Studio Code is recommended, which is cross-platform, and all CLI commands are compatible with Linux/macOS. No critical steps are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Explicitly mention that all tools (Azure CLI, Azure Developer CLI, Visual Studio Code) are cross-platform.
- Consider adding a short note confirming Linux/macOS compatibility for all steps, to reassure non-Windows users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell (Windows) examples are given alongside Bash, and PowerShell-specific formatting is explicitly called out. Bash examples are shown first, but the presence of PowerShell examples indicates a mild Windows bias. No Linux-specific tools or patterns are missing, and the Azure CLI commands work cross-platform.
Recommendations
- Clarify that both Bash and PowerShell examples are cross-platform (PowerShell Core runs on Linux/macOS).
- Consider explicitly mentioning that Bash examples are suitable for Linux/macOS, and PowerShell for Windows (or PowerShell Core on other OSes).
- If possible, provide a brief note about running Azure CLI commands in Bash on Linux/macOS and in PowerShell on Windows.
- Ensure parity by not implying PowerShell is Windows-only, since PowerShell Core is cross-platform.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell examples are shown for every CLI command, which is primarily a Windows shell. Bash examples are presented first, but PowerShell examples are given equal prominence, which may suggest a slight Windows bias. No Linux-specific tools or patterns are missing, and the Azure CLI commands are cross-platform.
Recommendations
- Clarify that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS.
- Consider grouping Bash and PowerShell examples under separate tabs for clarity.
- Explicitly mention that Bash examples work on Linux/macOS and Windows (if Bash is installed), while PowerShell is primarily for Windows.
- If possible, provide a note about cross-platform compatibility of 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 featured equally alongside CLI. There is a slight Windows bias as PowerShell is traditionally associated with Windows, and the PowerShell example is given immediately after the CLI example. However, both methods are clearly presented, and Azure CLI is cross-platform. No Linux/macOS-specific tools or patterns are missing, but there are no explicit Bash or Linux shell examples.
Recommendations
- Clarify that Azure CLI works on Linux/macOS and Windows, and is recommended for cross-platform users.
- Consider adding a Bash shell example for Linux users, even if it simply wraps Azure CLI commands.
- Mention that PowerShell Core is available on Linux/macOS, to avoid implying PowerShell is Windows-only.
- If relevant, note that the Azure portal and Cloud Shell are platform-agnostic.
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 Bicep files. However, PowerShell is presented as a primary option alongside Azure CLI, and there are references to Azure PowerShell requirements. While Azure CLI is cross-platform, PowerShell is more commonly associated with Windows, and its inclusion may create a slight Windows bias. There are no Linux-specific examples or explicit mentions of Linux/macOS tools or workflows.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is available on Linux/macOS, but Azure CLI is generally more common for non-Windows environments.
- Consider providing bash shell examples or instructions for Linux/macOS users, especially for file operations (e.g., saving/uploading the Bicep file).
- Ensure that prerequisites and environment setup instructions include Linux/macOS guidance where relevant.
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 are no Windows-only tools or patterns, but the examples do show Windows (PowerShell) syntax alongside Bash, which may create minor friction for Linux/macOS users. The documentation does not exclusively mention Windows tools, and Visual Studio Code is cross-platform. No critical steps are Windows-only.
Recommendations
- Consider showing Bash examples first, or grouping Bash and PowerShell examples together for parity.
- Clarify that PowerShell syntax is for Windows users, and Bash for Linux/macOS, to help readers quickly identify their relevant section.
- If possible, provide a single Bash example where syntax is identical, and only split when necessary.
- Explicitly mention that all steps can be performed on Linux/macOS unless otherwise noted.
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 formatted specifically for Windows users and are presented immediately after the Bash examples. There is no explicit Linux bias, but the inclusion of PowerShell examples and their prominence suggests a mild Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples as 'Linux/macOS' and 'Windows' respectively to help users identify which example is relevant to their platform.
- Consider providing Bash examples first, or at least alternate the order to avoid always showing Windows examples second.
- Add a brief note clarifying that Bash examples are intended for Linux/macOS terminals, and PowerShell for Windows.
- Ensure parity in explanations and troubleshooting tips for both environments.
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 PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux/macOS-specific tools or workflows. The instructions reference uploading files to Azure Cloud Shell, which is cross-platform, but do not mention Linux-native tools (e.g., Bash, shell scripting) or alternative deployment methods (such as using REST API or Terraform). The order of examples (CLI first, then PowerShell) is neutral, but the presence of PowerShell-specific requirements and examples may create minor friction for Linux/macOS users.
Recommendations
- Add explicit mention that Azure CLI works natively on Linux/macOS, and provide Bash shell example commands where relevant.
- Clarify that Azure PowerShell is cross-platform, but CLI is often preferred on Linux/macOS.
- Consider including a REST API example for ARM template deployment, which is platform-agnostic.
- Mention that Cloud Shell supports both Bash and PowerShell, and show how to use Bash for file uploads and deployments.
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 Bicep files, but PowerShell is mentioned alongside CLI throughout and is given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the documentation includes a custom tag 'devx-track-azurepowershell'. However, Linux/macOS users can fully complete the quickstart using Azure CLI, and no critical steps are Windows-only.
Recommendations
- Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Clarify that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Add a note highlighting that Azure CLI is recommended for cross-platform scenarios.
- Ensure that any referenced prerequisites or environment setup instructions for PowerShell include Linux/macOS guidance.
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 alongside Bash for every step, and PowerShell syntax is shown first in some cases. There is a slight bias toward Windows/PowerShell users, as Linux/macOS users may find the PowerShell examples unnecessary or confusing. However, Bash examples are present, so Linux parity is mostly maintained.
Recommendations
- Clearly label Bash and PowerShell examples to avoid confusion.
- Consider grouping Bash and PowerShell examples under separate tabs or sections, rather than showing both inline.
- Ensure Bash examples are shown first, as Bash is the default shell for Azure CLI and most cross-platform users.
- Add a note clarifying which examples are for Windows (PowerShell) and which are for Linux/macOS (Bash).
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 note about Azure CLI usage mentions PowerShell first. There are no Windows-only tools or patterns, but the ordering and explicit PowerShell examples indicate a mild Windows bias. All steps are achievable on Linux/macOS, but Windows users may find the examples slightly more tailored to their environment.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them under clear headings for each platform.
- Explicitly state that all steps are cross-platform and supported on Linux/macOS.
- Add a brief note clarifying that Visual Studio Code and Azure CLI are available on Linux/macOS, and that all commands can be run in Bash shells.
- Consider providing a single Bash example with a link to PowerShell syntax, unless both are truly necessary.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, with PowerShell (Windows) variants shown immediately after Bash. While Linux Bash examples are present, PowerShell examples are given equal prominence, potentially implying Windows is a primary platform. No Linux-specific tools or patterns are missing, but the PowerShell variants may create a perception of Windows-first bias.
Recommendations
- Clearly label Bash and PowerShell examples as 'Linux/macOS' and 'Windows', respectively, to help users identify their relevant platform.
- Consider showing Bash (Linux/macOS) examples first, followed by PowerShell (Windows) examples, to reinforce platform parity.
- Add a brief note explaining that Azure CLI commands work on both Linux/macOS (Bash) and Windows (PowerShell), and clarify any syntax differences.
- If possible, provide a single cross-platform example using Azure CLI, with notes on syntax differences, rather than duplicating commands.
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 formatting is explicitly called out, which may create a slight Windows bias. The Bash examples are present and correct, but PowerShell examples are shown immediately after, sometimes with more explanation. There is no exclusive use of Windows tools, and Linux users can complete all tasks without friction.
Recommendations
- Ensure Bash examples are always shown first, as Bash is the default shell for most cross-platform CLI users.
- Clearly label PowerShell examples as 'Windows/PowerShell' and Bash as 'Linux/macOS/Bash' to help users quickly identify their relevant section.
- Consider separating Bash and PowerShell examples into distinct tabs or sections, rather than showing both inline, to reduce confusion.
- Review explanations to ensure Bash/Linux usage is not treated as secondary or less detailed.
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 Bicep files. However, PowerShell is presented as a primary option alongside CLI, and there is a slight Windows-first bias in the ordering and inclusion of PowerShell-specific instructions. No Linux/macOS-specific guidance or troubleshooting is provided, but Azure CLI is cross-platform and included.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a brief note clarifying that Azure PowerShell is primarily used on Windows, while Azure CLI works on Linux/macOS.
- Consider showing Azure CLI examples first, or labeling them as the recommended method for non-Windows environments.
- Include troubleshooting tips for Linux/macOS users, such as file path conventions or Cloud Shell usage.
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 throughout, with Bash examples shown first and PowerShell examples following. There are no Windows-specific tools or patterns, and Linux parity is maintained in all examples. The only minor bias is that Bash (Linux/macOS) examples are presented before PowerShell (Windows), but both are equally supported.
Recommendations
- No significant changes needed. Both Bash and PowerShell examples are provided, ensuring parity.
- If desired, clarify at the start that all CLI commands work on Windows, Linux, and macOS, and that examples for both shells are included.
- Consider alternating the order of Bash and PowerShell examples in future documentation for absolute neutrality.
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 always shown immediately after the Bash ones, and are labeled as 'Formatted for PowerShell.' This gives slight preference to Windows/PowerShell users, but Linux/macOS users are not blocked. All commands are cross-platform Azure CLI commands.
Recommendations
- Consider using tabbed code blocks for Bash and PowerShell to make it easier for users to select their preferred shell.
- Explicitly mention that Bash examples work on Linux/macOS and Windows (with WSL or Git Bash), and that PowerShell examples are for Windows or PowerShell Core.
- If possible, default to Bash examples first, as Bash is available on all platforms, or clarify that both are equally supported.