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
181 issues found
Showing 26-50 of 181 flagged pages
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-apim-reader.md
...ter/includes/configure-managed-identity-apim-reader.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell (Windows) examples are given immediately after the Bash ones, and are explicitly labeled as 'Formatted for PowerShell.' There is no explicit mention of Linux or macOS environments, and the Bash examples are not clearly labeled as 'Linux/macOS.' The documentation does not provide parity in guidance or troubleshooting for Linux users, and the structure may imply a Windows-first approach.
Recommendations
- Explicitly label Bash examples as 'Linux/macOS' and PowerShell examples as 'Windows' to clarify platform relevance.
- Present Bash (Linux/macOS) examples before PowerShell (Windows) examples to avoid a Windows-first impression.
- Add a brief note at the start of the CLI section explaining which example to use based on the user's operating system.
- Ensure troubleshooting tips or environment-specific notes are included for both Windows and Linux/macOS users.
- Consider providing a tabbed interface for Bash and PowerShell examples, so users can easily select their platform.
Create Pull Request
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/synchronize-api-management-apis.md
...articles/api-center/synchronize-api-management-apis.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it claims that Azure CLI command examples can run in both PowerShell and bash, the only explicit command example is given in a generic CLI format without showing both PowerShell and bash syntax where they might differ. There is mention that separate examples are provided 'where needed,' but no Linux-specific (bash) example is actually shown. The documentation also references running CLI commands in PowerShell first, and the prerequisite section for Azure CLI setup is ambiguous about Linux-specific steps or differences.
Recommendations
- Provide explicit bash/Linux command examples alongside PowerShell examples wherever variable syntax or command usage differs.
- Ensure that CLI setup instructions include Linux-specific prerequisites and installation steps, not just generic or Windows-focused guidance.
- If referencing the ability to use both PowerShell and bash, demonstrate this parity by including both sets of examples where relevant.
- Avoid language that defaults to Windows-first (e.g., mentioning PowerShell before bash), or alternate the order to show neutrality.
- Include troubleshooting or environment notes for Linux users, such as common issues with Azure CLI on Linux.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/authorize-api-access.md
.../blob/main/articles/api-center/authorize-api-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows/Azure portal bias by exclusively referencing the Azure portal UI and Microsoft Entra ID (formerly Azure Active Directory) for identity management, with no mention of Linux command-line tools, cross-platform CLI alternatives, or non-Microsoft identity providers in practical examples. There are no PowerShell-specific commands, but all workflows are described in the context of the Azure portal, which is most familiar to Windows users. There are no Linux shell/CLI examples, and no mention of using Azure CLI, REST APIs, or automation scripts that are platform-agnostic.
Recommendations
- Provide equivalent Azure CLI (az) commands for all portal-based steps, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include REST API examples for automation and platform neutrality.
- Mention and, where possible, provide examples for using non-Microsoft identity providers (e.g., Auth0, Okta) for OAuth 2.0, not just Microsoft Entra ID.
- Explicitly state that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
- Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
- If screenshots are used, consider including at least one from a non-Windows environment (e.g., browser on Linux/macOS) to reinforce cross-platform support.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence to CLI and is mentioned in metadata and prerequisites. There are no explicit Linux/macOS shell examples (e.g., Bash), and the instructions for uploading the template file reference Azure Cloud Shell generically, without clarifying Linux/macOS workflows. The documentation does not mention Linux-specific tools or patterns, and PowerShell is not clearly marked as Windows-only, which may cause confusion for Linux/macOS users.
Recommendations
- Add explicit Bash shell examples for deploying ARM templates using Azure CLI on Linux/macOS.
- Clarify that Azure PowerShell is available cross-platform, but most Linux/macOS users will prefer Azure CLI.
- Provide instructions for uploading files in Linux/macOS environments (e.g., using scp, curl, or direct download in Cloud Shell).
- Ensure that CLI examples are shown first, as they are more universally applicable.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence despite being Windows-centric. There is no mention of Linux/macOS-specific shell environments or alternative deployment methods (e.g., Bash, scripting on Linux), and PowerShell requirements are listed alongside CLI prerequisites. The order of examples does not strongly favor Windows, but the inclusion of PowerShell as a primary method may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI works natively on Linux/macOS and provide Bash-specific instructions or notes for Linux users.
- Mention that Azure Cloud Shell supports both Bash and PowerShell, and highlight Bash as a cross-platform option.
- Consider listing Azure CLI examples first, as it is cross-platform, and move PowerShell examples to a secondary position.
- Add a note or section for deploying ARM templates using Bash or other Linux-native tools (e.g., curl, jq, etc.), if applicable.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced in prerequisites and deployment instructions. There is no explicit mention of Linux/macOS-specific considerations, and PowerShell is presented as a standard method alongside CLI, which may create friction for non-Windows users. The ordering of examples is neutral, but the inclusion of PowerShell as a primary method reflects a Windows bias.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, including instructions for uploading files in Cloud Shell or using native shell commands.
- Consider listing Azure CLI examples first, as it is platform-agnostic.
- Remove or de-emphasize PowerShell as a primary method unless there are Windows-specific steps.
- Include troubleshooting notes for common Linux/macOS issues (e.g., file paths, permissions).
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell, but consistently presents PowerShell examples immediately after bash, sometimes with explicit formatting notes. There is a recurring emphasis on PowerShell syntax and usage, which may suggest a slight Windows bias. However, Linux/bash examples are present and not omitted.
Recommendations
- Alternate the order of shell examples, sometimes presenting bash first and sometimes PowerShell, or group them together for parity.
- Add explicit notes or sections for macOS users if there are any platform-specific considerations.
- Clarify that all CLI commands are cross-platform and highlight any differences or caveats for Linux/macOS users.
- Consider providing generic CLI examples without shell-specific formatting where possible, or use tabs/expanders to let users select their shell.
- Ensure that any referenced tooling, scripts, or file paths use neutral or platform-agnostic conventions.
Medium 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, and the variable assignment syntax is labeled 'Formatted for PowerShell' rather than 'Windows'. There is no explicit mention of Linux or macOS, and no examples for those platforms beyond Bash. The portal instructions implicitly assume a Windows environment due to the use of PowerShell and lack of mention of Linux-specific tools or workflows.
Recommendations
- Explicitly mention that Bash examples are suitable for Linux/macOS and that PowerShell examples are for Windows.
- Provide clear guidance on which shell to use for each operating system.
- Include notes or tabs for Linux/macOS users, such as using Bash in WSL or native terminals.
- Avoid labeling examples as 'Formatted for PowerShell' only; instead, use 'Windows (PowerShell)' and 'Linux/macOS (Bash)'.
- Consider adding troubleshooting tips for common issues on Linux/macOS (e.g., permissions, path differences).
API Center
Enable API Center portal view - Azure API Center - VS Code extension
...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and its extensions, which, while cross-platform, are most commonly associated with Windows environments. The instructions and screenshots focus on VS Code usage patterns (e.g., Ctrl+Shift+P shortcut) without mentioning Linux-specific alternatives or keyboard shortcuts. There are no examples or guidance for Linux users, such as using VS Code on Linux, or alternative CLI-based workflows. Additionally, all authentication and troubleshooting steps are described in terms of Azure and Microsoft Entra, with no mention of Linux-specific considerations or potential issues.
Recommendations
- Add explicit notes confirming that Visual Studio Code and the Azure API Center extension are supported on Linux and macOS, and provide installation instructions for those platforms.
- Include Linux/macOS keyboard shortcuts (e.g., Cmd+Shift+P for macOS) alongside Windows shortcuts.
- Provide screenshots from VS Code running on Linux or macOS, or clarify that the UI is identical across platforms.
- Mention any Linux-specific troubleshooting steps or considerations, such as package dependencies or permissions.
- If possible, offer CLI-based alternatives for connecting to the API Center, for users who prefer terminal workflows.
Medium 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 given immediately after the Bash ones, and use Windows-specific syntax (e.g., backticks for line continuation, .substring method). There is no explicit mention of Linux or macOS environments, nor any guidance for users on non-Windows platforms. The portal instructions are generic, but the CLI section leans toward Windows by including PowerShell-formatted code for each step.
Recommendations
- Explicitly state that Bash examples are for Linux/macOS and PowerShell examples are for Windows, helping users identify which to use.
- Provide clear guidance or a note at the start of the CLI section about which shell/environment each example is intended for.
- Consider listing Bash (Linux/macOS) examples first to avoid implicit Windows-first bias.
- Add troubleshooting tips or links for common issues encountered on Linux/macOS (e.g., Azure CLI installation, shell compatibility).
- Ensure parity in explanations and code comments for both Bash and PowerShell, and avoid assuming PowerShell as the default for CLI usage.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell as a tool for listing deployed resources alongside Azure CLI, but does not provide explicit Linux-specific examples or mention Linux shell tools. The ordering of 'Azure CLI or Azure PowerShell' may suggest a slight Windows-first bias, and the lack of Linux-specific guidance or examples further reinforces this.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux (bash).
- Include Linux shell examples (e.g., bash) for listing resources using Azure CLI.
- Clarify that Azure PowerShell is primarily a Windows tool, and suggest alternatives for Linux users.
- Consider reordering to mention Azure CLI before Azure PowerShell, as CLI is more universally available.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Medium 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 featured equally alongside CLI, and there is no mention of Linux-specific tools or shell environments (e.g., Bash). The prerequisites and deployment instructions do not clarify cross-platform usage, and PowerShell (traditionally Windows-centric) is presented without noting its availability on Linux. No Linux-specific examples, troubleshooting, or guidance are provided.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are cross-platform, and clarify installation steps for Linux and macOS users.
- Include Bash shell examples or instructions for Linux users, especially for file handling (e.g., copying/uploading Bicep files).
- Add troubleshooting notes or tips for common Linux issues (e.g., file permissions, path formats).
- Ensure that any referenced tools or commands (such as PowerShell) are clearly marked as available on Linux, or provide alternative commands where appropriate.
- Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Medium 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 PowerShell examples immediately after bash, and explicitly formats commands for PowerShell syntax. There is a note clarifying differences in variable syntax between bash and PowerShell, but no mention of other Linux shells or platforms. The documentation does not provide Linux-specific troubleshooting, nor does it mention Linux tools or patterns beyond bash. The repeated inclusion of PowerShell examples and explicit formatting for Windows shells suggests a mild Windows bias.
Recommendations
- Clarify that bash examples are suitable for Linux, macOS, and WSL environments.
- Add explicit references to Linux and macOS compatibility in prerequisites and notes.
- Provide troubleshooting tips or environment setup instructions for Linux users (e.g., file permissions, path formats).
- Consider including zsh or other popular Linux shell examples if syntax differs.
- Ensure that Linux examples are presented first or equally alongside PowerShell, rather than always following bash.
- Mention cross-platform CLI usage and any platform-specific caveats.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Medium 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 presented immediately after Bash, and sometimes with explicit 'PowerShell syntax' labeling. There is a slight Windows-first bias in the ordering and labeling of examples, and the use of Visual Studio Code (a cross-platform tool, but often associated with Windows) is emphasized. However, Linux parity is generally maintained, and there are no cases where only Windows or PowerShell examples are given, nor are Windows-specific tools required.
Recommendations
- Alternate the order of Bash and PowerShell examples, or present Bash first in some sections to avoid implicit prioritization.
- Explicitly mention that all steps and tools (VS Code, Azure CLI, azd) are fully supported on Linux and macOS, not just Windows.
- Where possible, provide screenshots or references for Linux/macOS environments (e.g., terminal, VS Code on Ubuntu) alongside Windows examples.
- Clarify that Visual Studio Code is cross-platform and provide links to installation instructions for Linux/macOS.
- Consider adding a short section or note at the beginning stating that all instructions are applicable to Linux, macOS, and Windows unless otherwise specified.
Medium 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 included alongside Bash, and PowerShell-specific formatting is explicitly called out. The variable assignment and string manipulation examples are tailored for PowerShell, which is primarily used on Windows. There is no mention of Linux-specific shell environments beyond Bash, and PowerShell examples are given equal prominence, suggesting a Windows-centric approach.
Recommendations
- Clearly indicate which examples are for Linux/macOS (Bash) and which are for Windows (PowerShell), possibly using tabs or headings.
- Ensure Bash examples are presented first, or at least equally, to avoid implicit prioritization of Windows.
- Consider including examples for other common Linux shells if relevant (e.g., zsh, sh), or clarify that Bash examples are applicable to most Linux environments.
- Add notes explaining differences in variable assignment and string manipulation between Bash and PowerShell, to help users on both platforms.
- Review documentation for any Windows-specific terminology or assumptions, and provide Linux/macOS equivalents where appropriate.
API Center
Enable API Center portal view - Azure API Center - VS Code extension
...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and its extensions, which are cross-platform but are most commonly associated with Windows. All instructions use Windows-centric terminology (e.g., Ctrl+Shift+P for Command Palette, screenshots with Windows UI), and there are no examples or mentions of Linux-specific workflows, keyboard shortcuts, or alternative editors. There is no mention of Linux package managers, shell commands, or how to install/use the extension on Linux. The troubleshooting and setup steps assume Azure portal and Microsoft Entra ID usage, which are platform-neutral but the developer experience described is tailored to Windows users.
Recommendations
- Include explicit instructions and screenshots for Linux users, such as using the Super/Command key instead of Ctrl where appropriate.
- Mention how to install the Azure API Center extension for VS Code via Linux package managers or command-line (e.g., code --install-extension).
- Add notes about using VS Code on Linux and macOS, including any differences in UI or keyboard shortcuts.
- Provide troubleshooting steps relevant to Linux environments (e.g., dealing with authentication issues or extension installation problems on Linux).
- Clarify that the instructions apply to VS Code on all platforms, and link to platform-specific VS Code documentation where relevant.
Medium 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 in every instance, and the PowerShell formatting is explicitly called out. There is no explicit mention of Linux or macOS environments, and the Bash examples are generic rather than specifically labeled for Linux. The portal instructions are platform-neutral, but the CLI section leans toward Windows by always pairing Bash with PowerShell and using PowerShell-specific syntax and comments.
Recommendations
- Explicitly label Bash examples as 'Linux/macOS' and PowerShell as 'Windows' to clarify platform relevance.
- Provide a brief note at the start of the CLI section explaining which environments each example applies to.
- Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows) examples to avoid implicit Windows-first bias.
- Include troubleshooting notes or links for common issues on Linux/macOS (e.g., shell compatibility, Azure CLI installation).
- Ensure parity in detail and explanation for both Bash and PowerShell examples, and avoid assuming PowerShell as the default secondary shell.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools to review deployed resources, but does not provide explicit Linux-specific examples or mention Linux shell tools. The ordering of 'Azure CLI or Azure PowerShell' puts the CLI first, which is cross-platform, but the inclusion of PowerShell (historically Windows-centric) without clarifying cross-platform support may suggest a Windows bias. No Linux-specific commands or examples are provided.
Recommendations
- Clarify that Azure CLI is cross-platform and provide explicit Linux shell examples (e.g., bash commands).
- If mentioning Azure PowerShell, note that it is available on Linux and macOS as well.
- Consider adding examples or instructions for Linux users, such as using bash or zsh with Azure CLI.
- Ensure parity by listing tools in a neutral order (e.g., 'Azure CLI or PowerShell') and avoid implying Windows-first usage.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Medium 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 given equal prominence to CLI, and there are no explicit Linux shell (bash) examples or mentions of Linux-specific tooling. The prerequisites section lists Azure PowerShell requirements immediately after Azure CLI, and the use of PowerShell may suggest a Windows-centric approach, as PowerShell is traditionally associated with Windows environments.
Recommendations
- Add explicit bash examples for Linux users, especially for file operations (e.g., copying, uploading Bicep files).
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
- Mention that PowerShell Core is cross-platform, but also provide bash alternatives for common tasks.
- Include notes or sections highlighting Linux usage patterns, such as using Azure CLI in bash or zsh shells.
- Ensure that any references to uploading files to Azure Cloud Shell include instructions for both Windows and Linux users.
Medium 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 in each step, and some variable naming (e.g., $apicObjID) is more typical of PowerShell/Windows environments. There is no explicit mention of Linux or macOS, and the structure may suggest a slight preference for Windows/PowerShell users by always including PowerShell examples and using Windows-style variable conventions.
Recommendations
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to clarify cross-platform applicability.
- Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows) examples, or alternate the order in different sections.
- Include a note about shell compatibility and how to adapt commands for different environments.
- Ensure variable naming and command formatting are idiomatic for each platform (e.g., use $var for PowerShell, var for Bash).
- Add troubleshooting tips for common issues encountered on Linux/macOS (e.g., permissions, path differences).
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both bash and PowerShell examples for Azure CLI commands, but PowerShell examples are always shown immediately after bash, and are explicitly formatted and called out. There is a slight Windows-first bias in that PowerShell is given equal prominence to bash, despite bash being the default shell on most Linux and macOS systems. No Linux-specific tools, patterns, or troubleshooting are mentioned, and there are no references to Linux distributions or package managers. However, the use of Azure CLI itself is cross-platform, and the documentation does note that commands can be run in either shell.
Recommendations
- Clearly state that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Provide guidance or troubleshooting tips for Linux users (e.g., file permissions, path formats, package installation).
- If showing both bash and PowerShell examples, alternate the order or clarify that bash is the default for Linux/macOS.
- Reference Linux package managers (apt, yum, etc.) for Azure CLI installation in the prerequisites.
- Add a note or section for common Linux-specific issues or best practices when using Azure CLI.
API Center
Enable API Center portal view - Azure API Center - VS Code extension
...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code and its extensions, which are cross-platform but are most commonly associated with Windows environments. All instructions and examples use Windows-centric patterns (e.g., Ctrl+Shift+P shortcut, VS Code UI screenshots) and do not mention or provide Linux-specific guidance, such as alternative keyboard shortcuts, installation methods, or troubleshooting steps for Linux users. There are no references to Linux tools, shell commands, or platform-specific considerations, and Windows/VS Code patterns are presented as the default without acknowledging Linux workflows.
Recommendations
- Explicitly mention that Visual Studio Code and its extensions are available on Linux and macOS, and provide installation instructions for these platforms.
- Include alternative keyboard shortcuts for Linux/macOS (e.g., Cmd+Shift+P for macOS).
- Add screenshots or descriptions of the UI on Linux/macOS, if there are differences.
- Provide troubleshooting steps specific to Linux environments, such as dealing with authentication issues or extension installation problems.
- Reference Linux-native tools or workflows where applicable, such as using the command line to launch VS Code or manage extensions.
- Clarify any platform-specific prerequisites or limitations for using the Azure API Center VS Code extension.
Medium 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 (Windows) versions are given equal prominence to Bash (Linux/macOS) versions. The PowerShell examples are labeled as 'Formatted for PowerShell', which may suggest a Windows-first approach. There is no explicit mention of Linux-specific tools or workflows, and the documentation does not clarify which example should be used on which platform, potentially confusing Linux users. The portal instructions are platform-neutral, but the CLI section could be improved for Linux parity.
Recommendations
- Clearly label Bash examples as suitable for Linux/macOS and PowerShell examples for Windows.
- Present Bash (Linux/macOS) examples before PowerShell (Windows) examples to avoid implicit Windows-first bias.
- Add a short note explaining which shell to use on which platform.
- Consider including troubleshooting tips for common Linux shell issues (e.g., quoting, environment variables).
- Ensure that all CLI instructions are tested and work as expected on Linux distributions.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/import-api-management-apis.md
...main/articles/api-center/import-api-management-apis.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides Azure CLI examples for both bash and PowerShell, but consistently lists PowerShell examples immediately after bash, and explicitly calls out PowerShell formatting. There is a notable emphasis on PowerShell, which is primarily a Windows shell, and the documentation frequently mentions that commands can run in PowerShell or bash, with separate examples for each. No Linux-specific tools or workflows are mentioned, and the parity between bash and PowerShell is maintained, but PowerShell is given equal or slightly more prominence than bash, which may subtly favor Windows users.
Recommendations
- Ensure bash examples are listed first, as bash is the default shell on Linux and macOS.
- Add explicit notes or examples for macOS users if there are any differences.
- Clarify that bash examples are applicable to Linux and macOS, and PowerShell examples are for Windows.
- Consider including troubleshooting tips or environment setup instructions for Linux users, such as file permissions or path conventions.
- If possible, provide a single cross-platform example (using Azure CLI syntax that works identically in bash and PowerShell) before splitting into shell-specific examples only where necessary.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/enable-api-center-portal-vs-code-extension.md
...i-center/enable-api-center-portal-vs-code-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing Visual Studio Code and its extensions, which are cross-platform but are most commonly associated with Windows. All examples and instructions use Windows-centric patterns (e.g., Ctrl+Shift+P shortcut, screenshots with Windows UI), and there are no explicit mentions of Linux or macOS equivalents, nor any terminal/CLI alternatives. There are no examples using Linux-specific tools, shell commands, or instructions for Linux users, and troubleshooting steps reference Azure and Microsoft Entra tools without noting cross-platform access methods.
Recommendations
- Add explicit notes that Visual Studio Code and its extensions are available on Linux and macOS, and provide links to installation instructions for those platforms.
- Include keyboard shortcut equivalents for macOS (e.g., Cmd+Shift+P) alongside Windows shortcuts.
- Provide screenshots or descriptions that show the UI on Linux/macOS, or clarify that the UI may look different on those platforms.
- Mention that all steps can be performed on Linux/macOS, and highlight any platform-specific differences in authentication or extension installation.
- If possible, offer CLI or terminal-based alternatives for connecting to the API Center, especially for users who prefer not to use a GUI.