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 126-150 of 186 flagged pages
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details →
Detected Bias Types
Windows First
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 prioritized. There are no Linux-specific tools or workflows mentioned, but the documentation does not exclusively reference Windows tools. Visual Studio Code is recommended, which is cross-platform, and all CLI instructions are compatible with Linux/macOS. However, PowerShell syntax is given equal prominence to bash throughout, and Windows portal screenshots are used.
Recommendations
- Show bash examples first, with PowerShell as an alternative.
- Explicitly state that all CLI commands work on Linux/macOS and provide any necessary Linux-specific notes (e.g., file path differences, environment setup).
- Include screenshots or instructions for Azure portal access from Linux/macOS (if relevant).
- Where possible, clarify that Visual Studio Code and Azure Functions extension are fully supported on Linux/macOS.
- Consider adding a section or note for Linux/macOS users about any potential differences or tips.
Create Pull Request
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 for Windows and are presented immediately after the Bash examples. There is no explicit Linux bias, but the presence of PowerShell examples and their placement may suggest a slight Windows-first approach.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell examples are for Windows users.
- Consider labeling the code blocks more explicitly, e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)'.
- Ensure Bash examples are presented first, or alternate their order to avoid implicit Windows prioritization.
- Add a note that Azure CLI works cross-platform and that Bash examples are generally preferred 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 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, and its requirements are listed alongside Azure CLI. However, both CLI and PowerShell examples are given, and the CLI is cross-platform. There are no Linux-specific instructions or examples, but Linux/macOS users can use Azure CLI without issue.
Recommendations
- Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
- Consider mentioning Bash or shell scripting as an alternative for Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as file path conventions or uploading files in Cloud Shell.
- Ensure that PowerShell is not presented as the default or primary method unless required.
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 each step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is used, which is common on Linux/macOS. The ordering and explicit PowerShell labeling suggest Windows users are prioritized, but Linux/macOS users can complete all tasks without friction.
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 clarity.
- Ensure Bash examples are shown first or equally with PowerShell to avoid perceived prioritization.
- Add a brief note indicating cross-platform compatibility of Azure CLI commands.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides Azure CLI examples for both bash and PowerShell throughout, with PowerShell examples consistently shown after bash. There is no exclusive use of Windows/PowerShell, nor are Windows tools or patterns mentioned before Linux equivalents. The Azure CLI is cross-platform, and the documentation explicitly notes that commands can run in either shell, providing syntax for both. No Linux/macOS functionality is missing.
Recommendations
- Continue providing both bash and PowerShell examples to maintain parity.
- Consider alternating the order of examples (sometimes showing PowerShell first) to avoid any perception of Windows-first bias.
- Explicitly state in the prerequisites that all CLI commands are supported on Linux, macOS, and Windows for clarity.
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 presented immediately after Bash in every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'). This creates a mild Windows bias, as Linux/macOS users may perceive the PowerShell examples as unnecessary or confusing. However, Bash examples are present and complete, so Linux users can follow the instructions without issue.
Recommendations
- Consider grouping Bash and PowerShell examples under explicit tabs or sections labeled 'Linux/macOS (Bash)' and 'Windows (PowerShell)' for clarity.
- If possible, present Bash examples first, as Azure CLI is cross-platform and Bash is the default shell for many users.
- Add a brief note explaining that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
- Ensure that Bash examples are always complete and not dependent on PowerShell-specific syntax.
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 no mention of Linux/macOS-specific shell environments or considerations. The instructions for uploading files reference Azure Cloud Shell generically, but do not clarify OS-specific steps or highlight Bash usage. PowerShell is a Windows-centric tool, though it is now cross-platform; its prominence may create friction for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash-specific instructions or examples where relevant.
- Clarify that PowerShell is available cross-platform, but highlight Bash as the default shell for Linux/macOS users in Azure Cloud Shell.
- Consider adding a note or section for Linux/macOS users, including tips for file uploads and environment setup.
- Ensure that CLI examples are shown first or equally with PowerShell to avoid Windows-first impression.
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 command, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may create a perception of Windows bias. There are no Linux-specific tools or workflows mentioned, but Bash examples are present, ensuring Linux parity.
Recommendations
- Ensure Bash examples are shown first, as Bash is the default shell for most Linux and macOS users.
- Clearly label Bash and PowerShell sections, possibly using tabs or headings, to avoid confusion.
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS, and PowerShell for Windows.
- If possible, provide a single Bash example unless there is a PowerShell-specific need.
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 alongside CLI, and there is no mention of Linux-specific shell environments (e.g., Bash) or macOS. The prerequisites section includes Azure PowerShell requirements, which are more relevant to Windows users, and PowerShell is shown as a first-class option, potentially creating friction for Linux/macOS users who may prefer Bash or other shells.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell examples are provided.
- Add Bash shell examples or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
- In prerequisites, highlight cross-platform installation instructions for Azure CLI and PowerShell Core.
- Consider listing Azure CLI (Bash) examples first, as CLI is more universally accessible.
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 (a Windows-centric tool) is featured equally alongside Azure CLI, and the documentation references Azure PowerShell requirements in the prerequisites. There is minor bias in that PowerShell is presented as a primary option, which may create friction for Linux/macOS users who typically use Bash or Azure CLI.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool for deployment, listing CLI examples first.
- Clarify that Azure PowerShell is available on Linux/macOS, but recommend Azure CLI for non-Windows users.
- Add a Bash shell example for deploying the ARM template using Azure CLI, to further improve Linux parity.
- Explicitly mention that all steps can be completed on Linux/macOS using Azure CLI and Azure Cloud 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 PowerShell examples are shown immediately after Bash in each step, and the PowerShell formatting is explicitly called out. There are no Linux-specific tools or patterns mentioned, but the presence of PowerShell examples throughout and their prominence may suggest a mild Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples with OS context (e.g., 'For Linux/macOS' and 'For Windows') to help users quickly identify relevant instructions.
- Consider showing Bash examples first, or alternating which example appears first, to avoid implicit prioritization.
- Add a note clarifying that Bash examples are for Linux/macOS terminals and PowerShell examples are for Windows, to improve clarity for cross-platform users.
- Ensure parity in explanations, and avoid unnecessary PowerShell-specific syntax unless required.
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 immediately after Bash in every step, and the PowerShell formatting is explicitly called out. There is no explicit Linux/macOS example or mention, and PowerShell is primarily a Windows shell, though it is now cross-platform. The Bash examples are generic, but the PowerShell examples may create a perception of Windows bias, especially as PowerShell is not the default shell on most Linux/macOS systems.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell examples are for Windows users.
- Consider labeling the code blocks as 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for clarity.
- If possible, provide explicit instructions or notes for Linux/macOS users, such as how to run Azure CLI commands in their default environments.
- Ensure that Bash examples are shown first, or at least equally, to avoid 'windows_first' bias.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides Azure CLI examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown second. There is a clear effort to support both Linux/macOS and Windows users, and no Windows-specific tools or patterns are prioritized. However, the presence of PowerShell examples alongside bash may be interpreted as a minor 'windows_first' bias, since PowerShell is primarily a Windows shell (though now available cross-platform). No Linux examples are missing, and no Windows-exclusive tools are mentioned.
Recommendations
- Continue providing both bash and PowerShell examples to ensure parity.
- Consider clarifying that PowerShell examples are also valid for Linux/macOS, since PowerShell Core is cross-platform.
- Explicitly state that all CLI commands work on Linux, macOS, and Windows, to reassure non-Windows users.
- If possible, provide a note on how to install Azure CLI and extensions on Linux/macOS, or link to relevant setup guides.
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 PowerShell example is given equal prominence. There is a minor bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the page metadata includes 'devx-track-azurepowershell', suggesting a focus on PowerShell. 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 it is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Add a note explicitly stating that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell snippets or instructions for Linux/macOS users, especially for file operations (e.g., saving/uploading the Bicep file).
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 consistently presents bash (Linux/macOS) examples first, followed by PowerShell (Windows) syntax. There are no Windows-only tools or patterns, and all instructions are cross-platform. However, PowerShell examples are included throughout, which may be unnecessary for Linux/macOS users. Visual Studio Code is recommended, which is cross-platform, and no Windows-specific tools are mentioned.
Recommendations
- Consider grouping bash and PowerShell examples in collapsible tabs or sections to reduce clutter and clarify platform relevance.
- Explicitly state that all CLI commands are cross-platform and clarify when PowerShell syntax is needed.
- Add a brief note at the start of CLI sections indicating that bash examples are for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant instructions.
- If possible, provide a single, generic CLI example unless syntax differences are significant.
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 appear immediately after the Bash examples. There is a slight bias in favor of Windows/PowerShell users, as PowerShell examples are given equal prominence and are not clearly separated as 'Windows' vs 'Linux/macOS'. No Linux-specific tools or patterns are missing, but the dual-formatting may create friction for Linux/macOS users.
Recommendations
- Clearly label Bash examples as 'Linux/macOS' and PowerShell examples as 'Windows', so users can easily identify which applies to their platform.
- Consider placing Bash (Linux/macOS) examples before PowerShell (Windows) examples, or use tabs to allow users to select their platform.
- Ensure that Bash examples are fully functional and do not rely on Windows-specific syntax or features.
- Add a brief note clarifying that Azure CLI works cross-platform and that Bash examples are suitable for Linux/macOS terminals.
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. This creates a slight bias toward Windows users, as Linux/macOS users may find the PowerShell examples unnecessary or confusing. There are no missing Linux examples, but the presence of PowerShell throughout suggests a Windows-first approach.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash is shown first for cross-platform parity.
- Consider separating Bash and PowerShell examples into distinct tabs or sections, rather than showing both inline.
- Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows users.
- Review variable naming consistency (e.g., $apicObjID vs. $apimID) 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. However, Azure PowerShell is highlighted as a primary option alongside Azure CLI, and PowerShell examples are given equal prominence. There is minor bias in listing PowerShell as a main deployment method, which is more common on Windows, but Linux/macOS users are not excluded and can follow the Azure CLI instructions.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell, or clarifying that PowerShell is primarily for Windows users.
- Add a brief note about using Bash or other shells for Linux/macOS users, if relevant.
- Ensure prerequisites and environment setup sections clearly indicate cross-platform compatibility.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence and is mentioned in metadata and prerequisites. There is a slight bias in that PowerShell (a Windows-centric tool) is featured alongside CLI, and the metadata includes 'devx-track-azurepowershell', which may suggest a Windows focus. However, Linux users can use Azure CLI and Cloud Shell, and no critical steps are Windows-only.
Recommendations
- Ensure Azure CLI examples are shown first, as CLI is cross-platform.
- Explicitly mention that Azure CLI and Azure Cloud Shell are available on Linux/macOS.
- Add a note clarifying that PowerShell Core is available cross-platform, but Azure CLI is recommended for Linux/macOS users.
- Remove or balance metadata tags if they suggest a Windows/PowerShell focus unless required for tracking.
- Consider adding a Bash script example for Linux users, 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
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 is explicitly labeled. There are frequent references to running Azure CLI in PowerShell, and notes clarify that commands can run in either shell. However, Linux/macOS users are not given additional guidance or troubleshooting tips, and Visual Studio Code is the only editor mentioned, which is cross-platform but often associated with Windows. No Windows-only tools or patterns are used, but the ordering and explicit PowerShell labeling create a minor Windows-first impression.
Recommendations
- Provide explicit Linux/macOS troubleshooting tips or notes where relevant (e.g., file path differences, shell environment setup).
- Consider showing bash examples first, or alternating the order to avoid implicit Windows prioritization.
- Add references to other popular cross-platform editors (e.g., JetBrains Rider, Vim, etc.) if relevant.
- Clarify that all steps are fully supported on Linux/macOS, and mention any OS-specific caveats if they exist.
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 both shell types shown side-by-side. However, in several sections, PowerShell examples are labeled as 'Formatted for PowerShell' and are consistently shown after the bash examples, indicating a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive Windows instructions are present. Linux parity is generally maintained, but bash examples are always shown first.
Recommendations
- Consider alternating the order of bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state at the beginning that both Linux/macOS (bash) and Windows (PowerShell) are fully supported and that examples are provided for both.
- Where possible, clarify that Azure CLI commands work identically across platforms, and highlight any platform-specific differences only if they exist.
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 CLI command, and in some cases, PowerShell syntax is shown immediately after Bash, suggesting a Windows-first or PowerShell-heavy bias. There are no Linux-specific tools or patterns missing, but the PowerShell examples may be unnecessary for cross-platform parity, as Bash covers Linux/macOS users.
Recommendations
- Consider grouping Bash and PowerShell examples under clear tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to clarify platform relevance.
- If Bash examples are sufficient for Linux/macOS, PowerShell examples could be moved to a secondary position or made optional.
- Explicitly state which examples are for Windows and which are for Linux/macOS to avoid confusion.
- Ensure Bash examples are shown first or equally prominent for 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 PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence. There is no explicit Linux/macOS bias, but PowerShell is presented as a standard option, which may create friction for Linux/macOS users. Azure CLI is cross-platform and is shown first, which mitigates the bias somewhat.
Recommendations
- Clarify that Azure PowerShell is available on Linux/macOS (via .NET Core), or note its Windows origins.
- Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider adding a Bash shell example (using Azure CLI) to reinforce Linux parity.
- If relevant, add a note about using Cloud Shell (which supports both CLI and PowerShell) from any 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, but PowerShell examples are shown immediately after Bash for every step, indicating a slight Windows-first bias. There is no exclusive use of Windows tools, and Linux examples are present, but the PowerShell formatting is given equal prominence, which may create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Consider showing Bash examples first, as Bash is the default shell for Azure CLI and most cross-platform environments.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify the relevant example.
- If possible, provide a single cross-platform example (Bash) unless PowerShell-specific syntax 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 deployment instructions, but PowerShell is featured equally alongside CLI, and PowerShell is a Windows-centric tool. The prerequisites section includes Azure PowerShell requirements, which are primarily relevant for Windows users. However, Azure CLI examples are present and shown first in the deployment section, and Cloud Shell (cross-platform) is mentioned.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes about cross-platform compatibility, highlighting that Azure CLI works natively on Linux/macOS.
- Ensure that all instructions (e.g., file upload, path usage) are clear for Linux/macOS users, such as mentioning how to upload files in Cloud Shell or referencing Linux file paths.
- Consider adding a short section or callout for Linux/macOS users, confirming that all steps are supported and providing any OS-specific tips.