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 101-125 of 186 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 immediately after Bash for every step, indicating a Windows-first approach. The PowerShell formatting is prominent, and there is no explicit mention of Linux/macOS environments or their nuances. However, Bash examples are present, so Linux users can complete the task.
Recommendations
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider showing Bash examples first, or clarify that Bash is the default for cross-platform usage.
- Add a note about any differences in environment setup or command syntax between platforms.
- Provide guidance for macOS users if any step differs.
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 Bicep files. However, PowerShell is mentioned alongside CLI throughout, and the page includes a custom tag 'devx-track-azurepowershell'. PowerShell examples are given equal prominence to CLI, but there is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, which may create friction for Linux/macOS users who typically use CLI or Bash. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Consider mentioning Azure CLI first, as it is cross-platform and more widely used on Linux/macOS.
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Add a note that all steps can be completed on Linux/macOS using Azure CLI and Bicep.
- Ensure that any references to PowerShell do not imply it is required or preferred over CLI.
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 PowerShell formatting is explicitly called out, which can create a perception of Windows bias. There are no Linux-specific tools or patterns mentioned, but the Bash examples are present, ensuring Linux parity. The bias is minor and mostly in the ordering and explicit labeling of PowerShell.
Recommendations
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows' for clarity.
- Alternate the order of examples or provide tabs for Bash and PowerShell to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported and that Bash is suitable for Linux/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. However, PowerShell is presented as a primary option alongside CLI, and there is minor bias in the order and prominence of PowerShell, which is more commonly used on Windows. No Linux-specific tools or shell examples (such as Bash scripting or references to Linux-native deployment methods) are included, but the Azure CLI example is cross-platform and sufficient for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and is the recommended cross-platform tool.
- Consider adding a Bash shell example for deploying the ARM template, or clarify that the CLI example can be run in Bash or other Linux shells.
- Ensure that PowerShell is not presented as the default or primary method unless there is a Windows-specific requirement.
- Add a note for Linux/macOS users about using Azure CLI in their native terminal environments.
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 shown after the Bash examples. There is a slight bias towards Windows/PowerShell users, but Linux/macOS users are fully supported with Bash examples.
Recommendations
- Clarify in the tab headers that Bash is for Linux/macOS and PowerShell is for Windows, to help users quickly find the relevant examples.
- Consider using explicit tabbed sections for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to improve parity and discoverability.
- Ensure that variable names and code snippets are consistent between Bash and PowerShell examples to avoid 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 Bicep files, but PowerShell is given equal prominence to Azure CLI, which is more cross-platform. There is a slight bias in mentioning Azure PowerShell requirements alongside Azure CLI, and PowerShell is a Windows-centric tool, though it is available on Linux/macOS. The examples and instructions are not Windows-exclusive, but PowerShell is presented as a primary option rather than a secondary or Windows-specific alternative.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Explicitly note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for non-Windows environments.
- Consider listing Azure CLI examples first, followed by PowerShell as an alternative, to reduce perceived Windows bias.
- Add a brief note about using Cloud Shell, which is platform-agnostic, for both CLI and PowerShell tasks.
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 an equal alternative to Azure CLI, and there is a slight bias in the order of presentation: PowerShell requirements are mentioned alongside CLI requirements, and PowerShell examples are given equal prominence. There are no Linux-specific instructions, but Azure CLI is cross-platform and the examples are not Windows-exclusive. No Windows-only tools or patterns are mentioned, and the documentation does not prevent Linux/macOS users from completing the task.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a brief note clarifying that Azure PowerShell is primarily for Windows, while Azure CLI works on all platforms.
- Consider showing Azure CLI examples first, as it is the default for cross-platform usage.
- If possible, add a short section about using Cloud Shell (which is platform-agnostic) for deployments.
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 included immediately after Bash, and some variable naming (e.g., $apimID) in PowerShell is inconsistent with Bash ($apicObjID), which may cause confusion. There is a slight bias toward Windows/PowerShell users by always providing PowerShell examples, even though Bash is sufficient for cross-platform use.
Recommendations
- Clarify that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash).
- Consider grouping PowerShell examples in a collapsible section or tab, making Bash the default.
- Ensure variable names are consistent between Bash and PowerShell examples to avoid confusion.
- Explicitly state that Bash examples are recommended for cross-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. However, PowerShell examples are shown immediately after Bash for every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may indicate a slight Windows bias. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples in parity with Bash may create a perception of Windows preference.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to avoid implying parity or priority.
- If possible, show Bash examples first, as Bash is the default shell for most Linux/macOS users.
- Clarify that Azure CLI works cross-platform and that Bash examples are suitable for Linux/macOS users.
- Add a brief note explaining that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
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. However, PowerShell is highlighted as a primary method alongside CLI, and PowerShell requirements are mentioned before Linux equivalents. There is minor Windows bias in the ordering and prominence of PowerShell, but Linux users can complete all tasks using Azure CLI.
Recommendations
- Ensure Azure CLI examples are presented before PowerShell, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, while PowerShell is primarily for Windows users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell scripting examples for advanced scenarios, if relevant.
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 shown immediately after Bash in every step, and PowerShell-specific formatting is highlighted. There is no explicit Linux/macOS bias, but the presence of PowerShell examples throughout and their prominence may signal a slight Windows-first approach.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under explicit OS headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Ensure Bash examples are shown first to emphasize cross-platform parity.
- Add a note that Azure CLI works identically on all platforms, and users should use the shell appropriate for their OS.
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 equally, which may indicate a mild Windows bias. There is no exclusive use of Windows tools or missing Linux examples, but the presence of PowerShell-specific formatting can create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell sections, and ensure Bash (Linux/macOS) examples are shown first.
- Consider separating Bash and PowerShell examples into distinct tabs for clarity.
- Review variable usage and ensure Bash syntax is correct and prioritized for cross-platform parity.
- Add notes clarifying that Bash examples are for Linux/macOS and PowerShell for Windows.
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 mentioned prominently in metadata and examples. Azure PowerShell is a Windows-centric tool, though it is available cross-platform. The CLI example is present and shown first, but PowerShell requirements are listed in the prerequisites and metadata, which may suggest a Windows bias.
Recommendations
- Ensure Azure CLI examples are equally prominent and not secondary to PowerShell.
- Clarify that Azure PowerShell is available cross-platform, not only on Windows.
- Add explicit instructions for Linux/macOS users where relevant, such as file upload steps in Azure Cloud Shell.
- Remove or balance metadata tags (e.g., devx-track-azurepowershell) to avoid implying PowerShell is preferred.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file. Azure CLI is cross-platform, while Azure PowerShell is more commonly associated with Windows, though it is available on Linux/macOS. The CLI example is presented first, followed by PowerShell. There is no evidence of Windows-only tools or patterns, nor are Linux/macOS equivalents missing. The documentation does not exhibit significant Windows bias.
Recommendations
- Maintain the current order, showing Azure CLI (cross-platform) examples first.
- Clarify that both Azure CLI and Azure PowerShell are available on Windows, Linux, and macOS.
- Optionally, add a note for Linux/macOS users about using Azure CLI in their native terminal environments.
- Ensure any referenced prerequisites or included content (e.g., 'azure-powershell-requirements-no-header.md') do not assume Windows-only environments.
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 CLI usage mentions PowerShell before bash. There are no Windows-only tools or patterns, but the ordering and explicit inclusion of PowerShell examples may subtly prioritize Windows users. All tools and workflows (Azure CLI, Azure Developer CLI, Visual Studio Code) are cross-platform, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Alternate the order of bash and PowerShell examples, or present bash first to match the default shell on Linux/macOS.
- Clarify that all CLI commands work equally well on Linux/macOS, and explicitly mention cross-platform compatibility.
- Consider adding a brief section or callout for Linux/macOS users, confirming that all steps are supported on their platforms.
- Where possible, use generic shell syntax or highlight bash as the default for cross-platform 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 examples are shown immediately after Bash for each step, indicating a mild Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is present, ensuring Linux parity. However, PowerShell formatting and variable assignment are highlighted, which may subtly prioritize Windows users.
Recommendations
- Clearly label Bash and PowerShell examples, possibly using tabs or headings for each platform.
- Consider showing Bash (Linux/macOS) examples first, or alternating order to avoid implicit prioritization.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows.
- Ensure that all CLI commands are cross-platform and do not rely on Windows-specific syntax or features.
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 mentioned alongside CLI throughout, and the PowerShell example is given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, even though Azure CLI is cross-platform. No Linux-specific tools or shell examples are provided, but the CLI example is sufficient for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider providing Bash shell context or notes for Linux/macOS users (e.g., file path conventions, uploading files to Cloud Shell).
- Clarify that PowerShell is optional and primarily for Windows users, while CLI works everywhere.
- Add a note about using Cloud Shell (which supports both Bash and PowerShell) for cross-platform parity.
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 always shown immediately after Bash, and are labeled as 'Formatted for PowerShell' rather than as a distinct tab. This may slightly favor Windows users, especially since PowerShell is more common on Windows. However, Linux/macOS users are not blocked, as Bash examples are present and complete.
Recommendations
- Consider using tabbed code blocks for Bash and PowerShell to make it clearer for users to select their preferred shell.
- Explicitly mention that Bash examples are suitable for Linux/macOS and WSL users, while PowerShell examples are for Windows.
- Ensure that all examples are tested and work as shown on both Linux/macOS (Bash) and Windows (PowerShell).
- If possible, provide a short note about using Azure CLI in Cloud Shell, which supports both Bash and PowerShell.
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, but PowerShell is given equal prominence to CLI, and the PowerShell example is included directly after the CLI example. There is no explicit Linux/macOS bias, but the presence of PowerShell examples and references may create a slight Windows bias, as PowerShell is more commonly associated with Windows environments. However, Azure CLI is cross-platform and shown first, mitigating the impact.
Recommendations
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform use.
- Add a note clarifying that PowerShell Core (pwsh) is available on Linux/macOS, and the PowerShell example works there as well.
- Consider including Bash shell examples if relevant, or clarify that Azure CLI commands can be run in Bash on Linux/macOS.
- If possible, add a section or callout for Linux/macOS users to ensure parity and clarity.
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 alongside Bash, sometimes immediately after Bash. Notes clarify that Azure CLI commands can run in PowerShell or Bash, but PowerShell examples are always present, and Bash is not always shown first. No Linux-specific tools or patterns are mentioned, and Visual Studio Code is the recommended editor, which is cross-platform. There are no Windows-only tools or instructions, but the frequent inclusion of PowerShell syntax and occasional 'Windows-first' ordering may create minor friction for Linux/macOS users.
Recommendations
- Show Bash examples first when presenting Azure CLI commands, as Bash is the default shell on Linux/macOS.
- Where possible, clarify that Visual Studio Code and Azure CLI are fully cross-platform.
- Consider grouping Bash and PowerShell examples under clearly labeled tabs or sections, rather than interleaving them.
- Explicitly mention Linux/macOS compatibility in prerequisites and instructions.
- Add a brief note that all steps are applicable on Linux/macOS unless otherwise stated.
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 for every CLI step, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may subtly prioritize Windows users. There is no explicit Linux bias, but the presence of PowerShell examples throughout may create a perception of Windows preference.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash (Linux/macOS) examples are shown first where possible.
- Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows.
- Consider grouping Bash and PowerShell examples under separate tabs for clarity.
- Ensure variable naming and syntax are consistent and correct for each shell.
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 receives equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is presented as a primary option, and the page includes a custom tag 'devx-track-azurepowershell'. However, Linux users are fully supported via Azure CLI, and all critical steps have CLI equivalents.
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 primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI in their environments.
- Ensure that any referenced prerequisites or setup instructions for Azure PowerShell also mention CLI alternatives for Linux/macOS.
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) versions shown alongside Bash. However, PowerShell examples are formatted and labeled explicitly, and in some cases, Windows-style syntax is presented first or equally, which may create friction for Linux/macOS users. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples may suggest a Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash (Linux/macOS) examples are shown first or equally prominent.
- Consider providing a single Bash example unless PowerShell syntax differs significantly, or use tabs to separate Bash and PowerShell.
- Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows.
- Ensure all CLI commands are cross-platform and avoid Windows-specific syntax unless necessary.
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, with PowerShell being presented as a primary option alongside CLI. There is a slight Windows bias in the inclusion and prominence of PowerShell examples and requirements, but Linux parity is maintained through Azure CLI examples. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks.
Recommendations
- Ensure Azure CLI examples are always presented first, as CLI is cross-platform.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation guides for non-Windows platforms.
- Consider adding a note clarifying that all steps can be completed on Linux/macOS using Azure CLI or PowerShell Core.
- If possible, add Bash script examples for template deployment to further reinforce Linux parity.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file, with CLI (cross-platform) and PowerShell (Windows-centric) options shown in parallel. There is minor bias in that PowerShell is mentioned alongside CLI throughout, and the metadata includes 'devx-track-azurepowershell', but Linux/macOS users are not excluded and can follow the CLI instructions. No critical sections are Windows-only.
Recommendations
- Ensure Azure CLI examples are shown first in each section, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell examples for file operations (e.g., copying/uploading files) if relevant.