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 101-125 of 262 flagged pages
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but the presence of PowerShell examples and references (including devx-track-azurepowershell metadata) may indicate a slight Windows bias. However, Azure CLI examples are also present and shown first, which helps Linux/macOS parity. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the Azure CLI is cross-platform.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and Windows.
- Add a Bash shell example for Linux users, or clarify that Azure CLI commands can be run in Bash.
- Consider referencing Azure Cloud Shell as a cross-platform option.
- Ensure that any prerequisites or environment setup instructions are not Windows-centric.
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 every step, indicating a Windows-first approach. The PowerShell formatting is prominent, which may suggest a bias toward Windows users. However, Linux (Bash) examples are present and complete, so Linux/macOS users can follow the instructions without missing information.
Recommendations
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to reduce visual bias and improve clarity.
- Ensure Bash examples are presented first or equally, especially since Azure CLI is cross-platform.
- Add a brief note clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, to guide users.
- Review for any subtle differences in command syntax or environment variables that may affect Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell (Windows) examples for Azure CLI commands. However, in each case, the Bash example is shown first, followed by the PowerShell version. There are no exclusive Windows tools or patterns, and Linux/macOS users are fully supported.
Recommendations
- No major changes needed, as both Bash and PowerShell examples are provided.
- Consider clarifying in the tab headers or code comments which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows) to further reduce ambiguity.
- Ensure that the Bash examples are always presented first if following a Linux-first approach, or provide clear tabs for each 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 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, which is cross-platform. There is minor bias in listing PowerShell as a primary method, but Linux/macOS users can use Azure CLI without issue. No Windows-only tools or patterns are mentioned, and the instructions are generally platform-neutral.
Recommendations
- Explicitly note that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell, or clarify that both methods are equivalent.
- Add a brief note that Azure PowerShell is available on Linux/macOS via PowerShell Core, but Azure CLI is often simpler for non-Windows environments.
- Ensure that any references to uploading files in Azure Cloud Shell are clear for both Bash and PowerShell environments.
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 the inclusion of PowerShell-specific requirements and examples, which are more relevant to Windows users, while Linux/macOS users primarily use Azure CLI. However, Linux parity is generally maintained, as CLI instructions are present and not secondary.
Recommendations
- Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI instructions first in each section to reduce Windows-first perception.
- Add a brief note clarifying that Azure PowerShell is primarily for Windows, while Azure CLI works on all platforms.
- Ensure that prerequisite sections for Azure CLI and PowerShell are equally detailed and accessible.
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 step, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may imply a Windows-centric approach. There is no explicit Linux bias, but the inclusion 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, as Bash is the default shell for Azure CLI and most cross-platform users.
- Consider providing only Bash examples unless there is a specific need for PowerShell, or move PowerShell examples to a separate tab or section to avoid clutter and bias.
- Explicitly mention that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash), and PowerShell is for Windows users.
- Ensure variable naming and command syntax is consistent and correct for each shell (e.g., $scope vs. $apimID).
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. Azure CLI is cross-platform, but the documentation does not highlight this or provide Bash-specific guidance. The PowerShell example may create friction for Linux/macOS users, especially since PowerShell is less commonly used outside Windows.
Recommendations
- Clarify that Azure CLI is cross-platform and works natively on Linux/macOS.
- Consider providing Bash shell examples or explicitly noting that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- Mention that PowerShell Core is available on Linux/macOS if referencing PowerShell, or link to installation instructions for non-Windows platforms.
- If possible, prioritize Azure CLI examples or present them before PowerShell, since CLI is more universal.
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 as 'Formatted for PowerShell', which may imply a Windows-centric approach. There is no explicit mention of Linux/macOS, nor are Bash examples labeled as 'Linux/macOS'. The portal instructions are platform-neutral, but the CLI section subtly prioritizes Windows by including PowerShell variants for every command.
Recommendations
- Label Bash examples as 'Linux/macOS' and PowerShell as 'Windows' to clarify platform applicability.
- Consider using tabbed code blocks for Bash (Linux/macOS) and PowerShell (Windows) to visually separate and equally prioritize both platforms.
- Add a brief note explaining that Bash examples are for Linux/macOS terminals and PowerShell examples are for Windows.
- Ensure parity in instructions and avoid implying that PowerShell is the default or preferred shell for Azure CLI usage.
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 Bicep files. While both tools are cross-platform, Azure PowerShell is more commonly associated with Windows environments. However, the CLI example is given first, and both are presented equally. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI. No Linux-specific examples or notes are missing, but minor bias exists in the inclusion of PowerShell, which may be unnecessary for Linux users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a note that Azure PowerShell is also available on Linux/macOS, or indicate which tool is preferred for each platform.
- Optionally, provide Bash shell scripting examples for common automation scenarios.
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, and the PowerShell formatting is explicitly called out as 'Formatted for PowerShell', which may indicate a slight preference for Windows environments. There is no explicit Linux/macOS bias, but the presence of PowerShell examples and their formatting may create minor friction for non-Windows users.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows' for clarity.
- Ensure Bash examples are always shown first to reinforce Linux parity.
- Add a note that Azure CLI works cross-platform and Bash is recommended for Linux/macOS.
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 (a Windows-centric tool) is featured equally alongside Azure CLI, and PowerShell requirements are mentioned in the prerequisites. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, though it is available on Linux/macOS. The order of examples does not strongly favor Windows, but the inclusion of PowerShell as a primary option may create mild friction for Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, highlighting that Azure CLI works natively and is preferred.
- Consider showing Azure CLI examples first, or adding a brief note about PowerShell's cross-platform availability.
- Ensure that any referenced prerequisites or setup instructions for PowerShell include Linux/macOS guidance if PowerShell is to be used.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both bash and PowerShell command examples for Azure CLI operations, but PowerShell syntax is often shown immediately after bash, and Visual Studio Code instructions reference Windows keyboard shortcuts and folder paths first. Output examples use Windows-style paths (e.g., C:\Users\<user>\AppData\Local\Temp), and Visual Studio Code instructions reference Windows conventions. However, all critical steps are cross-platform, and Linux/macOS users can complete the tasks without friction.
Recommendations
- Ensure output examples use generic or cross-platform paths, or provide both Windows and Linux/macOS output samples.
- When referencing Visual Studio Code, include macOS/Linux keyboard shortcuts and clarify folder navigation for all platforms.
- Alternate the order of bash and PowerShell examples, or explicitly state that both are supported equally.
- Add explicit notes about Linux/macOS compatibility for Azure Functions Core Tools and Azure CLI steps.
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 consistently shown immediately after Bash, and are explicitly labeled as 'Formatted for PowerShell.' This creates a slight Windows bias, as Linux/macOS users may expect Bash examples to be prioritized or exclusively shown. However, both platforms are covered, and the Azure CLI is cross-platform.
Recommendations
- Clearly label Bash examples as 'Linux/macOS' and PowerShell as 'Windows' to help users identify the relevant section.
- Consider showing Bash examples first, or grouping them together before PowerShell examples, to reinforce Linux parity.
- Add a brief note clarifying that Azure CLI commands work on all platforms, and that Bash is the default shell for Linux/macOS users.
- If possible, provide a toggle or tabbed interface for users to select their preferred shell (Bash or PowerShell), reducing clutter and bias.
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 alongside CLI throughout, and the PowerShell example is given equal prominence. There is no explicit Linux/macOS bias, but PowerShell is a Windows-centric tool (though available on Linux/macOS), and the documentation does not mention Bash or shell scripting alternatives. The Azure Cloud Shell is referenced, which is cross-platform, but the focus remains on CLI and PowerShell.
Recommendations
- Clarify that Azure PowerShell is available on Linux/macOS, not just Windows.
- Add Bash or shell scripting examples for template deployment, or explicitly state that Azure CLI commands work on Linux/macOS.
- Mention that Azure Cloud Shell can be used from any OS, and highlight its cross-platform nature.
- Consider providing a table or section that summarizes deployment options for Windows, Linux, and macOS users.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is presented as a primary option alongside CLI. There is a slight bias in mentioning Azure PowerShell requirements and examples, which are more relevant to Windows users, and the PowerShell example is given equal prominence to the CLI example. However, Azure CLI is cross-platform and shown first, and all tasks can be completed on Linux/macOS using CLI.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users, such as instructions for uploading files in Cloud Shell or using CLI locally.
- Consider mentioning that Azure PowerShell is available on Linux/macOS, but CLI is generally simpler for non-Windows environments.
- Ensure prerequisites and environment setup sections link to Linux/macOS-specific guidance 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 PowerShell examples are given for every step and are formatted with Windows-specific syntax. Bash examples are present, but PowerShell examples appear immediately after, suggesting parity but with a slight Windows-first bias. There are no missing Linux examples, but the PowerShell formatting and variable usage may create friction for Linux/macOS users.
Recommendations
- Ensure Bash examples are presented first or equally alongside PowerShell examples, especially since Azure CLI is cross-platform.
- Clarify that Bash examples are for Linux/macOS and PowerShell for Windows, to help users identify the relevant section.
- Consider providing a brief note about cross-platform compatibility and how to adapt examples for different shells.
- Review variable usage and syntax to ensure Bash examples are fully functional and not dependent on Windows-specific conventions.
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 mentioned alongside CLI throughout, and the Azure PowerShell requirements are listed before the deployment section. The examples are presented in tabbed format, so Linux users can use Azure CLI, but PowerShell is a Windows-centric tool (though available cross-platform). There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux/macOS environments or tools.
Recommendations
- Add explicit Bash shell examples for ARM template deployment using Azure CLI.
- Clarify that Azure CLI works natively on Linux/macOS and Windows, and provide guidance for Linux/macOS users where relevant.
- Mention that PowerShell Core is cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Ensure prerequisites and environment setup instructions include Linux/macOS guidance (e.g., installation steps for Azure CLI on Linux).
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 the PowerShell formatting is explicitly called out as 'Formatted for PowerShell', which may indicate a slight bias toward Windows users. Additionally, the PowerShell examples are not strictly necessary since Azure CLI works identically on all platforms, but their inclusion may help Windows users. The Bash examples are present and shown first, so Linux parity is mostly maintained.
Recommendations
- Clarify that Azure CLI commands work cross-platform and that Bash examples are suitable for Linux/macOS users.
- Consider grouping Bash and PowerShell examples under clear headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to make parity explicit.
- Ensure variable naming and command syntax is consistent and correct between Bash and PowerShell examples.
- Add a note that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.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 syntax is often shown immediately after bash, and Visual Studio Code is referenced as the primary editor. Output paths and screenshots use Windows-style paths and environments (e.g., C:\Users\<user>), and instructions reference Windows keyboard shortcuts. However, Linux/macOS equivalents are generally present, and the Azure CLI and Azure Developer CLI are cross-platform tools.
Recommendations
- Show bash and PowerShell examples side-by-side, or alternate which comes first.
- Include explicit notes that all CLI commands work on Linux/macOS and Windows.
- Add screenshots or output examples from Linux/macOS environments, or clarify that output paths may differ.
- Mention that Visual Studio Code is available on Linux/macOS, and provide alternative editor options if relevant.
- Use generic file paths in examples, or note differences between OSes.
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 for every step, and in each case, the PowerShell version is shown immediately after the Bash version, indicating a Windows-first approach. There is no explicit mention of Linux/macOS, but Bash is used, which is cross-platform. The presence of PowerShell throughout may create friction for Linux/macOS users, but all necessary Bash examples are present.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash).
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows', to make parity clearer.
- If possible, provide a brief note about running Azure CLI on Linux/macOS and Windows, including links to installation guides.
- Ensure Bash examples are not presented as secondary to PowerShell; consider alternating order or making Bash the default.
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 is given equal prominence. There is a slight bias in that PowerShell is included as a primary option, which is more relevant to Windows users, while Linux/macOS users typically use Azure CLI. However, CLI examples are present and shown first, so Linux users are not blocked.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Explicitly state that Azure CLI works on Linux/macOS and is recommended for those platforms.
- Consider adding a note or section for Linux/macOS users, highlighting the CLI workflow and any relevant differences.
- Ensure that any referenced prerequisites or setup guides for Azure CLI include Linux/macOS instructions.
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 may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is presented first, which is positive for Linux parity. No critical Linux functionality is missing.
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 clarity.
- Add a brief note explaining which shell to use on each platform to reduce confusion.
- Ensure parity in explanations for both shells, not just formatting.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.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 syntax is consistently shown after bash. Visual Studio Code is recommended as the editor, which is cross-platform, and all tooling (Azure CLI, Azure Developer CLI, Azure Functions Core Tools, Node.js, npm) is available for Linux/macOS. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks. However, minor bias exists in the order of examples and some output paths referencing Windows directories.
Recommendations
- Ensure all CLI examples are shown for both bash and PowerShell, with clear labeling.
- Consider alternating the order of bash and PowerShell examples or grouping them together to avoid implicit prioritization.
- Where possible, use generic output paths or note that output locations may differ by OS.
- Explicitly state that all steps are supported on Linux/macOS and Windows.
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 step, and in some cases, PowerShell syntax is shown first or equally, which may indicate a slight Windows bias. There are no missing Linux examples, but the presence of PowerShell throughout may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clearly label Bash and PowerShell examples, and consider showing Bash (Linux/macOS) examples first, as Bash is the default shell for most non-Windows environments.
- Provide brief guidance for macOS users if any commands differ or require additional setup.
- If PowerShell is not required for Linux/macOS, clarify that Bash is the recommended shell for those platforms.
- Consider grouping PowerShell examples in a separate tab or section to reduce clutter for Linux/macOS readers.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions Azure PowerShell and Azure CLI as tools for reviewing deployed resources, but lists Azure PowerShell before Azure CLI. This ordering may subtly prioritize Windows tooling, as PowerShell is most commonly associated with Windows environments, even though it is cross-platform. No explicit Linux/macOS examples or tools are provided, and no command-line examples are shown.
Recommendations
- List Azure CLI before Azure PowerShell, as Azure CLI is more commonly used on Linux/macOS.
- Explicitly mention that both Azure CLI and Azure PowerShell are cross-platform.
- Provide example commands for both Azure CLI and Azure PowerShell, ensuring Linux/macOS users see parity.
- Consider referencing Bash or shell scripting where relevant for Linux/macOS users.