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 51-75 of 186 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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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 are presented immediately after the Bash examples in each step. There is no explicit mention of Linux or macOS environments, and the PowerShell examples use Windows-specific syntax (e.g., `$variable=$(...)`, backticks for line continuation, `.substring()` method). The portal instructions do not mention platform differences, but the CLI section gives equal weight to PowerShell (Windows) and Bash (Linux/macOS), with PowerShell examples appearing directly after Bash in each case.
Recommendations
  • Explicitly mention that Bash examples are for Linux/macOS and PowerShell examples are for Windows, to clarify platform relevance.
  • Consider presenting Bash (Linux/macOS) examples first, or clearly label tabs as 'Linux/macOS (Bash)' and 'Windows (PowerShell)'.
  • Add a note about prerequisites for each environment (e.g., Bash shell, PowerShell, Azure CLI installation).
  • Ensure that variable naming and command syntax are consistent and correct for each platform (e.g., use `$apicObjID` for Bash, `$apicObjID` for PowerShell, but avoid mixing Bash and PowerShell variable assignment styles).
  • If possible, provide a summary table or section comparing the steps for both platforms, highlighting any differences.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Visual Studio Code and Azure tools, with all examples and instructions referencing Windows-centric workflows (e.g., Ctrl+Shift+P shortcut, Azure sign-in, Microsoft Entra ID, and GitHub Copilot in VS Code). There are no references to Linux-specific workflows, terminal commands, or alternative editors. The documentation does not mention how to perform these tasks on Linux or macOS, nor does it provide parity for non-Windows environments.
Recommendations
  • Include explicit instructions or notes for Linux and macOS users, such as alternative keyboard shortcuts (e.g., Cmd+Shift+P for macOS) and any differences in the VS Code extension installation process.
  • Add examples or screenshots showing the process on Linux and macOS, especially for sign-in flows and extension usage.
  • Clarify that the Visual Studio Code extension is cross-platform and works on Linux/macOS, and mention any prerequisites or caveats for those platforms.
  • If any CLI or terminal-based alternatives exist (e.g., Azure CLI), provide equivalent steps for Linux users.
  • Avoid language that implies Windows is the default or only supported environment; use neutral, cross-platform phrasing.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and lists it before Linux-native alternatives. There are no explicit Linux examples or references to Linux-specific tools or shell environments.
Recommendations
  • Provide explicit examples using Azure CLI in Bash or other Linux shells.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Avoid listing Azure PowerShell before Azure CLI unless PowerShell is required for a specific task.
  • Include instructions or examples for Linux users, such as command-line snippets for resource review.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
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 mentioned in prerequisites and deployment steps. There is no explicit mention of Linux-specific tools or shell environments (such as Bash), nor are there examples tailored for Linux users. The documentation assumes familiarity with PowerShell and does not clarify cross-platform usage, potentially leading to a Windows bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash-specific notes or examples where relevant.
  • Clarify that PowerShell Core is cross-platform, but most users on Linux/macOS will prefer Azure CLI.
  • Add a section or note for Linux/macOS users, including instructions for uploading files in Cloud Shell or using local Bash terminals.
  • Avoid listing PowerShell before or alongside CLI unless there is a clear cross-platform rationale; consider making CLI the default example, as it is more widely used across platforms.
  • Mention Linux tools (e.g., curl, wget, nano, vi) for file manipulation where appropriate.
GitHub Create Pull Request
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 →
Scanned: 2025-09-16 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but consistently presents Bash (Linux/macOS) syntax first, followed by PowerShell (Windows) syntax. However, the documentation refers to running commands in 'PowerShell or a bash shell' and provides explicit PowerShell syntax for every CLI example, which is not always the case in Microsoft docs. There is no exclusive use of Windows tools or patterns, and Linux users are well supported. The use of Visual Studio Code (cross-platform) and Azure CLI (cross-platform) further reduces Windows bias.
Recommendations
  • Continue providing both Bash and PowerShell examples for all CLI commands.
  • Consider explicitly stating that all tools and steps are supported on Linux, macOS, and Windows.
  • Where possible, include screenshots or references for Linux/macOS environments in addition to Azure Portal (which is OS-agnostic).
  • If any step is OS-specific (e.g., file paths, shell commands), clarify the differences for each platform.
GitHub Create Pull Request
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 →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation assumes the use of Visual Studio Code and its extensions, which are cross-platform, but all example instructions and screenshots are oriented toward the VS Code GUI and keyboard shortcuts (e.g., Ctrl+Shift+P) that are Windows-centric. There are no explicit Linux or macOS-specific instructions, nor are there any command-line alternatives or references to Linux-specific tools or patterns. The documentation does not mention any differences or considerations for Linux users, and the keyboard shortcuts and UI references are presented in a Windows-first manner.
Recommendations
  • Include keyboard shortcut alternatives for macOS (e.g., Cmd+Shift+P) and mention that shortcuts may differ on Linux.
  • Explicitly state that the Visual Studio Code extension and instructions apply to Windows, Linux, and macOS, and note any platform-specific differences if they exist.
  • Provide command-line alternatives (such as using the Azure CLI or scripts) where possible, or clarify if only the GUI is supported.
  • Add screenshots or notes that reflect the appearance of the extension on Linux and macOS, if there are any differences.
  • Ensure that any referenced tools or processes (such as authentication flows) are validated and documented for Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
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 explicitly labeled and formatted, suggesting a focus on Windows users. Additionally, PowerShell examples are presented immediately after Bash, which may imply a slight Windows-first ordering. There are no Linux-specific tools or workflows mentioned beyond Bash, and no explicit mention of Linux environments.
Recommendations
  • Clearly label Bash examples as suitable for Linux/macOS and PowerShell for Windows, to help users identify the right commands for their platform.
  • Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows) examples, or use tabs to allow users to select their OS.
  • Add a brief note clarifying that Bash examples are intended for Linux/macOS terminals and PowerShell for Windows, ensuring parity in guidance.
  • If possible, include troubleshooting notes or environment setup tips for both Linux and Windows users.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell is given equal prominence to CLI, which can be interpreted as a Windows-centric approach since PowerShell is primarily a Windows tool (despite cross-platform support). There is no mention of Linux-specific considerations, nor are there examples using native Linux tools or shell scripting. The order of presentation (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method, without similar attention to Bash scripting or Linux-native workflows, reflects a subtle Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
  • Consider adding a Bash shell script example for Linux users, especially for automation scenarios.
  • Clarify that PowerShell Core is cross-platform, but note that many Linux users may prefer Bash.
  • If referencing PowerShell, also reference Bash or other common Linux shells to ensure parity.
  • Add a brief section or note about running these commands on Linux, including any differences in file paths or environment setup.
GitHub Create Pull Request
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 →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently presents Bash examples first, followed by PowerShell. There is a note clarifying that examples can run in either shell and that differences in variable syntax are addressed with separate examples. No Windows-specific tools or patterns are mentioned, and Linux parity is generally maintained. However, the explicit labeling of 'Formatted for PowerShell' and the inclusion of PowerShell-specific syntax throughout indicate a slight bias toward Windows/PowerShell users, though not to the exclusion of Linux users.
Recommendations
  • Continue to provide both Bash and PowerShell examples, but consider alternating the order in which they are presented or grouping them side-by-side to avoid implicit prioritization.
  • Explicitly state in the prerequisites that all examples are cross-platform and tested on both Windows (PowerShell) and Linux/macOS (Bash).
  • Where possible, use variable syntax that is compatible across shells, or provide a table summarizing syntax differences.
  • Ensure that any referenced scripts or downloadable assets are compatible with both Bash and PowerShell environments.
GitHub Create Pull Request
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 →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
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 are always presented 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, Bash examples are present and shown first, which helps mitigate bias. No Windows-only tools or patterns are used, but the presence of PowerShell examples throughout and lack of explicit Linux/macOS references indicate a mild Windows bias.
Recommendations
  • Explicitly mention that the Bash examples are suitable for Linux and macOS users, and the PowerShell examples are for Windows users.
  • Add a short note clarifying cross-platform compatibility of Azure CLI and the provided scripts.
  • Consider using tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' for clearer parity.
  • Ensure that any platform-specific instructions (such as line continuation characters) are clearly explained for each OS.
GitHub Create Pull Request
API Center https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/store-secret-key-vault.md ...articles/api-center/includes/store-secret-key-vault.md
Medium Priority View Details →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions using the Azure portal GUI, which is a cross-platform web interface but often aligns with Windows-centric workflows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux-specific tools or workflows. This can disadvantage Linux users who prefer or require CLI-based automation or scripting.
Recommendations
  • Add equivalent Azure CLI examples for all steps, showing how to enable managed identity and assign roles via command line.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic, but provide links or examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) automation.
  • Include a section comparing portal-based and CLI-based approaches, highlighting when each is appropriate.
  • Ensure that any future examples or screenshots do not assume a Windows environment (e.g., file paths, UI conventions).
GitHub Create Pull Request
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 →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exclusively references Visual Studio Code and its Azure extension, which are available cross-platform but are most commonly associated with Windows environments. There is no mention of Linux-specific tools, command-line alternatives, or instructions for Linux users. No examples or guidance are provided for users who may prefer or require Linux-native workflows.
Recommendations
  • Explicitly mention that Visual Studio Code and the Azure API Center extension are available on Linux and macOS, not just Windows.
  • Provide alternative instructions or examples for Linux users, such as using the Azure CLI or other command-line tools where possible.
  • Include a note or section addressing Linux setup considerations, such as installation commands for VS Code and the extension on Linux distributions.
  • If relevant, mention any differences or limitations when using the tools on Linux compared to Windows.
GitHub 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
Medium Priority View Details →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively uses Azure Portal, Logic Apps, and Microsoft Teams for workflow automation, all of which are Microsoft-centric tools. There are no examples or mentions of Linux-native tools, CLI-based automation, or cross-platform notification systems (e.g., Slack, email, or open-source alternatives). The workflow is tightly coupled to the Microsoft ecosystem, with no guidance for users who may prefer or require Linux-based or open-source solutions.
Recommendations
  • Provide alternative examples using Azure CLI or REST API calls that can be executed from any platform, including Linux.
  • Include guidance or examples for integrating with non-Microsoft notification systems (e.g., Slack, email, or webhooks) to demonstrate cross-platform compatibility.
  • Mention and link to automation options that are platform-agnostic, such as using GitHub Actions, Azure Functions (with code samples in bash or Python), or other open-source workflow engines.
  • Explicitly state that the workflow can be adapted for non-Windows environments and provide at least one example or reference for Linux users.
  • Where possible, avoid assuming the use of the Azure Portal GUI and provide equivalent command-line or API-based instructions.
GitHub Create Pull Request
API Center https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/set-up-api-center-vs-code-extension.md ...cles/api-center/set-up-api-center-vs-code-extension.md
Medium Priority View Details →
Scanned: 2025-09-14 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes the use of Visual Studio Code and its Azure API Center extension, which are cross-platform, but it does not mention or provide any Linux-specific guidance, troubleshooting, or alternative workflows. There is an implicit Windows-first bias as there are no references to Linux environments, terminal commands, or platform-specific considerations. All instructions and screenshots are generic or implicitly Windows-oriented.
Recommendations
  • Explicitly state that Visual Studio Code and the Azure API Center extension are available on Windows, macOS, and Linux.
  • Include notes or sections addressing any Linux-specific installation steps, such as using package managers (apt, yum, snap) for VS Code.
  • Provide screenshots or examples from Linux desktop environments to demonstrate parity.
  • Mention any known issues or differences in behavior on Linux, if applicable.
  • Add troubleshooting tips for Linux users, such as permissions or dependency issues.
GitHub Create Pull Request
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 →
Scanned: 2025-09-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but consistently lists Bash first and PowerShell second. There are no exclusive Windows-only tools or steps, but the presence of PowerShell examples throughout, and the explicit mention that Azure CLI commands can run in PowerShell or Bash, introduces a mild Windows bias. All tooling and instructions are otherwise cross-platform (Azure CLI, azd, Visual Studio Code), and Linux users are not excluded, but the parity in example prominence could be improved.
Recommendations
  • Alternate the order of Bash and PowerShell examples throughout the documentation, or present both equally (e.g., side-by-side tabs).
  • Explicitly state that all tools and steps are fully supported on Linux, macOS, and Windows.
  • Where possible, provide a single cross-platform command (e.g., using environment-agnostic syntax) before splitting into shell-specific variants.
  • Add a brief section or callout confirming that Visual Studio Code and Azure CLI are available and supported on Linux, macOS, and Windows.
  • If referencing Visual Studio Code, clarify that it is cross-platform and provide links to Linux/macOS installation guides as well.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently presents Bash first and then PowerShell. There is a note clarifying that examples can run in either shell and that separate examples are provided where variable syntax differs. No Windows-specific tools or patterns are exclusively mentioned, and there are no missing Linux examples. However, the explicit labeling of 'Formatted for PowerShell' and the inclusion of PowerShell-specific syntax throughout the page indicate a strong focus on Windows parity, possibly even a slight Windows-first bias due to the explicit PowerShell formatting, though Bash is always listed first.
Recommendations
  • Continue to provide both Bash and PowerShell examples, but clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right syntax.
  • Consider adding a short section or table at the top summarizing which shell to use on which platform (e.g., Bash for Linux/macOS, PowerShell for Windows), to make it clearer for cross-platform users.
  • If possible, provide a toggle or tabbed interface in the documentation to let users select their preferred shell (Bash or PowerShell), reducing visual clutter and making parity more obvious.
  • Ensure that any references to file paths, environment variables, or shell-specific behaviors are clearly explained for both platforms.
  • Maintain the order of examples (Bash first, then PowerShell) or alternate the order in different sections to avoid any perception of platform preference.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Visual Studio Code and its Azure API Center extension as prerequisites, which are cross-platform tools. However, there is a subtle bias in that only Visual Studio Code (and its extension) is mentioned as the tool for interacting with Azure API Center, with no mention of alternative editors or CLI tools commonly used on Linux. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility or provide Linux-centric guidance.
Recommendations
  • Explicitly state that Visual Studio Code and the Azure API Center extension are available on Windows, Linux, and macOS.
  • Mention and provide links to alternative tools or CLI options (if available) for managing API centers, especially those commonly used on Linux.
  • Include a note or section on installing and using the Azure API Center extension on Linux distributions.
  • If Visual Studio Code is the only supported tool, clarify its cross-platform nature to avoid the impression of Windows preference.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
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 are always presented immediately after the Bash examples. There is a slight bias toward Windows/PowerShell by explicitly formatting and labeling PowerShell commands, while not providing equivalent detail for other shells (e.g., zsh, fish) or Linux-specific environments. The documentation does not mention Linux or macOS explicitly, nor does it provide troubleshooting or environment-specific notes for non-Windows users.
Recommendations
  • Clearly label Bash examples as 'Linux/macOS (Bash)' and PowerShell examples as 'Windows (PowerShell)' to make platform targeting explicit.
  • Consider providing a short note at the beginning of the CLI section explaining that Bash examples are for Linux/macOS and PowerShell for Windows, and that Azure CLI works cross-platform.
  • If possible, provide parity in detail for both environments, such as mentioning common shell differences or potential issues on Linux/macOS.
  • Add troubleshooting tips or links for users running Azure CLI on Linux/macOS, especially if there are known differences.
  • Consider including a table or tabbed interface for 'Linux/macOS (Bash)', 'Windows (PowerShell)', and possibly 'Windows (CMD)' if relevant, to make it clear which commands apply to which environments.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
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 explicitly labeled and formatted, potentially giving them prominence. Additionally, PowerShell examples are included immediately after Bash, which can be interpreted as a subtle 'windows_first' bias. However, Linux (Bash) examples are present and correct, and no Windows-only tools are used.
Recommendations
  • Clearly label both Bash and PowerShell examples with headings such as 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make platform targeting explicit.
  • Present Bash and PowerShell examples in parallel tabs or side-by-side, rather than sequentially, to avoid implying priority.
  • Ensure that introductory text does not imply that PowerShell is the default or preferred shell.
  • Consider including a brief note about cross-platform compatibility of Azure CLI and how users can select the appropriate shell for their OS.
GitHub Create Pull Request
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 →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
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 PowerShell is a Windows-centric tool. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there any explicit Linux or cross-platform command-line considerations. The prerequisites section references Azure PowerShell requirements, which may reinforce a Windows-oriented workflow.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend it as the default for cross-platform users.
  • Add Bash-specific instructions or notes for Linux/macOS users, such as how to install Azure CLI on Linux.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell examples are to be retained, and provide installation guidance.
  • Consider listing Azure CLI (Bash) examples before PowerShell to reduce perceived Windows-first bias.
  • Add a note or section on running these commands in the Azure Cloud Shell, which is cross-platform and browser-based.
GitHub Create Pull Request
API Center https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-center/includes/store-secret-key-vault.md ...articles/api-center/includes/store-secret-key-vault.md
Medium Priority View Details →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions using the Azure portal GUI, which is a web-based interface commonly associated with Windows-centric workflows. There are no command-line examples (such as Azure CLI or PowerShell), and no mention of Linux-native tools or workflows. This can be seen as a subtle Windows bias, as Linux users often prefer or require CLI-based instructions.
Recommendations
  • Add equivalent Azure CLI examples for enabling managed identities and assigning roles, as the CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic, but provide alternative instructions for users who prefer command-line tools.
  • Where possible, include both GUI and CLI instructions side by side, ensuring parity for Linux and Windows users.
  • Reference documentation for both PowerShell and Azure CLI where relevant, making it clear that both are supported.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-08-14 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is given equal prominence to CLI, and there is no explicit mention of Linux or Bash-specific considerations. The structure and language (e.g., 'your local computer', use of PowerShell) may implicitly favor Windows users, as PowerShell is primarily a Windows tool (though available on Linux). There are no Linux- or Bash-specific examples or troubleshooting notes.
Recommendations
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux) and can be run in Bash or other shells.
  • Add a Bash-specific example or clarify that the CLI example is intended for Bash/Unix shells.
  • Include a note that PowerShell is available on Linux, but Bash is the default shell on most Linux distributions.
  • If relevant, provide troubleshooting tips or environment setup notes for Linux users.
  • Consider listing the CLI (Bash) example first, as it is more universally applicable across platforms.
GitHub Create Pull Request
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 →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell syntax is consistently presented immediately after Bash, and sometimes with explicit 'PowerShell syntax' labels. There are no Windows-only tools or exclusive PowerShell-only steps, but the repeated inclusion and labeling of PowerShell examples may give the impression of Windows being a primary or preferred platform. All tooling (Azure CLI, azd, Visual Studio Code) is cross-platform, but the documentation does not explicitly highlight Linux or macOS parity, nor does it provide Linux-specific troubleshooting or environment notes.
Recommendations
  • Alternate the order of Bash and PowerShell examples to avoid always presenting Bash first, or clarify that both are equally supported.
  • Explicitly mention that all tools and steps are cross-platform, and provide links or notes for Linux/macOS users where relevant (e.g., VS Code installation, azd installation).
  • Add a short section or note confirming that the workflow is fully supported on Linux and macOS, including any known differences or tips for those environments.
  • Where possible, include screenshots or terminal output from Linux/macOS environments, not just Windows/PowerShell.
  • If there are any platform-specific caveats (e.g., file path syntax, permissions), call them out directly.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:25
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally 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' labels. There are no Linux-specific tools or workflows mentioned, but the documentation does state that Azure CLI commands can be run in either PowerShell or Bash. No examples are exclusive to Windows or PowerShell, but the repeated explicit inclusion of PowerShell syntax and the order of presentation (Bash first, then PowerShell) may suggest a slight Windows-first or PowerShell-heavy bias.
Recommendations
  • Ensure that all command examples are provided for both Bash and PowerShell, as currently done.
  • Consider alternating the order of Bash and PowerShell examples, or presenting them in parallel tabs, to avoid implying a default preference.
  • Explicitly mention Linux and macOS compatibility in the prerequisites and command sections, not just Bash.
  • Include screenshots or references to Linux/macOS environments where appropriate, not only Azure Portal (which is OS-agnostic but often associated with Windows workflows).
  • If any troubleshooting or environment setup steps differ for Linux/macOS, provide those details alongside Windows instructions.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-13 21:25
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence to Azure CLI, and there is no mention of Linux-specific considerations or examples. The PowerShell example is presented alongside the CLI example, but there are no explicit Linux shell (bash) examples or notes about cross-platform usage, which may implicitly favor Windows users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider providing bash-specific examples or notes where appropriate.
  • Clarify that PowerShell Core is cross-platform, but traditional Azure PowerShell is most commonly used on Windows.
  • Add a section or note for Linux/macOS users, highlighting any differences or confirming parity.
  • Ensure that CLI examples are presented first, as they are more universally applicable across platforms.
  • Avoid implying that PowerShell is the default or primary method unless it is truly cross-platform.
GitHub Create Pull Request
← Previous Page 3 of 8 Next →