Stream Analytics

60
Total Pages
39
Linux-Friendly Pages
21
Pages with Bias
35.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

98 issues found
Showing 26-50 of 98 flagged pages
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-deploy-with-bicep.md ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt) for all command-line examples, including npm and Azure CLI commands. There are no Bash/Linux/macOS equivalents, and Windows path separators are used throughout. This may confuse or exclude Linux/macOS users.
Recommendations
  • Provide Bash/Linux/macOS command examples alongside PowerShell/Windows examples, especially for npm and Azure CLI commands.
  • Use platform-agnostic path separators in documentation (e.g., ./ instead of .\), or show both variants.
  • Explicitly mention that the commands work cross-platform and clarify any differences in syntax or prerequisites for Linux/macOS users.
  • Where possible, use neutral shell prompts (e.g., $) or clarify which shell is being used in each example.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cosmos-db-managed-identity.md ...rticles/stream-analytics/cosmos-db-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, referencing Windows-centric tools, and omitting equivalent instructions for Linux environments (such as Azure CLI or REST API). The instructions and examples assume the use of PowerShell, which is most commonly used on Windows, and do not mention or prioritize cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI commands for role assignment, which are natively supported on Linux and macOS.
  • Include REST API examples for role assignment to support automation and cross-platform usage.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify platform requirements for each example.
  • Ensure that examples and instructions are presented in a platform-neutral way, or offer both Windows and Linux/macOS alternatives side-by-side.
  • Add a section or note addressing cross-platform usage and how users on non-Windows systems can perform the same tasks.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-cosmos-db-output.md ...in/articles/stream-analytics/azure-cosmos-db-output.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools and workflows (PowerShell, Visual Studio) before Linux-friendly alternatives. The 'Next steps' section prioritizes Azure PowerShell and Visual Studio, both primarily used on Windows, and does not provide explicit Linux examples or mention Linux-specific tools. While the Azure CLI and Visual Studio Code are cross-platform, the ordering and inclusion of Windows-only tools suggest a preference for Windows environments.
Recommendations
  • Reorder the 'Next steps' section to list cross-platform tools (Azure CLI, Visual Studio Code) before Windows-only tools (PowerShell, Visual Studio).
  • Explicitly mention Linux compatibility for Azure CLI and Visual Studio Code steps.
  • Add Linux-specific examples or instructions where relevant, such as running Azure CLI commands on Linux.
  • Clarify which steps/tools are Windows-only and provide Linux alternatives where possible.
  • Consider including screenshots or walkthroughs from Linux environments to improve parity.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-input.md ...ain/articles/stream-analytics/confluent-kafka-input.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing all Azure CLI command examples in PowerShell syntax, referencing Windows file paths (e.g., C:\Users\Downloads\...), and instructing users to 'right-click and copy the path,' which is a Windows-specific action. There are no examples or instructions for Linux or macOS users, such as using Bash, typical Linux file paths, or alternative methods for copying file paths. The guidance for installing and configuring Azure CLI is also Windows-centric, with no mention of Linux or macOS installation steps.
Recommendations
  • Provide Azure CLI command examples in Bash syntax alongside PowerShell, using Linux/macOS file paths (e.g., /home/user/downloads/isrgrootx1.pem).
  • Include instructions for installing and configuring Azure CLI on Linux and macOS, with relevant links.
  • Mention alternative methods for copying file paths on Linux/macOS (e.g., using the terminal or file manager).
  • Add notes or callouts to clarify that the steps apply to all platforms, and highlight any platform-specific differences.
  • Ensure screenshots and UI instructions are not exclusively Windows-focused, or provide equivalents for other operating systems where relevant.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-functions-output.md ...in/articles/stream-analytics/azure-functions-output.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where Windows-centric tools (Azure PowerShell, Visual Studio) are listed before Linux-friendly alternatives (Azure CLI, Visual Studio Code). The inclusion of PowerShell and Visual Studio as quickstart options, both of which are traditionally Windows-focused, further emphasizes this bias. There are no explicit Linux examples or mentions of Linux-specific tools or patterns, and no parity guidance for Linux users.
Recommendations
  • Reorder the 'Next steps' section to list cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific ones (PowerShell, Visual Studio).
  • Explicitly mention Linux compatibility and provide Linux-specific examples or notes where relevant.
  • Include instructions or quickstarts for Linux users, such as using Bash scripts or Linux-native tools.
  • Clarify which steps or tools are cross-platform and which are Windows-only, to help users on non-Windows systems.
  • Consider adding a table or section comparing tool availability and usage on Windows vs. Linux.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md .../blob/main/articles/stream-analytics/cicd-autoscale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell commands and examples, referencing Windows-centric tools (such as PowerShell and Az modules), and omitting equivalent instructions for Linux or macOS environments. There are no bash, shell, or cross-platform CLI examples, nor any mention of Linux-specific considerations. The documentation assumes the use of PowerShell and Windows tooling throughout, even though the Stream Analytics CI/CD tool is installed via npm and could be used on any OS.
Recommendations
  • Provide equivalent bash or shell command examples for Linux/macOS users, especially for npm installation and Azure CLI operations.
  • Mention cross-platform compatibility of the Stream Analytics CI/CD tool and clarify that it can be used on Linux and macOS.
  • Include Azure CLI examples for authentication and deployment, as Azure CLI is available on all platforms.
  • Add notes or sections highlighting any OS-specific requirements or differences, such as file path formats or environment setup.
  • Ensure screenshots and instructions do not assume a Windows file system or shell unless necessary.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-tools.md ...docs/blob/main/articles/stream-analytics/cicd-tools.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell syntax, and Windows-specific tools (e.g., Connect-AzAccount, New-AzResourceGroupDeployment) are featured exclusively. There are no Linux shell (bash/sh) examples, nor are cross-platform alternatives (such as Azure CLI) mentioned. The note about JavaScript UDFs only working on Windows further highlights platform limitations. The documentation implicitly assumes a Windows environment throughout, which may hinder Linux users.
Recommendations
  • Provide equivalent bash/sh examples for all commands, especially npm install and azure-streamanalytics-cicd usage.
  • Include Azure CLI alternatives for deployment steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clearly indicate platform-specific limitations (e.g., JavaScript UDFs) and suggest alternatives or workarounds for Linux users.
  • Avoid using backslashes in file paths; use forward slashes or show both formats.
  • Add a section or callouts for Linux/macOS setup, including prerequisites and environment differences.
  • Review all examples to ensure they are runnable on Linux and macOS, or explicitly mark Windows-only steps.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/geo-redundancy.md .../blob/main/articles/stream-analytics/geo-redundancy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its 'Next steps' section, which exclusively recommends PowerShell for monitoring and managing Azure Stream Analytics jobs. PowerShell is a Windows-centric tool, and there is no mention of Linux alternatives or cross-platform command-line tools. Additionally, the documentation does not provide examples or guidance for Linux users, such as using Azure CLI or Bash scripts, which are common in Linux environments.
Recommendations
  • Include equivalent instructions and examples for managing Stream Analytics jobs using Azure CLI, which is cross-platform and widely used on Linux.
  • Provide links to documentation or tutorials for Linux users, such as Bash scripting or using REST APIs for job management.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify platform compatibility where relevant.
  • Ensure that future documentation sections present both Windows and Linux options side-by-side, or in a platform-neutral manner.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md ...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section about uploading certificates to Azure Key Vault. All CLI examples are given in PowerShell syntax, with explicit references to Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem) and instructions such as 'Make sure you have Azure CLI configured locally with PowerShell.' There are no equivalent Linux/macOS shell examples, nor is there mention of using Bash or typical Linux file paths. The guidance assumes a Windows environment for local setup and usage.
Recommendations
  • Provide parallel examples using Bash shell syntax for Linux/macOS users, including typical Linux file paths (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI can be used on Linux/macOS and provide instructions for those platforms.
  • Avoid language that assumes PowerShell is the default shell; instead, mention both PowerShell and Bash as options.
  • Add notes or links to Azure CLI installation and usage guides for Linux/macOS.
  • Where screenshots or instructions reference file navigation, include guidance for Linux/macOS equivalents.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/includes/event-generator-app.md ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for running the TelcoGenerator application using Windows-specific tools (e.g., .exe file, command prompt), without mentioning or providing alternatives for Linux or macOS users. The command-line example uses Windows syntax, and there is no guidance for running the application on non-Windows platforms.
Recommendations
  • Provide instructions for running the TelcoGenerator application on Linux and macOS, including any prerequisites (e.g., Mono for .NET executables, or alternative cross-platform versions).
  • Include Linux/macOS command-line examples (e.g., using ./telcodatagen.exe with Mono, or a native binary if available).
  • Clarify whether the TelcoGenerator application is Windows-only, and if so, suggest cross-platform alternatives or containerized solutions.
  • Add notes about editing configuration files and running commands using Linux/macOS tools (e.g., nano, vi, Terminal) alongside Windows tools.
  • Ensure screenshots and UI instructions are not exclusively tailored to Windows environments if the Azure portal experience differs on other platforms.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-tools.md ...docs/blob/main/articles/stream-analytics/cicd-tools.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all code examples use PowerShell syntax, Windows-specific tools (such as Connect-AzAccount and New-AzResourceGroupDeployment) are used exclusively, and there are no Bash or Linux shell equivalents provided. The only mention of platform differences is a note that JavaScript UDFs only work on Windows, but no guidance or alternatives are offered for Linux users. This could make it difficult for Linux or macOS users to follow the instructions or adapt them to their environments.
Recommendations
  • Provide all command-line examples in both PowerShell and Bash (or generic shell) syntax, especially for npm commands and directory navigation.
  • Include Azure CLI equivalents for deployment steps (e.g., az login, az deployment group create) alongside PowerShell cmdlets.
  • Explicitly state platform requirements or limitations at the beginning of the article, and offer alternatives or workarounds for non-Windows users where possible.
  • Add notes or sections for Linux/macOS users, including any differences in file paths, environment setup, or tool installation.
  • Where features are Windows-only (e.g., JavaScript UDFs), suggest alternative approaches or clarify the impact for Linux users.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-deploy-with-bicep.md ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt, and commands) for all CLI examples, including npm installation and Azure CLI deployment. There are no Linux/macOS shell equivalents, and Windows path separators are used throughout, which may confuse or exclude Linux/macOS users.
Recommendations
  • Provide equivalent Bash examples alongside PowerShell, using appropriate path separators (e.g., ./ instead of .\).
  • Explicitly mention that the commands work cross-platform and clarify any OS-specific differences.
  • Use platform-agnostic syntax in documentation when possible, or provide tabs/switches for Windows and Linux/macOS instructions.
  • Add a note about prerequisites or shell environments for each platform.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-data-explorer-managed-identity.md ...ream-analytics/azure-data-explorer-managed-identity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes how to configure managed identities and permissions using the Azure portal, which is a graphical tool most commonly used on Windows. There are no examples or instructions for performing these tasks using cross-platform command-line tools such as Azure CLI, PowerShell, or REST APIs. No Linux-specific or CLI-based workflows are mentioned, and the documentation assumes the user is interacting with the Azure portal UI, which may not be the preferred or available method for Linux users or those automating deployments.
Recommendations
  • Add equivalent instructions for configuring managed identities and role assignments using the Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are given equal or higher prominence.
  • Provide REST API examples or references for users who need to automate these tasks in a platform-agnostic way.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using the CLI or API, not just the Azure portal.
  • Where screenshots are used, consider including CLI output or code snippets as alternatives.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md .../blob/main/articles/stream-analytics/cicd-autoscale.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows/Powershell bias. All command-line examples, including installation, project build, autoscale configuration, Azure login, and deployment, are shown exclusively using Powershell syntax and cmdlets (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment). There are no Bash, Linux shell, or cross-platform CLI equivalents provided, despite the fact that the Stream Analytics CI/CD tool is installed via npm and could be used on Linux/macOS. The documentation assumes a Windows environment for Azure authentication and deployment, omitting az CLI or Bash alternatives.
Recommendations
  • Provide equivalent Bash/Linux/macOS shell commands for all steps, especially for npm installation, project build, and running the CI/CD tool.
  • Include Azure CLI (az) commands for authentication and deployment, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly state that the CI/CD tool and deployment steps can be performed on Linux/macOS, and highlight any platform-specific considerations.
  • Reorder or parallelize examples so that Linux/Bash and Windows/Powershell instructions are given equal prominence.
  • Add a section or callout for Linux/macOS users, clarifying any differences in file paths, environment setup, or command syntax.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-github-actions.md .../main/articles/stream-analytics/cicd-github-actions.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell for command-line instructions, linking only to Windows-specific Azure CLI installation guides, and omitting any mention or examples for Linux or macOS environments. All screenshots and terminal instructions assume a Windows/PowerShell context, with no alternatives or parity for other platforms.
Recommendations
  • Provide equivalent command-line instructions for Linux and macOS users, using Bash or sh syntax where appropriate.
  • Include links to Azure CLI installation guides for Linux and macOS alongside the Windows link.
  • Add screenshots or notes indicating how to open the terminal and run commands in VS Code on Linux/macOS.
  • Use platform-agnostic language (e.g., 'open a terminal' instead of 'open PowerShell') and clarify that the Azure CLI works across operating systems.
  • Where referencing PowerShell, also show the Bash equivalent, especially for commands that may differ in syntax or environment.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram-vs-code.md ...m-analytics/debug-locally-using-job-diagram-vs-code.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform as it focuses on Visual Studio Code, which is available on both Windows and Linux. However, there is a notable Windows bias in the 'Limitations' section, where it states that running jobs locally with JavaScript functions is only supported on Windows. No Linux-specific instructions, troubleshooting, or parity notes are provided elsewhere. There are no Linux or macOS examples, nor are there alternative workflows or caveats for non-Windows users.
Recommendations
  • Explicitly state which features are supported on Linux and macOS, not just Windows.
  • Provide alternative instructions or workarounds for Linux/macOS users where features are Windows-only.
  • Add Linux/macOS-specific troubleshooting tips or known issues if certain features are unavailable.
  • Include parity tables or notes to clarify which features are cross-platform and which are not.
  • If possible, prioritize cross-platform support for local JavaScript function execution or provide a roadmap for Linux/macOS support.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cosmos-db-managed-identity.md ...rticles/stream-analytics/cosmos-db-managed-identity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, with no equivalent Azure CLI or REST API examples. It explicitly states that role assignment must be done via Azure PowerShell, which is primarily a Windows-centric tool, and does not mention or provide guidance for Linux or cross-platform users. There are no Bash or Linux shell examples, and the documentation assumes access to PowerShell.
Recommendations
  • Provide equivalent Azure CLI (az) commands for role assignment, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API or ARM template examples for users who may want to automate the process in a platform-agnostic way.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, if PowerShell is truly required, and provide installation instructions or links.
  • Add a note or section addressing Linux/macOS users, ensuring parity in instructions and tooling.
  • Where possible, avoid language that implies PowerShell is the only supported method, unless it is a technical limitation, and clarify if so.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram.md ...es/stream-analytics/debug-locally-using-job-diagram.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on using Visual Studio for local debugging of Azure Stream Analytics queries, which is a Windows-centric tool. There are no examples or instructions for Linux users, nor are any cross-platform alternatives (such as Visual Studio Code or CLI-based workflows) mentioned. All steps, screenshots, and references assume the use of Visual Studio on Windows, and there is no guidance for achieving similar functionality on Linux or macOS.
Recommendations
  • Provide equivalent instructions for Linux users, such as using Visual Studio Code with relevant extensions or Azure CLI for local testing and debugging.
  • Explicitly mention platform requirements and, if the feature is Windows-only, suggest alternative workflows for non-Windows users.
  • Include cross-platform examples and screenshots, or clarify which steps are not available on Linux/macOS.
  • Reference any available tools or SDKs that support local debugging on Linux, or provide a roadmap for such support if it does not exist.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/geo-redundancy.md .../blob/main/articles/stream-analytics/geo-redundancy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell specifically in the 'Next steps' section, suggesting it as the primary tool for monitoring and managing Azure Stream Analytics jobs. There are no examples or mentions of Linux-native tools, Bash, or cross-platform alternatives, which may make Linux users feel unsupported.
Recommendations
  • Include equivalent Bash or Azure CLI examples and links alongside PowerShell references.
  • Explicitly mention that Azure Stream Analytics management can be performed from Linux, macOS, and Windows, and provide cross-platform instructions.
  • Balance the 'Next steps' section by linking to documentation for both PowerShell and Azure CLI/Bash management.
  • Where possible, use neutral language (e.g., 'use your preferred shell or scripting environment') and provide code snippets for both Windows and Linux users.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md ...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell examples for Azure CLI commands, referencing Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem), and instructing users to configure Azure CLI locally with PowerShell. There are no equivalent Linux/macOS command-line examples, nor are Linux file path conventions or shell environments mentioned.
Recommendations
  • Provide Azure CLI command examples using Bash (or generic shell) syntax alongside PowerShell, including Linux/macOS file path examples (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI can be used on Windows, Linux, and macOS, and provide links or instructions for installing and using Azure CLI on non-Windows platforms.
  • Avoid language that assumes PowerShell as the default shell; instead, offer both PowerShell and Bash command blocks where appropriate.
  • Include notes or callouts for any platform-specific considerations, such as file path formats or shell differences.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/feature-comparison.md ...b/main/articles/stream-analytics/feature-comparison.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (a Windows-only tool) is mentioned in the commented-out sections and in the 'Next steps' links, sometimes before Visual Studio Code (which is cross-platform). The feature table for JavaScript UDF and UDA explicitly states 'Windows only' for Visual Studio Code, without further explanation or Linux alternatives. There are no Linux-specific examples, troubleshooting, or parity notes, and the documentation does not highlight or address limitations/workarounds for non-Windows users.
Recommendations
  • Ensure all feature tables and descriptions clarify platform limitations, and provide workarounds or alternatives for Linux/macOS users where possible.
  • In 'Next steps' and throughout the documentation, list cross-platform tools (like Visual Studio Code) before Windows-only tools (like Visual Studio) to avoid Windows-first bias.
  • Where features are Windows-only (e.g., JavaScript UDF/UDA), explicitly state the limitation and, if possible, provide a roadmap or alternatives for Linux/macOS users.
  • Add Linux/macOS-specific examples, troubleshooting tips, or notes to improve parity and inclusivity.
  • Consider a dedicated section summarizing platform support and limitations for all major features.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-cosmos-db-output.md ...in/articles/stream-analytics/azure-cosmos-db-output.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows a mild Windows bias in the 'Next steps' section, where Windows-centric tools and workflows (PowerShell, Visual Studio) are listed before cross-platform or Linux-friendly options (Azure CLI, Visual Studio Code). There is a dedicated PowerShell quickstart, and Visual Studio (Windows-only) is mentioned before Visual Studio Code. No Linux-specific examples or tools are highlighted, and there is no mention of Linux shell or scripting environments.
Recommendations
  • List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio) in the 'Next steps' section.
  • Explicitly mention Linux and macOS compatibility where applicable, especially for Azure CLI and Visual Studio Code.
  • Provide Linux shell (bash) examples or references alongside PowerShell examples.
  • Add a note clarifying which tools are cross-platform and which are Windows-only.
  • Consider including a Linux-specific quickstart or troubleshooting guide.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-functions-output.md ...in/articles/stream-analytics/azure-functions-output.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits subtle Windows bias, particularly in the 'Next steps' section, where Windows-centric tools (PowerShell, Visual Studio) are listed before or alongside cross-platform alternatives. There is a dedicated quickstart for Azure PowerShell and Visual Studio (both Windows-focused), while Linux-native or cross-platform command-line examples (like Bash or Linux shell) are not specifically highlighted. No explicit Linux examples or tools are mentioned, and the ordering of next steps may suggest a preference for Windows environments.
Recommendations
  • Add explicit Linux/bash shell examples or quickstarts, especially for common tasks (e.g., using Azure CLI from Bash).
  • Ensure that cross-platform tools (Azure CLI, Visual Studio Code) are listed before or at least alongside Windows-specific tools in 'Next steps'.
  • Include notes or sections clarifying that all features and instructions apply equally to Linux and macOS environments where applicable.
  • Where PowerShell is mentioned, also provide equivalent Bash or shell commands for Linux users.
  • Consider adding a table or section comparing tool availability and usage across Windows, Linux, and macOS.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-output.md ...in/articles/stream-analytics/confluent-kafka-output.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing Windows file paths (e.g., C:\Users\Downloads), and instructing users to use PowerShell for Azure CLI operations. There are no Linux/macOS equivalents or notes, and instructions such as 'right-click and copy the path' are Windows-specific. No mention is made of Linux or cross-platform considerations, despite Azure CLI being cross-platform.
Recommendations
  • Provide command-line examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, especially for Azure CLI commands.
  • Use generic or platform-neutral file paths in examples (e.g., /home/user/Downloads/isrgrootx1.pem for Linux/macOS).
  • Add notes or sections explaining how to perform steps (such as copying file paths) on Linux/macOS.
  • Explicitly state that Azure CLI can be used on Windows, Linux, and macOS, and link to relevant installation guides for each platform.
  • Where screenshots or UI steps are shown, clarify if there are any platform-specific differences or confirm that the steps are the same across platforms.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-input.md ...ain/articles/stream-analytics/confluent-kafka-input.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section on uploading certificates to Azure Key Vault. All command-line examples are shown using PowerShell syntax and Windows-style file paths (e.g., C:\Users\Downloads\...), with no equivalent Linux/macOS examples or mention of cross-platform compatibility. The guidance assumes the user is running Azure CLI from PowerShell, and instructions such as 'right-click and copy the path' are Windows-centric. There is no mention of how to perform these steps on Linux or macOS, nor are there examples using Unix-style paths or shells.
Recommendations
  • Provide Azure CLI command examples using both PowerShell (Windows) and Bash (Linux/macOS) syntax.
  • Include file path examples for both Windows (C:\...) and Linux/macOS (/home/user/...).
  • Clarify that Azure CLI is cross-platform and can be used from any shell, not just PowerShell.
  • Replace or supplement 'right-click and copy the path' with platform-agnostic instructions.
  • Explicitly mention any platform-specific requirements or differences, if any, for Linux/macOS users.
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →