API Center
108
Total Pages
92
Linux-Friendly Pages
16
Pages with Bias
14.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
41 issues found
Showing 1-25 of 41 flagged pages
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-kv-secret-user.md
.../includes/configure-managed-identity-kv-secret-user.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 examples are labeled as 'Formatted for PowerShell' and are always presented immediately after the Bash examples. However, the PowerShell examples use Windows-specific syntax (e.g., backticks for line continuation, $variable assignment), and there is no explicit mention of Linux or macOS environments. The documentation does not clarify which example is for which OS, and the PowerShell examples may be confusing for non-Windows users. There is also a lack of explicit Linux/macOS context or troubleshooting, and the ordering of examples (Bash first, then PowerShell) could be interpreted as a mild 'windows_first' bias, especially since PowerShell is a Windows-native shell.
Recommendations
- Clearly label Bash examples as 'Linux/macOS (Bash)' and PowerShell examples as 'Windows (PowerShell)' to avoid confusion.
- Provide a brief note explaining which shell/environment each example is intended for.
- Consider including troubleshooting notes or environment setup instructions for both Linux/macOS and Windows users.
- If possible, provide parity in example depth and clarity for both platforms, and avoid assuming PowerShell is the default for Windows users.
- Ensure that Linux/macOS users are not required to adapt PowerShell-specific syntax.
Create Pull Request
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-notification-workflow.md
...in/articles/api-center/set-up-notification-workflow.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong bias toward Windows and Microsoft-centric tools and workflows. All examples and instructions are built around the Azure Portal, Logic Apps, and Microsoft Teams, with no mention of Linux-compatible alternatives or cross-platform notification tools. There are no CLI, Bash, or non-Microsoft notification examples, and the only automation platforms referenced are Logic Apps and Power Automate, both of which are primarily accessed via the Azure Portal (a web GUI) and are closely tied to the Microsoft ecosystem. The notification workflow is exclusively demonstrated using Microsoft Teams, with no mention of alternatives like Slack or email, which are commonly used in Linux environments. The documentation also consistently references the Azure Portal UI, which, while web-based, is presented in a way that assumes familiarity with Microsoft patterns and does not provide parity for users who prefer or require command-line or Linux-native tools.
Recommendations
- Provide equivalent examples using Azure CLI and/or Azure PowerShell, and ensure CLI examples are given equal prominence.
- Include instructions for setting up similar workflows using cross-platform tools such as Bash scripts, curl, or automation via GitHub Actions or other CI/CD tools that are popular in Linux environments.
- Offer notification workflow examples that use email, Slack, or other cross-platform messaging services in addition to Microsoft Teams.
- Explicitly mention that Logic Apps and Power Automate can be triggered and managed via CLI or REST API, and provide links or examples.
- Add a section or callout for Linux users, highlighting any differences or additional steps needed for non-Windows environments.
- Avoid assuming the use of the Azure Portal for all steps; provide alternatives for users who prefer command-line or infrastructure-as-code approaches (e.g., ARM/Bicep, Terraform).
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-arm-template.md
.../articles/api-center/set-up-api-center-arm-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides deployment examples using Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is mentioned as a primary method, which may bias towards Windows users. References to uploading files in Azure Cloud Shell are neutral, but the lack of bash or Linux-native command examples is notable.
Recommendations
- Add explicit bash/Linux shell examples for deploying ARM templates, such as using curl/wget with az CLI.
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and consider listing CLI examples before PowerShell.
- If PowerShell is included, note that PowerShell Core is cross-platform, or provide bash equivalents for all PowerShell commands.
- Review included prerequisite content to ensure Linux and macOS environments are addressed equally.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-bicep.md
...ob/main/articles/api-center/set-up-api-center-bicep.md
High 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 Bicep files, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced in prerequisites and deployment steps. There is no mention of Linux-native shells or tools (e.g., Bash), and PowerShell is included as a primary workflow, which may bias the documentation towards Windows users.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool, since it works natively on Linux, macOS, and Windows.
- Clearly state that all Azure CLI commands work on Bash (Linux/macOS) and Windows Command Prompt/PowerShell.
- Add explicit Bash shell examples or notes for Linux/macOS users, especially for file operations (e.g., uploading Bicep files in Cloud Shell or copying files).
- If PowerShell is included, clarify that it is available cross-platform, or provide a note for Linux users on how to install and use PowerShell if desired.
- Review included prerequisite content to ensure Linux and macOS users are equally addressed, not just Windows/PowerShell users.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-notification-workflow.md
...in/articles/api-center/set-up-notification-workflow.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (a web UI most commonly accessed from Windows environments) and Microsoft Teams for workflow automation, with no mention of Linux-native tools or alternatives. All examples and screenshots are based on the Azure Portal and Microsoft Teams, which are typically associated with Windows-centric workflows. There are no CLI, Bash, or Linux automation examples, nor are Linux notification tools (such as Slack, email, or open-source equivalents) referenced. The only alternative workflow tool mentioned is Power Automate, another Microsoft/Windows-centric solution.
Recommendations
- Add examples using Azure CLI and Bash scripts to configure API Center, Logic Apps, and event subscriptions, making the workflow accessible from Linux environments.
- Include automation and notification examples using open-source or cross-platform tools (e.g., Slack, email via SendGrid, or other webhook-compatible services) alongside Microsoft Teams.
- Provide instructions for configuring workflows via REST API calls, which can be executed from any OS, not just via the Azure Portal.
- Mention and demonstrate how Linux users can perform equivalent tasks without relying on Windows-specific tools or GUIs.
- Reference PowerShell only as one option, and provide parity with Bash or other Linux shell scripting examples.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/register-discover-mcp-server.md
...in/articles/api-center/register-discover-mcp-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing the Azure portal (a web-based tool often associated with Windows-centric workflows) as the primary method for registering and discovering MCP servers. There are no command-line examples (e.g., Azure CLI, Bash, or PowerShell), and no Linux-specific tools or workflows are mentioned. The only development tool referenced is Visual Studio Code, which is cross-platform, but the overall workflow assumes use of the Azure portal, which is more familiar to Windows users. There are no explicit Linux or cross-platform command-line examples or instructions.
Recommendations
- Add Azure CLI and/or Bash examples for registering and managing MCP servers to provide parity with the Azure portal instructions.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to reduce the perception of a Windows-only workflow.
- Include references to Linux-compatible tools and workflows, such as using curl or other command-line utilities to interact with APIs.
- Provide PowerShell and Bash script examples side-by-side where scripting is relevant.
- Clarify that Visual Studio Code is cross-platform and suggest other editors or tools popular in Linux environments if appropriate.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-arm-template.md
.../articles/api-center/set-up-api-center-arm-template.md
High 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 ARM templates, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned before Bash or Linux-native tools. There are no explicit Bash or Linux shell script examples, and the PowerShell requirements are called out in a dedicated section. The documentation does not mention Linux-specific tools or workflows, and the structure implies parity between PowerShell and CLI, despite CLI being more cross-platform.
Recommendations
- Add explicit Bash/Linux shell script examples for deploying ARM templates, in addition to Azure CLI and PowerShell.
- Mention that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, while PowerShell is more common on Windows.
- If possible, provide Bash one-liners or scripts for common deployment tasks.
- List Azure CLI (Bash) examples before PowerShell to reduce Windows-first impression.
- Clarify in prerequisites that Azure CLI is recommended for Linux/macOS users.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/synchronize-aws-gateway-apis.md
...in/articles/api-center/synchronize-aws-gateway-apis.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a Windows bias by referencing the Azure portal (a web GUI, often associated with Windows workflows) and by providing Azure CLI examples with a note that they can run in PowerShell or bash, but does not provide explicit Linux shell (bash) examples where variable syntax might differ. The instructions and screenshots are oriented toward the Azure portal, which is more familiar to Windows users. There are no explicit Linux-specific instructions or troubleshooting tips, and the documentation does not mention Linux tools or patterns (e.g., using environment variables, curl, or jq).
Recommendations
- Provide explicit bash/Linux shell examples for Azure CLI commands, especially where variable syntax differs from PowerShell.
- Include screenshots or instructions for using the Azure CLI in a Linux terminal.
- Mention and link to Linux-native tools or workflows where relevant (e.g., using the CLI in WSL, bash, or native Linux).
- Clarify in prerequisites that the instructions are cross-platform and highlight any platform-specific steps.
- Add troubleshooting tips for common Linux-specific issues (e.g., permissions, path differences).
API Center
Workflow automation after API registration - Azure API Center
...in/articles/api-center/set-up-notification-workflow.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure Portal (web UI) for all workflow steps, which is a cross-platform tool, but it implicitly assumes users are in a Microsoft-centric environment. All notification examples use Microsoft Teams, and alternative Linux-friendly notification channels (e.g., Slack, email, webhook) are not mentioned. There are no CLI, PowerShell, Bash, or REST API examples, and no Linux/macOS-specific guidance. The only automation alternative mentioned is Power Automate, another Microsoft product. The documentation does not provide parity for Linux/macOS users who may prefer scripting, CLI, or non-Microsoft notification tools.
Recommendations
- Add equivalent workflow setup instructions using Azure CLI and REST API, which are cross-platform and commonly used on Linux/macOS.
- Include examples for sending notifications to other platforms (e.g., Slack, email, webhook) in addition to Microsoft Teams.
- Mention and provide steps for configuring the workflow using Infrastructure as Code (e.g., ARM templates, Bicep, Terraform) for automation across platforms.
- Explicitly state that all steps can be performed from any OS via the Azure Portal, but highlight CLI and API alternatives for users who prefer command-line or scripting approaches.
- List Linux/macOS tools and patterns (e.g., Bash scripts, curl) where relevant.
API Center
Workflow automation after API registration - Azure API Center
...in/articles/api-center/set-up-notification-workflow.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented around the Azure Portal GUI and Microsoft Teams, both of which are most commonly used in Windows environments. There are no CLI, PowerShell, Bash, or Linux-native workflow examples. All instructions assume use of the Azure Portal (web), and integration with Microsoft Teams (a Microsoft product with best support on Windows). No mention is made of Linux/macOS alternatives, nor are there examples using cross-platform tools like Azure CLI, REST API, or open-source notification systems.
Recommendations
- Add equivalent instructions for setting up the workflow using Azure CLI or REST API, which are cross-platform and usable on Linux/macOS.
- Provide examples of integrating with alternative notification systems (such as Slack, email, or webhook endpoints) that are platform-agnostic.
- Explicitly mention that the Azure Portal and Microsoft Teams are available on web and desktop clients for Linux/macOS, and link to relevant installation or usage guides.
- Include screenshots or step-by-step instructions for Linux/macOS users where applicable.
- Clarify any prerequisites or limitations for users on non-Windows platforms.
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-first bias by exclusively referencing Visual Studio Code (VS Code) and its extensions, which are cross-platform but are often associated with Windows workflows. All instructions and screenshots are tailored to VS Code usage, with no mention of Linux-specific tools, terminal commands, or alternative editors. Keyboard shortcuts and troubleshooting steps are presented in a way that assumes a Windows environment (e.g., Ctrl+Shift+P), and there are no examples or guidance for Linux users or those using non-Microsoft authentication methods.
Recommendations
- Explicitly mention that VS Code and its extensions are available on Linux and macOS, and provide links or instructions for installation on those platforms.
- Include Linux-specific keyboard shortcuts (e.g., Ctrl+Shift+P is the same, but clarify if there are differences) and note any platform-specific UI differences.
- Add troubleshooting steps relevant to Linux environments, such as checking environment variables, file permissions, or network configurations.
- Provide examples or guidance for using the Azure API Center from the command line (e.g., Azure CLI) or alternative editors (such as Vim or Emacs) where possible.
- Clarify that Microsoft Entra ID and Azure RBAC are platform-agnostic, and provide links to documentation for configuring these on Linux.
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 case, and the PowerShell formatting is explicitly called out. This may signal a slight Windows bias, as Linux shell usage is treated as the default but Windows/PowerShell is always included and highlighted. There are no Linux-specific tools or patterns mentioned, but the parity is reasonable.
Recommendations
- Clarify in the introduction that both Bash (Linux/macOS) and PowerShell (Windows) examples are provided for cross-platform users.
- Consider alternating the order of examples, or grouping them under explicit OS tabs (e.g., 'Linux/macOS', 'Windows') for clarity.
- Ensure that any OS-specific nuances (such as environment variable handling or path formats) are explained for both platforms.
- If possible, provide guidance for users of WSL (Windows Subsystem for Linux) or other cross-platform environments.
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
Windows First
Powershell Heavy
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell shells, but consistently lists PowerShell examples immediately after Bash, and explicitly formats commands for PowerShell. Notes repeatedly mention PowerShell as a supported environment, and variable syntax differences are called out. There is no mention of Linux-specific tools, nor are Linux distributions or shells (other than Bash) discussed. Windows/PowerShell is given equal or slightly more prominence than Linux/Bash, suggesting a subtle Windows bias.
Recommendations
- Explicitly state that all CLI commands work equally well on Linux, macOS, and Windows, and mention supported shells (e.g., Bash, Zsh, Fish) on Linux.
- Provide examples for additional Linux shells (e.g., Zsh) if syntax differs, or clarify that Bash examples apply to most Linux shells.
- List Bash/Linux examples before PowerShell, or alternate the order to avoid implicit prioritization.
- Add a note about running Azure CLI in native Linux environments (e.g., Ubuntu, CentOS) and on macOS.
- Reference installation instructions for Azure CLI on Linux and macOS alongside Windows.
- Avoid unnecessary emphasis on PowerShell unless there is a specific Windows-only scenario.
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
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 case, and the PowerShell formatting is explicitly called out. There is no mention of Linux-specific tools, nor are Linux workflows prioritized or explained in detail. The portal instructions are platform-neutral, but the CLI section leans toward Windows parity by always including PowerShell and not, for example, Zsh or other Linux shell variants.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly in a note at the start of the CLI section.
- Consider providing examples for other popular Linux shells (e.g., Zsh) if syntax differs, or explicitly state that Bash commands work for most Linux/macOS environments.
- Ensure that Bash examples appear first and are clearly marked as the default for cross-platform usage.
- Add a short section or note on how to run Azure CLI commands on Linux/macOS, including installation and environment setup if relevant.
- Avoid labeling PowerShell examples as 'Formatted for PowerShell' without a corresponding 'Formatted for Bash' label, to avoid implying PowerShell is the primary or default shell.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-bicep.md
...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 Bicep files, but PowerShell is mentioned alongside CLI throughout, and there is no mention of Bash or Linux-specific shell environments. The prerequisites and tooling sections reference Azure PowerShell requirements, which are Windows-centric, and the overall structure tends to present PowerShell as a primary option, which may implicitly prioritize Windows users.
Recommendations
- Explicitly mention Bash or Linux shell environments in the prerequisites and deployment sections.
- Add Bash-specific instructions or notes where relevant, especially for file handling and environment setup.
- Ensure that Azure CLI examples are clearly marked as cross-platform and, where possible, provide additional context for Linux/macOS users (e.g., file paths, uploading files in Cloud Shell).
- Avoid positioning PowerShell as the default or primary method; instead, clarify that both CLI and PowerShell are supported equally across platforms.
- Include troubleshooting tips or links for common Linux/macOS issues (e.g., file permissions, path formats) when working with Bicep and Azure CLI.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/enable-api-analysis-linting.md
...ain/articles/api-center/enable-api-analysis-linting.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently presents Bash (Linux/macOS) examples first, followed by PowerShell (Windows) syntax. However, there is a notable emphasis on Visual Studio Code (VS Code) with Azure Functions extension for deployment, which is cross-platform but more commonly associated with Windows workflows. The documentation does not provide any Linux-specific tools or workflows outside of Bash CLI usage, and all portal-based instructions are platform-agnostic. There are no exclusive Windows-only tools or patterns, but PowerShell syntax is always included, indicating a slight bias toward Windows users.
Recommendations
- Ensure that all command-line examples are tested and work in both Bash (Linux/macOS) and PowerShell (Windows) environments.
- Explicitly mention that Visual Studio Code and the Azure Functions extension are available and supported on Linux and macOS, not just Windows.
- Where possible, include references to alternative Linux-native editors (such as Vim or Emacs) for users who may not use VS Code.
- Clarify that all Azure CLI commands can be run in native Linux terminals without requiring PowerShell.
- Consider adding a short section or note highlighting any Linux-specific considerations or troubleshooting tips.
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 consistently references Visual Studio Code and its extension ecosystem, which is cross-platform, but all keyboard shortcuts and UI instructions use Windows conventions (e.g., Ctrl+Shift+P) without mentioning Linux or macOS equivalents. There are no explicit Linux/macOS-specific instructions, troubleshooting steps, or examples, and no mention of platform-specific differences. This subtly prioritizes Windows users and may confuse or inconvenience Linux/macOS users.
Recommendations
- Include keyboard shortcut equivalents for Linux (e.g., Ctrl+Shift+P is the same, but Cmd+Shift+P for macOS) and mention them explicitly.
- Add notes or sections clarifying that all instructions apply equally to Linux and macOS, or call out any platform-specific differences if they exist.
- If screenshots are provided, consider including at least one from a Linux or macOS environment, or note that the UI may look slightly different.
- Explicitly state that the Visual Studio Code extension and all features described are supported on Linux, macOS, and Windows.
- In troubleshooting, mention any platform-specific issues or links to platform-specific VS Code documentation.
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
Windows First
Powershell Heavy
Summary
The documentation provides both bash and PowerShell examples for Azure CLI commands, but PowerShell examples are consistently presented immediately after bash, with explicit formatting for PowerShell. There is a note clarifying differences in variable syntax between bash and PowerShell, but no mention of other Linux shells or environments. The documentation does not show exclusive use of Windows tools, but the prominence and parity given to PowerShell may suggest a slight Windows-first bias.
Recommendations
- Explicitly mention that bash examples work on Linux, macOS, and Windows (via WSL or native bash).
- Include a brief note about running Azure CLI in native Linux/macOS terminals, not just bash or PowerShell.
- Consider providing examples for other common shells (e.g., zsh, fish) or clarify that bash syntax is broadly applicable.
- Ensure that Linux/macOS users are addressed in prerequisites and environment setup sections.
- Review and balance the order of examples so that Linux-first or cross-platform parity is maintained, rather than consistently listing PowerShell second.
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
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 labeled as 'Formatted for PowerShell' and always appear immediately after the Bash examples. There is no explicit mention of Linux or macOS, and the PowerShell examples may suggest a Windows-first approach. However, both platforms are technically covered. No Linux-specific tools or shell patterns are discussed, and the portal instructions are platform-agnostic.
Recommendations
- Explicitly mention that the Bash examples are suitable for Linux and macOS users, and the PowerShell examples are for Windows users.
- Consider using tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for greater clarity.
- Ensure that any platform-specific prerequisites (e.g., installing Azure CLI on Linux) are referenced or linked.
- If possible, provide a short note at the start of the CLI section explaining which example to use based on the user's operating system.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/configure-managed-identity-kv-secret-user.md
.../includes/configure-managed-identity-kv-secret-user.md
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 versions are labeled as 'Formatted for PowerShell' and appear immediately after the Bash examples. There is a slight Windows bias in that PowerShell (a Windows-centric shell) is given parity with Bash, and the variable assignment syntax in PowerShell is shown for every step. However, Linux-specific considerations (such as shell differences or troubleshooting) are not discussed, and the examples do not mention alternative Linux tools or workflows beyond Bash.
Recommendations
- Clarify which examples are for Bash (Linux/macOS) and which are for PowerShell (Windows), possibly using tabs or clearer headings.
- Ensure that Linux/Bash examples are presented first, or at least equally, to avoid implicit prioritization of Windows/PowerShell.
- Add troubleshooting notes or tips for common issues on Linux (e.g., permissions, environment differences).
- Mention that Bash examples work on macOS as well as Linux, and clarify any platform-specific caveats.
- Consider including a note about using WSL (Windows Subsystem for Linux) for users on Windows who prefer Bash.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/vscode-extension-basic-prerequisites.md
...enter/includes/vscode-extension-basic-prerequisites.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references Visual Studio Code and its Azure API Center extension, both of which are cross-platform, but does not mention or provide examples for Linux-specific tools, editors, or workflows. There is an implicit bias toward Windows environments by focusing on Visual Studio Code (which, while cross-platform, is often associated with Windows) and not acknowledging alternative editors or command-line workflows common on Linux.
Recommendations
- Explicitly state that Visual Studio Code and the Azure API Center extension are available on Linux and macOS, not just Windows.
- Mention or provide examples for alternative editors or command-line tools that Linux users might prefer (e.g., Vim, Emacs, or using Azure CLI directly).
- Include instructions or links for installing Visual Studio Code and the extension on Linux.
- If possible, add a section or note about using the Azure API Center with Linux-native tools or workflows.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-portal.md
...b/main/articles/api-center/set-up-api-center-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing only the Azure portal (a web-based tool, but often associated with Windows-centric workflows) and Visual Studio Code (commonly used on Windows, though cross-platform). There are no explicit Linux-specific instructions, command-line examples, or mentions of Linux tools. No PowerShell or CLI examples are provided, but the absence of Linux terminal or shell instructions means Linux users may feel underrepresented.
Recommendations
- Add Azure CLI and/or Azure PowerShell command examples for key setup steps, and ensure both Windows and Linux shells are covered.
- Explicitly mention that the Azure portal and Visual Studio Code are cross-platform, and provide links or notes for Linux users where relevant.
- Include troubleshooting or setup notes for common Linux environments (e.g., Ubuntu, Fedora) where applicable.
- If any downloadable scripts or code snippets are provided, ensure they are compatible with Bash/zsh as well as PowerShell.
- Consider adding a section or callout for Linux users to clarify any OS-specific considerations.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/tutorials/configure-environments-deployments.md
...center/tutorials/configure-environments-deployments.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (a web-based GUI) for all instructions, with no mention of command-line tools or automation options. There are no examples using cross-platform tools such as Azure CLI, nor are there any references to Linux-specific workflows. The only tool referenced is the Azure portal, which is platform-agnostic but often associated with Windows-centric workflows in Azure documentation. No PowerShell or Windows-only commands are present, but the lack of CLI or Linux examples creates an implicit bias.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
- If automation is possible, provide examples using both Azure CLI and PowerShell, and present CLI examples first or side-by-side.
- Explicitly mention that the Azure portal is accessible from any OS/browser to avoid the impression of a Windows-only workflow.
- Include screenshots or terminal examples from Linux environments where relevant.
- Reference documentation or tutorials for Linux users, such as installing and using Azure CLI on Linux.
API Center
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/quickstart-template-review-resources.md
...enter/includes/quickstart-template-review-resources.md
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 usage. Azure PowerShell is primarily a Windows tool, and its mention before any Linux alternatives (such as Bash or shell scripting) suggests a Windows-first perspective.
Recommendations
- Include explicit examples using Azure CLI in Bash or other Linux shells.
- Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (PowerShell) and Linux (Bash).
- Mention Linux-native tools or patterns where appropriate.
- Avoid listing Windows-specific tools (like Azure PowerShell) before cross-platform alternatives unless contextually justified.
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 (Windows) examples are given immediately after Bash in every step, and are labeled 'Formatted for PowerShell'. There is no explicit Linux/macOS bias, but the presence of PowerShell examples throughout and the order in which they are presented (always Bash first, then PowerShell) suggests a mild Windows bias. However, Bash examples are present and usable for Linux/macOS users.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Consider adding a note at the top of the CLI section indicating which shell is appropriate for each platform.
- Ensure parity by verifying that all Bash commands work as expected on Linux/macOS.
- Optionally, use tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for clearer distinction.