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 126-150 of 262 flagged pages
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 featured as a primary option, and the prerequisites section includes Azure PowerShell requirements. However, Azure CLI (cross-platform) is also fully supported and shown first in the deployment example tabs. No Windows-only tools or patterns are exclusively mentioned, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider mentioning Bash or shell scripting as alternatives for Linux/macOS users where appropriate.
- Ensure that any references to uploading files (e.g., in Cloud Shell) include instructions for Linux/macOS users, such as using SCP or drag-and-drop.
- If possible, add a note that Azure PowerShell is available cross-platform, but CLI is generally preferred for Linux/macOS.
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, but PowerShell examples are shown immediately after Bash for each step, and some variable assignment patterns (e.g., $scope=$apimID.substring(1)) are PowerShell-specific. There is no explicit Linux/macOS bias, but the inclusion of PowerShell examples and variable assignment patterns may create friction for Linux users. However, Bash examples are present for all steps.
Recommendations
- Clearly label Bash and PowerShell examples to avoid confusion.
- Ensure Bash examples are shown first for cross-platform parity.
- Add a note clarifying which examples are for Linux/macOS (Bash) and which are for Windows (PowerShell).
- Consider providing a brief explanation of the differences in variable assignment and string manipulation between Bash and PowerShell.
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 the prerequisites section tracks Azure PowerShell. The PowerShell example is given equal prominence to CLI, and there is no explicit mention of Linux/macOS-specific considerations (such as file path differences or shell compatibility). However, Azure CLI is cross-platform and shown first in deployment steps, mitigating most bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a note indicating Azure PowerShell is primarily used on Windows, and CLI is recommended for Linux/macOS.
- Explicitly mention file path conventions for Linux/macOS (e.g., ./main.bicep vs .\main.bicep).
- Consider including a Bash example for deploying Bicep files, or referencing Cloud Shell as a cross-platform solution.
- Ensure prerequisites for Azure CLI are as prominent as PowerShell, and avoid tracking PowerShell unless 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. However, PowerShell examples are consistently shown immediately after Bash, and are labeled 'Formatted for PowerShell', which may indicate a slight Windows bias. There are no missing Linux examples, but the presence of PowerShell-specific formatting and variable assignment patterns may create friction for Linux/macOS users. No Windows-only tools or patterns are mentioned, and the Azure CLI is cross-platform.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with explicit labels.
- Consider showing Bash examples first, as Bash is the default shell on most Linux/macOS systems.
- Provide a brief note explaining the differences in shell syntax for users unfamiliar with PowerShell.
- Ensure parity in explanations and avoid implying PowerShell is the default or 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, but the PowerShell examples are formatted and presented immediately after the Bash examples in each step. There is a slight bias toward Windows/PowerShell users, as PowerShell examples are given equal prominence, and the PowerShell formatting is specifically called out. However, Linux users are not missing any information, and Bash examples are present throughout.
Recommendations
- Consider clearly labeling Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to help users quickly identify relevant sections.
- If possible, present Bash (Linux/macOS) examples first, as Azure CLI is cross-platform and Bash is the default shell for many users.
- Add a brief note clarifying that both Bash and PowerShell examples are functionally equivalent and that Azure CLI works on all platforms.
- Ensure that any future additions do not default to Windows/PowerShell unless the feature is Windows-only.
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, and the PowerShell formatting is explicitly called out. There is no evidence of missing Linux examples, but the presence of PowerShell examples and their prominence may create a slight Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Consider showing Bash (Linux/macOS) examples first, or providing a toggle to select preferred shell/OS.
- Ensure variable naming and command syntax are consistent and correct for each shell.
- Add a note clarifying that Bash examples are suitable for Linux/macOS users, and PowerShell for Windows users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools for reviewing deployed resources, but does not provide explicit Linux/macOS examples or clarify cross-platform usage. Azure PowerShell is primarily associated with Windows, and its mention before Linux-native tools may subtly prioritize Windows users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide example commands for both Azure CLI and Azure PowerShell, with clear notes on platform compatibility.
- Mention that Azure PowerShell is available for Linux/macOS, if relevant, or recommend Azure CLI for Linux/macOS users.
- Consider listing Azure CLI before Azure PowerShell to reinforce cross-platform parity.
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 mentioned prominently (in metadata and example tabs), and there is a slight preference for Windows/PowerShell tools. However, Azure CLI examples are also present, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are always shown first, as CLI is cross-platform.
- Add explicit notes clarifying that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
- Consider including Bash shell scripting examples for Linux/macOS users, or at least mention that Azure CLI commands can be run in Bash.
- Review metadata (ms.custom: devx-track-azurepowershell) to ensure it doesn't imply PowerShell is required.
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 featured as a primary option, and the prerequisites section tracks Azure PowerShell requirements. However, Azure CLI (cross-platform) is also fully supported and shown first in the deployment section.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI and uploading files in Cloud Shell.
- Consider including a brief section on using Bicep directly (if supported) for advanced users on Linux/macOS.
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 labeled 'Formatted for PowerShell', which is a Windows-centric shell. Bash examples are present, but PowerShell examples are always shown immediately after, suggesting a slight Windows-first bias. No Linux-specific tools or patterns are missing, but the PowerShell emphasis may create friction for Linux/macOS users.
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' and 'Windows') for clearer parity.
- Ensure Bash examples are shown first or equally, to avoid implicit Windows prioritization.
- Add a note explaining the equivalence of Bash and PowerShell commands for cross-platform 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 deployment examples for both Azure CLI and Azure PowerShell, but PowerShell is given equal prominence to CLI and is referenced in metadata and prerequisites. There is a mild bias in listing PowerShell alongside CLI, which can create friction for Linux/macOS users who typically use CLI or Bash. However, the CLI example is present and complete, and no Windows-only tools or patterns are required.
Recommendations
- Clarify that Azure PowerShell is cross-platform, but highlight Azure CLI as the primary method for Linux/macOS users.
- Add Bash shell example for deploying the ARM template, or explicitly mention that Azure CLI works natively on Linux/macOS.
- Ensure that prerequisites and environment setup instructions for Azure CLI are as detailed as those for PowerShell.
- Consider listing Azure CLI examples before PowerShell to better serve Linux/macOS 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 the PowerShell examples are shown immediately after the Bash ones for every command. This creates a mild bias toward Windows users, as PowerShell is primarily a Windows shell, and its inclusion may suggest Windows as a primary platform. However, Bash examples are present and shown first, ensuring Linux parity.
Recommendations
- Clearly label Bash and PowerShell examples to help users quickly identify their platform.
- Consider grouping Bash and PowerShell examples under explicit headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- If possible, provide a brief note explaining which shell to use depending on the user's OS.
- Ensure that Bash examples remain first for cross-platform 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. Azure CLI is presented first, which is cross-platform, followed by Azure PowerShell, which is more Windows-centric. There are no exclusive Windows tools or missing Linux examples; both deployment methods are covered. The only minor bias is the ordering, with PowerShell mentioned second and tracked in metadata.
Recommendations
- Ensure that Azure CLI examples are emphasized as the default for cross-platform users.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, while Azure PowerShell is primarily Windows-focused.
- Consider adding a note for Linux/macOS users recommending Azure CLI for best compatibility.
- If possible, provide links to installation instructions for Azure CLI on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools to review deployed resources, but does not provide explicit Linux/macOS examples or clarify cross-platform usage. Azure PowerShell is primarily associated with Windows, and its mention before Linux-native tools may suggest a Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Provide example commands for both Azure CLI and Azure PowerShell, or clarify that both are available on all major OSes.
- If referencing PowerShell, note that PowerShell Core is available on Linux/macOS, or link to installation instructions for those platforms.
- Consider listing Azure CLI first, as it is the default cross-platform tool.
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 directly after Bash, and the note about CLI usage references PowerShell before Bash. There are no Windows-only tools or patterns, but the ordering and explicit inclusion of PowerShell syntax throughout the CLI sections creates a mild Windows bias. All instructions are cross-platform, and Linux/macOS users can complete the tasks without friction.
Recommendations
- Alternate the order of Bash and PowerShell examples, or show Bash first in some sections to avoid implicit Windows prioritization.
- Clarify that all Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell or Bash.
- Consider providing a single CLI example with a note about variable syntax differences, rather than duplicating for PowerShell unless necessary.
- Explicitly mention Linux/macOS compatibility in the prerequisites or intro.
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 given equal prominence and are formatted specifically for Windows users. Bash examples are shown first, but the inclusion of PowerShell-specific syntax and comments indicates a moderate Windows bias. No Linux-specific tools or patterns are missing, but the PowerShell formatting may create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell examples, and consider grouping them under OS-specific tabs (e.g., 'Linux/macOS' and 'Windows').
- Provide a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows.
- Ensure Bash examples are always shown first, and PowerShell examples are secondary.
- Avoid PowerShell-specific comments unless necessary, and provide parity in explanation for Bash users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both Bash (Linux/macOS) and PowerShell (Windows), but the PowerShell examples are formatted and presented immediately after the Bash examples in each step. The PowerShell formatting is explicitly called out, and variable assignment syntax is shown for both shells. However, the PowerShell examples are labeled as 'Formatted for PowerShell', which may subtly prioritize Windows users. There is no missing Linux example, but the documentation could be more explicit about shell/platform parity.
Recommendations
- Clarify that Bash examples are for Linux/macOS and PowerShell examples are for Windows.
- Present Bash and PowerShell examples side-by-side or in clearly separated tabs to avoid implicit prioritization.
- Ensure variable names and assignment patterns are consistent and correct for each shell.
- Add a brief note at the start of the CLI section explaining which shell/platform each example targets.
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 a Windows-centric tool and is presented alongside Azure CLI without explicit mention of Linux/macOS alternatives (such as Bash or shell scripting). The Azure PowerShell example may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms, even though it is technically cross-platform. The CLI example is shown first, which helps mitigate bias, but there is no explicit guidance for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- Add a note that Azure PowerShell is available cross-platform, but CLI is preferred for Linux/macOS users.
- Consider including Bash shell script examples or instructions for Linux/macOS users, if relevant.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
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, Azure PowerShell is highlighted alongside Azure CLI throughout, and PowerShell examples are given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the prerequisites section explicitly tracks Azure PowerShell. The CLI example is shown first, but both are presented in parallel, and Linux users can complete the task using Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS.
- Add a note in the prerequisites section to guide Linux/macOS users toward Azure CLI.
- Consider including a Bash script example for further Linux parity, if 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
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell syntaxes. However, throughout the page, PowerShell examples are consistently shown after bash, and the documentation explicitly states that Azure CLI commands can run in either shell. There are no Windows-only tools or patterns, and Linux parity is maintained. The only minor bias is that PowerShell examples are always shown second, which may slightly favor Linux/bash users.
Recommendations
- Consider alternating the order of bash and PowerShell examples in sections, or explicitly state that both are equally supported.
- Add a brief note at the start of the CLI sections clarifying that all examples are cross-platform and that both bash and PowerShell are fully supported.
- Ensure screenshots and portal instructions are not Windows-centric (they currently are not).
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 for every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may suggest a Windows-centric approach. There are no Linux-specific tools or patterns mentioned, but Bash is presented first, indicating some parity.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with explicit labels.
- Consider grouping Bash and PowerShell examples under clear OS headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Ensure that any OS-specific caveats or requirements are mentioned (e.g., prerequisites for PowerShell on Windows, Bash on Linux/macOS).
- If possible, provide a note about using Azure CLI in Cloud Shell, which is cross-platform.
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 alongside CLI. There is a slight Windows bias in the inclusion and prominence of PowerShell examples and requirements, which are primarily relevant for Windows users. However, Azure CLI examples are also provided, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are presented first, as CLI is cross-platform and more accessible for Linux/macOS users.
- Explicitly mention that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI or Azure Cloud Shell.
- Consider including Bash shell scripting examples for Linux users where relevant.
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 and is referenced in the metadata and prerequisites. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) can create a perception of Windows bias, especially since PowerShell is not as commonly used on Linux/macOS. However, both CLI and PowerShell instructions are present, and the CLI is shown first in the deployment section.
Recommendations
- Ensure that Azure CLI examples are always shown first, as it is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, but Azure CLI is recommended for cross-platform users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI and uploading files in Cloud Shell.
- Review metadata tags (e.g., devx-track-azurepowershell) to ensure they do not imply Windows preference.
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 consistently shown immediately after Bash, and the PowerShell formatting is explicitly highlighted. This creates a mild Windows bias, as Linux/macOS users may perceive the PowerShell examples as unnecessary or confusing. There are no missing Linux examples, and the CLI commands are cross-platform, but the presence and prominence of PowerShell formatting indicate a Windows-first approach.
Recommendations
- Clearly label Bash and PowerShell sections to reduce confusion.
- Consider grouping Bash and PowerShell examples in separate tabs or collapsible sections.
- Ensure Bash examples are presented first, as Bash is the default shell for most Linux/macOS users.
- Add a note clarifying that Azure CLI commands work in both environments, and users should use the syntax appropriate for their shell.
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 featured equally alongside CLI, and there is no mention of Linux-specific tools or workflows (e.g., Bash, shell scripting, or references to Linux/macOS environments). The instructions for uploading files reference Azure Cloud Shell generically, but do not clarify Linux/macOS workflows. PowerShell is a Windows-centric tool, though it is available cross-platform; its inclusion may create friction for Linux/macOS users who typically use Bash or CLI.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash shell example commands where relevant.
- Clarify file upload instructions for Linux/macOS users (e.g., using SCP, curl, or native file managers).
- Consider including a Bash shell example for deploying the ARM template, or at least note that Azure CLI commands can be run in Bash.
- Ensure that PowerShell is not presented as the default or primary method, but as an alternative for users who prefer it.