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 76-98 of 98 flagged pages
Stream Analytics Automate builds, tests, and deployments using CI/CD tools ...docs/blob/main/articles/stream-analytics/cicd-tools.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page consistently uses PowerShell syntax for all CLI examples, including npm installation, project build, test, and deployment steps. Windows/PowerShell commands are shown exclusively, with no Bash, sh, or Linux/macOS shell equivalents. Azure PowerShell tools are referenced for deployment, and there is no mention of Azure CLI or cross-platform alternatives. The only explicit OS note is that JavaScript UDFs work only on Windows, but otherwise, Linux/macOS users are left to infer compatibility and command translation.
Recommendations
  • Provide Bash/sh equivalents for all CLI commands, especially for npm installation and azure-streamanalytics-cicd usage.
  • Include Azure CLI deployment instructions alongside Azure PowerShell, or clarify cross-platform support for deployment.
  • Explicitly state OS compatibility for the npm package and commands (e.g., supported on Windows, Linux, macOS).
  • When showing command examples, alternate or parallel Windows and Linux/macOS syntax, or use generic shell syntax where possible.
  • Add notes or troubleshooting for Linux/macOS users, especially regarding file paths and environment setup.
GitHub Create Pull Request
Stream Analytics Configure autoscale settings for a Stream Analytics job by using the CI/CD tool .../blob/main/articles/stream-analytics/cicd-autoscale.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell commands and examples for installing, configuring, and deploying the Stream Analytics CI/CD tool. There are no Bash, shell, or Linux/macOS-specific instructions, and all deployment steps use PowerShell cmdlets (Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment), which are native to Windows and require additional setup or alternatives on Linux/macOS. The documentation also refers to using PowerShell in both scenarios and does not mention cross-platform CLI options (e.g., Azure CLI) or provide Linux/macOS terminal equivalents.
Recommendations
  • Include equivalent Bash/shell commands for npm installation and running the CI/CD tool.
  • Provide Azure CLI examples for authentication and deployment steps, which are cross-platform and work natively on Linux/macOS.
  • Explicitly mention platform compatibility for the Stream Analytics CI/CD tool and deployment commands.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional requirements.
  • Present examples for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI), or use Azure CLI as the default for parity.
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into confluent cloud kafka ...in/articles/stream-analytics/confluent-kafka-output.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section on uploading certificates to Azure Key Vault. All Azure CLI command examples are shown using PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\isrgrootx1.pem), with instructions referencing right-clicking to copy file paths—a Windows-specific action. There are no Linux/macOS shell examples, nor any mention of how to perform equivalent steps on those platforms. This may cause confusion or friction for users on Linux or macOS.
Recommendations
  • Provide Azure CLI command examples using bash/zsh syntax and Linux/macOS file paths (e.g., /home/user/isrgrootx1.pem).
  • Add instructions for copying file paths on Linux/macOS (e.g., using the terminal or file manager).
  • Explicitly state that Azure CLI works cross-platform and link to platform-specific installation guides.
  • Include a note or section clarifying any differences in command usage or file path conventions between Windows and Linux/macOS.
GitHub Create Pull Request
Stream Analytics Achieve geo-redundancy for Azure Stream Analytics jobs .../blob/main/articles/stream-analytics/geo-redundancy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references PowerShell as the primary tool for monitoring and managing Azure Stream Analytics jobs, both in the 'Next steps' section and by linking to a PowerShell-focused guide. There is no mention of Linux/macOS alternatives such as Azure CLI or Bash scripting, nor are cross-platform options presented alongside PowerShell.
Recommendations
  • Include links or references to Azure CLI documentation for managing Stream Analytics jobs, which is cross-platform.
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide equivalent Bash/Azure CLI examples.
  • Add a note or section highlighting cross-platform management options for Azure Stream Analytics jobs.
  • Reorder or balance 'Next steps' to present both Windows and Linux/macOS tools equally.
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into Kafka ...cs/blob/main/articles/stream-analytics/kafka-output.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its instructions for uploading certificates to Azure Key Vault. All CLI examples are shown in PowerShell syntax, with explicit references to Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem) and instructions such as 'right-click and copy the path to the certificate,' which are Windows-centric. There are no equivalent examples or guidance for Linux/macOS users, such as using Bash shell, Linux file paths, or platform-agnostic instructions for copying file paths.
Recommendations
  • Provide CLI examples using Bash syntax alongside PowerShell, including Linux/macOS file path formats (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI works cross-platform and give instructions for installing and using it on Linux/macOS.
  • Replace or supplement 'right-click and copy the path' with platform-neutral instructions (e.g., 'use your file manager or terminal to determine the file path').
  • Explicitly mention that the az keyvault secret set command works on all platforms and show examples for each.
  • Add a note or section for Linux/macOS users, highlighting any differences or considerations.
GitHub Create Pull Request
Stream Analytics Use managed identities to access Azure Cosmos DB from an Azure Stream Analytics job ...rticles/stream-analytics/cosmos-db-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides an Azure PowerShell example for assigning RBAC roles to the managed identity, with no mention of Azure CLI or REST API alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer platform-agnostic tools. The documentation also refers to PowerShell as the only method for a critical step, and does not offer Linux-friendly guidance.
Recommendations
  • Add equivalent Azure CLI and/or REST API examples for assigning Cosmos DB RBAC roles.
  • Explicitly mention that PowerShell is not required and provide links to cross-platform tools.
  • Reorganize instructions to present platform-agnostic methods first, or side-by-side with PowerShell.
  • Clarify any prerequisites for PowerShell, and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Stream Analytics Azure Functions output from Azure Stream Analytics ...in/articles/stream-analytics/azure-functions-output.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Windows-centric tools (Azure PowerShell, Visual Studio) before Linux-friendly alternatives (Azure CLI, Visual Studio Code) in the 'Next steps' section. There is a notable emphasis on Windows tools and patterns, with PowerShell and Visual Studio mentioned explicitly, while Linux-native workflows are less prominent and not described in detail.
Recommendations
  • Ensure Linux-friendly tools (Azure CLI, Visual Studio Code) are listed before or alongside Windows tools in quickstart and next steps sections.
  • Provide explicit examples or guidance for Linux environments, such as bash scripts or Linux-specific setup instructions.
  • Balance references to PowerShell and Visual Studio with equivalent instructions for CLI and VS Code, highlighting cross-platform compatibility.
  • Add a note clarifying that all workflows are supported on both Windows and Linux, where applicable.
GitHub Create Pull Request
Stream Analytics Azure Functions output from Azure Stream Analytics ...in/articles/stream-analytics/azure-functions-output.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Windows-centric tools (PowerShell, Visual Studio) before Linux-friendly alternatives (Azure CLI, Visual Studio Code) in the 'Next steps' section. There is a notable emphasis on Windows tools and workflows, with PowerShell and Visual Studio appearing before CLI and VS Code, which are more cross-platform. No explicit Linux examples or Linux-specific guidance is provided.
Recommendations
  • Reorder the 'Next steps' section to list cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific ones (PowerShell, Visual Studio).
  • Include explicit examples or notes for Linux users, such as shell commands or Linux environment considerations.
  • Add a section or note clarifying that Azure CLI and Visual Studio Code are fully supported on Linux and macOS, and provide links to installation guides for these platforms.
  • Ensure parity in code samples and instructions by providing both PowerShell and Bash/CLI equivalents where relevant.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md ...blob/main/articles/stream-analytics/job-config-json.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on using Visual Studio Code for creating and managing Azure Stream Analytics jobs, without mentioning platform-specific instructions or examples. However, all workflow steps and references are centered around Visual Studio Code, which, while cross-platform, is often associated with Windows in Azure documentation. There are no explicit Linux or macOS instructions, nor are there examples or notes about platform-specific considerations, which may leave Linux users without guidance on potential differences or requirements.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Windows, Linux, and macOS, and that the instructions apply to all platforms.
  • Add notes or sections highlighting any platform-specific steps, such as command-line differences, file path conventions, or prerequisites for Linux/macOS users.
  • Provide example commands or screenshots from both Windows and Linux environments where relevant.
  • Include troubleshooting tips for common issues encountered on Linux (e.g., permissions, dependency installation).
  • Reference alternative editors or tools that Linux users may prefer, if applicable.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/capture-event-hub-data-parquet.md ...les/stream-analytics/capture-event-hub-data-parquet.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure Portal GUI for configuration and verification, with all screenshots and navigation instructions reflecting the Windows-centric Azure Portal interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux tools or workflows. The documentation implicitly assumes a graphical, Windows-like environment and does not address how to perform these tasks from Linux or cross-platform command-line environments.
Recommendations
  • Add equivalent instructions for performing these operations using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include sample commands for creating Event Hubs, Data Lake Storage accounts, and configuring Stream Analytics jobs using CLI or ARM templates.
  • Provide guidance on how to verify output files using Azure CLI (e.g., az storage blob list) or other cross-platform tools, not just through the Azure Portal.
  • Explicitly mention that all steps can be performed from any OS using the Azure Portal, but highlight and document command-line alternatives for automation and Linux users.
  • Where screenshots are used, consider including text-based equivalents or references for users who may not have access to a GUI.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/input-validation.md ...lob/main/articles/stream-analytics/input-validation.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page assumes the use of Visual Studio Code with the ASA Tools extension for development and local runs, but does not mention or provide guidance for Linux users. All setup and workflow instructions are written generically, but the only development environment referenced is VS Code, which is cross-platform, yet the documentation does not explicitly address Linux or macOS users, nor does it provide any Linux-specific instructions or troubleshooting. There are no references to Windows-only tools, but the lack of Linux parity in examples and environment setup is a subtle bias.
Recommendations
  • Explicitly state that Visual Studio Code and the ASA Tools extension are supported on Windows, Linux, and macOS.
  • Provide any Linux-specific setup steps or troubleshooting tips, especially for installing the ASA Tools extension and running local jobs.
  • Include example terminal commands for both Windows (PowerShell/CMD) and Linux/macOS (bash) when referencing file creation, navigation, or running local jobs.
  • Mention any known limitations or differences when running ASA local jobs on Linux/macOS, if applicable.
  • Add a note or section for Linux/macOS users to ensure they have a smooth experience following the tutorial.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides instructions and examples exclusively for Windows environments. It references a Windows executable (.exe), uses Windows command prompt syntax, and does not mention or provide guidance for Linux or cross-platform usage. There are no Linux-specific instructions or alternative commands, and the event generator application appears to be Windows-only.
Recommendations
  • Provide instructions for running the event generator application on Linux, such as offering a cross-platform version (e.g., .NET Core, Java, or Python) or a Docker container.
  • Include Linux shell command examples (e.g., bash) alongside Windows command prompt examples.
  • Clarify OS requirements for the event generator and suggest alternatives or workarounds for Linux/Mac users.
  • If the application is Windows-only, explicitly state this and provide a comparable method for Linux users to generate and send events (e.g., using Azure CLI, Python scripts, or open-source tools).
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-overview.md ...s/blob/main/articles/stream-analytics/cicd-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses on using Visual Studio Code and the ASA Tools extension, which are cross-platform, but does not provide any explicit Linux-specific guidance or examples. There is no mention of Linux command-line environments, shell scripts, or Linux package installation. The documentation also refers to 'exporting to your local machine' and 'command line' in a generic way, but does not clarify or demonstrate parity for Linux users. Additionally, there is a subtle bias toward tools and workflows that are more familiar to Windows users (e.g., Visual Studio Code with extensions, Azure Pipelines), without explicit Linux-first or Linux-equal instructions.
Recommendations
  • Add explicit instructions or examples for Linux users, such as how to install the ASA Tools extension in VS Code on Linux, and how to use the command line for building and deploying on Linux (e.g., bash scripts).
  • Include sample shell commands for Linux environments alongside any generic or Windows-specific instructions.
  • Clarify that all tools and steps are cross-platform, and highlight any differences or prerequisites for Linux users.
  • If screenshots or UI walkthroughs are included elsewhere, ensure they represent both Windows and Linux environments.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/blob-output-managed-identity.md ...icles/stream-analytics/blob-output-managed-identity.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents instructions and examples using the Azure Portal (a web UI) and the Azure CLI, which is cross-platform. However, there is a subtle Windows bias in the ordering and omission of Linux-specific considerations. The Azure Portal is often associated with Windows-centric workflows, and there are no explicit Linux shell or scripting examples, nor any mention of Linux-specific nuances. No PowerShell-specific commands are present, but the documentation does not provide parity for Linux users in terms of shell scripting or automation examples.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands for both Bash (Linux/macOS) and PowerShell (Windows).
  • Where automation is discussed, include example Bash scripts for Linux users, not just Azure CLI one-liners.
  • If referencing the Azure Portal, clarify that it is web-based and platform-independent, to avoid the impression of a Windows-only workflow.
  • If there are any differences in behavior or prerequisites between Windows and Linux environments (such as authentication methods, CLI installation, or file path conventions), document these explicitly.
  • Consider including a short section or note for Linux users, highlighting any relevant tips or troubleshooting steps.
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Azure PowerShell and Visual Studio (Windows-centric tools) before cross-platform or Linux-friendly options in the 'Next steps' section. While the main content is platform-neutral, the ordering and inclusion of Windows-specific tools (PowerShell, Visual Studio) before their Linux equivalents (Azure CLI, Visual Studio Code) suggests a subtle Windows-first bias. No Linux-specific examples or tools are highlighted, and there are no explicit Linux command-line or environment references.
Recommendations
  • Reorder the 'Next steps' links to list cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio).
  • Ensure that code samples and quickstarts are provided for both Windows and Linux environments, or clarify when instructions are cross-platform.
  • Explicitly mention Linux support or provide Linux-specific guidance where relevant.
  • Avoid assuming the use of Windows tools by default; always offer alternatives for Linux users.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md ...blob/main/articles/stream-analytics/job-config-json.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on using Visual Studio Code for creating and managing Azure Stream Analytics jobs, without mentioning or providing examples for Linux-specific workflows, tools, or command-line alternatives. There are no references to Linux environments, and all guidance assumes the use of Visual Studio Code, which is often associated with Windows development, though it is cross-platform.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux and macOS, and provide any Linux-specific setup or troubleshooting tips if applicable.
  • Include examples or references for creating and managing JobConfig.json using command-line tools (such as Azure CLI) that are commonly used in Linux environments.
  • If there are any differences or considerations for Linux users (e.g., file paths, permissions), document them clearly.
  • Add links or sections for alternative editors or workflows that are popular on Linux, if supported.
GitHub Create Pull Request
Stream Analytics https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/input-validation.md ...lob/main/articles/stream-analytics/input-validation.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page assumes and instructs users to use Visual Studio Code with the ASA Tools extension for development and local testing, but does not mention or provide guidance for Linux users. All instructions, examples, and tooling references are centered around Visual Studio Code, with no mention of alternative editors or command-line workflows that may be more common on Linux. There is no explicit mention of Windows-only tools, but the lack of Linux-specific instructions or parity in examples constitutes a subtle Windows bias.
Recommendations
  • Explicitly state that Visual Studio Code and the ASA Tools extension are cross-platform and supported on Linux, and provide installation instructions for Linux users.
  • Include references or examples for command-line workflows (e.g., using the Azure CLI or other scripting tools) that are platform-agnostic.
  • Mention any prerequisites or differences for Linux users, such as file path conventions or dependencies.
  • If any features are Windows-only, clearly indicate this and suggest alternatives for Linux users.
  • Add a section or note acknowledging Linux and macOS users, ensuring parity in guidance and troubleshooting steps.
GitHub Create Pull Request
Stream Analytics Azure Functions output from Azure Stream Analytics ...in/articles/stream-analytics/azure-functions-output.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is generally cross-platform, as Azure Functions and Azure Stream Analytics are cloud services accessible from any OS. However, in the 'Next steps' section, Windows-centric tools (PowerShell, Visual Studio) are listed before Linux-friendly alternatives (CLI, VS Code), and a PowerShell quickstart is included, which may signal a slight Windows-first bias. There are no explicit Linux/macOS examples or references to Linux-specific workflows.
Recommendations
  • Reorder the 'Next steps' links to place platform-neutral or Linux-friendly tools (Azure CLI, VS Code) before Windows-specific ones (PowerShell, Visual Studio).
  • Explicitly mention that Azure Functions and Stream Analytics can be managed from any OS using the Azure CLI and VS Code.
  • Add example workflows or code samples demonstrating usage from Linux/macOS environments, if relevant.
  • Clarify that PowerShell and Visual Studio are optional and not required for Linux/macOS users.
GitHub Create Pull Request
Stream Analytics Azure Cosmos DB output from Azure Stream Analytics ...in/articles/stream-analytics/azure-cosmos-db-output.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists Windows-centric tools and examples (PowerShell, Visual Studio) before Linux-friendly alternatives (CLI, VS Code). The 'Next steps' section places PowerShell and Visual Studio before CLI and VS Code, which may create a perception of Windows-first workflows. No Linux-specific examples or guidance are provided, and the documentation does not mention Linux/macOS compatibility for Stream Analytics or Cosmos DB output.
Recommendations
  • Reorder 'Next steps' to list cross-platform tools (CLI, VS Code) before Windows-only tools (PowerShell, Visual Studio).
  • Explicitly mention Linux/macOS compatibility for Stream Analytics and Cosmos DB output, if supported.
  • Add Linux/macOS-specific examples or notes where relevant, especially for command-line operations.
  • Clarify which steps or tools are Windows-only and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Stream Analytics Achieve geo-redundancy for Azure Stream Analytics jobs .../blob/main/articles/stream-analytics/geo-redundancy.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation itself is platform-neutral, focusing on architectural guidance for geo-redundancy in Azure Stream Analytics. However, the 'Next steps' section highlights PowerShell as the primary tool for monitoring and managing jobs, which may imply a Windows-centric approach and does not mention cross-platform alternatives such as Azure CLI or REST API.
Recommendations
  • Include links or references to Azure CLI and REST API documentation for managing Stream Analytics jobs, ensuring Linux/macOS users have clear guidance.
  • When listing management tools, present cross-platform options (Azure CLI, REST API) alongside PowerShell, or list them first to avoid implicit Windows-first bias.
  • Add example commands for both PowerShell and Azure CLI where relevant.
GitHub Create Pull Request
Stream Analytics Azure Cosmos DB output from Azure Stream Analytics ...in/articles/stream-analytics/azure-cosmos-db-output.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Windows-centric tools (PowerShell, Visual Studio) before Linux-friendly alternatives (CLI, VS Code) in the 'Next steps' section. There is a subtle prioritization of Windows tools and workflows, though Linux-compatible options are present.
Recommendations
  • List platform-neutral or Linux-friendly tools (Azure CLI, VS Code) before Windows-specific ones in the 'Next steps' section.
  • Explicitly mention cross-platform compatibility for each tool or provide platform-specific instructions where relevant.
  • Add examples or notes highlighting how Linux/macOS users can perform equivalent tasks, especially for PowerShell and Visual Studio steps.
GitHub Create Pull Request
Stream Analytics Azure Functions output from Azure Stream Analytics ...in/articles/stream-analytics/azure-functions-output.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page does not provide explicit code samples or command-line instructions, but the 'Next steps' section lists Windows-centric tools (PowerShell, Visual Studio) before Linux-friendly alternatives (Azure CLI, Visual Studio Code). This ordering and inclusion of Windows-only tools may subtly prioritize Windows workflows and tools for Azure Stream Analytics, potentially creating friction for Linux/macOS users.
Recommendations
  • Ensure Linux/macOS-friendly tools (Azure CLI, Visual Studio Code) are listed before or alongside Windows-only tools in 'Next steps'.
  • Add explicit notes about cross-platform compatibility for each tool, clarifying which are available on Linux/macOS.
  • Provide example workflows or quickstarts for Linux/macOS users, especially for tasks currently only described with Windows tools.
  • If PowerShell or Visual Studio are referenced, offer equivalent instructions for Bash/CLI and VS Code.
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
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows Only Feature
Summary
The documentation is generally cross-platform and does not show a strong Windows bias in its examples, terminology, or tool recommendations. However, it does note that running jobs locally with JavaScript functions is only supported on Windows, which is a Windows-only feature and may disadvantage Linux users.
Recommendations
  • Clearly indicate all feature limitations by platform at the start of the documentation.
  • Where features are Windows-only (such as local JavaScript function support), provide alternative workflows or workarounds for Linux users if possible.
  • Encourage parity in feature support for Linux and document any plans or timelines for Linux support.
  • If possible, provide links to issue trackers or feedback channels for users to request Linux support for missing features.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →