Stream Analytics

120
Total Pages
108
Linux-Friendly Pages
12
Pages with Bias
10.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

24 issues found
Showing 1-24 of 24 flagged pages
Stream Analytics include file ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references a Windows-only executable (telcodatagen.exe) and provides only Windows command-line instructions (using .exe and CMD syntax). There are no Linux/macOS equivalents, nor any mention of how to run the event generator on non-Windows platforms. The instructions for running the event generator are Windows-centric and do not address cross-platform needs.
Recommendations
  • Provide a cross-platform version of the TelcoGenerator application (e.g., .NET Core, Python, or Java) that can run on Linux/macOS.
  • Include Linux/macOS command-line examples (e.g., using ./telcodatagen or mono telcodatagen.exe if applicable).
  • Explicitly state platform requirements and offer alternatives or workarounds for non-Windows users.
  • If the generator is Windows-only, suggest other ways to generate sample data on Linux/macOS (such as using Azure CLI, PowerShell Core, or sample scripts).
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
High Priority View Details →
Scanned: 2026-01-12 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 Azure PowerShell commands for critical role assignment steps, with no mention of Linux/macOS alternatives (such as Azure CLI or REST API). The article assumes access to PowerShell, which is natively available only on Windows, and does not offer cross-platform instructions for Linux or macOS users.
Recommendations
  • Add equivalent Azure CLI commands for role assignment, which are cross-platform and work on Linux/macOS.
  • Explicitly mention REST API options for advanced users who may not use PowerShell.
  • Clarify which steps are platform-agnostic (Azure Portal) and which require command-line tools, providing alternatives for each OS.
  • Include a note or section for Linux/macOS users detailing how to install and use PowerShell Core if absolutely necessary, or preferably guide them to CLI/REST options.
GitHub Create Pull Request
Stream Analytics include file ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references a Windows-only executable (telcodatagen.exe) and provides only Windows command-line instructions (using .exe and .\ path notation). There is no mention of Linux/macOS alternatives, compatibility, or instructions for running the event generator on non-Windows platforms. The command example and tool usage are Windows-centric and presented without cross-platform consideration.
Recommendations
  • Provide instructions for running the event generator on Linux/macOS, such as using Mono or .NET Core if supported.
  • Offer a cross-platform version of the TelcoGenerator app, or suggest alternative methods (e.g., Python script) for generating sample data.
  • Include Linux/macOS command-line examples (e.g., ./telcodatagen.exe or mono telcodatagen.exe) alongside Windows examples.
  • Explicitly state platform requirements and offer guidance for non-Windows users.
GitHub Create Pull Request
Stream Analytics Stream data from confluent cloud Kafka with Azure Stream Analytics ...ain/articles/stream-analytics/confluent-kafka-input.md
Medium Priority View Details →
Scanned: 2026-01-12 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 the section on uploading certificates to Azure Key Vault. All CLI examples are shown using PowerShell syntax and Windows-style file paths (e.g., C:\Users\Downloads\...), with explicit instructions to use PowerShell and no mention of Linux/macOS equivalents. There are no bash or Linux/macOS examples for Azure CLI usage, nor guidance on file path conventions or shell differences. This could create friction for non-Windows users attempting to follow the steps.
Recommendations
  • Provide Azure CLI examples using bash syntax and Linux/macOS file paths (e.g., /home/user/downloads/isrgrootx1.pem).
  • Clarify that Azure CLI works cross-platform and can be used from any shell, not just PowerShell.
  • Add notes or examples for Linux/macOS users, including how to copy file paths and run CLI commands.
  • Avoid language that implies PowerShell is required; use neutral phrasing like 'Open your terminal'.
  • Consider ordering examples so that both Windows and Linux/macOS usage are shown, or alternate which comes first.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ 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 only to PowerShell-based guidance. No Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API) are mentioned, and Windows-centric tools are prioritized.
Recommendations
  • Include equivalent instructions and links for managing Stream Analytics jobs using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Mention REST API options for job management, which are platform-agnostic.
  • Add explicit examples or links for Linux/macOS users, ensuring parity in guidance.
  • Avoid listing Windows/PowerShell tools first unless alternatives are equally visible.
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-12 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 Azure CLI setup and certificate upload sections. All CLI commands are shown using PowerShell syntax, with explicit references to Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem) and instructions like 'right-click and copy the path,' which are Windows-specific. There are no Linux/macOS shell examples, nor any mention of Linux file path conventions or alternate shell usage. This may cause friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide equivalent Bash shell examples for Azure CLI commands, using Linux/macOS file path conventions (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI works across platforms and note any OS-specific differences in file path handling.
  • Avoid instructions that are Windows-specific, such as 'right-click and copy the path'; instead, use cross-platform language like 'locate the certificate file path.'
  • Add a note or section for Linux/macOS users with any relevant tips or caveats.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in the section on uploading certificates to Azure Key Vault. All CLI examples are given in PowerShell syntax, with explicit references to using Azure CLI in PowerShell and Windows-style file paths (e.g., C:\Users\Downloads\...). There are no Linux/macOS shell examples, nor guidance for non-Windows users on file path conventions or CLI usage. The instructions for copying file paths and configuring Azure CLI are also Windows-centric.
Recommendations
  • Provide equivalent Azure CLI examples using bash/zsh syntax for Linux/macOS users.
  • Include notes about file path formats for Linux/macOS (e.g., /home/user/Downloads/isrgrootx1.pem).
  • Clarify that Azure CLI works cross-platform and give installation links for Linux/macOS.
  • Avoid language such as 'configured and installed locally with PowerShell'; mention bash/zsh as alternatives.
  • Add screenshots or instructions relevant to Linux/macOS environments where appropriate.
GitHub Create Pull Request
Stream Analytics Integrating with GitHub Actions .../main/articles/stream-analytics/cicd-github-actions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in the prerequisites and secret creation steps. It instructs users to run the Azure CLI in PowerShell and links only to the Windows installation guide for Azure CLI. All command-line examples and screenshots use PowerShell, with no mention of Linux/macOS terminals or alternative shell environments. There are no instructions or examples for Linux or macOS users, which may cause confusion or friction for those on non-Windows platforms.
Recommendations
  • Include instructions and screenshots for running Azure CLI commands in Bash/zsh on Linux and macOS.
  • Link to Azure CLI installation guides for all platforms (Windows, Linux, macOS) in the prerequisites section.
  • Clarify that the Azure CLI commands work in any terminal, not just PowerShell.
  • Add notes or examples for creating secrets using Linux/macOS terminal environments.
  • Avoid using 'Open PowerShell' as the default instruction; use 'Open your terminal' or specify alternatives.
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-12 00:00
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 commands for all CLI instructions, including installation, project build, configuration, and deployment. There are no Bash, Linux shell, or macOS Terminal equivalents provided, and all deployment steps use PowerShell-specific cmdlets (e.g., Connect-AzAccount, New-AzResourceGroupDeployment), which are not natively available on Linux/macOS. The documentation assumes the user is running PowerShell, creating friction for Linux/macOS users who may use Bash or other shells.
Recommendations
  • Provide Bash (Linux/macOS) equivalents for all CLI commands, especially for npm installation and running the CI/CD tool.
  • Include Azure CLI commands for deployment steps, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention platform compatibility for the Stream Analytics CI/CD tool and clarify if PowerShell is required or if Bash/zsh can be used.
  • Reorder examples so that cross-platform commands (npm, Azure CLI) appear before or alongside PowerShell examples.
  • Add a note or section for Linux/macOS users, outlining any prerequisites or differences in workflow.
GitHub Create Pull Request
Stream Analytics Deploy Azure Stream Analytics jobs using Bicep files ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax and Windows-style paths in all code examples, including npm installation and Azure CLI deployment commands. There are no bash, Linux, or macOS examples, and Windows conventions (e.g., .\ for paths) are shown without alternatives.
Recommendations
  • Provide equivalent bash examples for Linux/macOS users, using $ and forward slashes in paths.
  • Clarify that Azure CLI and npm commands work cross-platform, and show both Windows and Linux/macOS syntax side-by-side.
  • Explicitly mention any OS-specific requirements or differences, such as path formats.
  • Add a note or section addressing Linux/macOS usage, including troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
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-12 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 consistently uses PowerShell syntax for all CLI examples, including npm installation, project build, local run, test case addition, unit testing, and Azure deployment. No Linux/macOS shell (bash/sh/zsh) equivalents are provided. Azure PowerShell modules and commands are used exclusively for deployment, with no mention of Azure CLI or cross-platform alternatives. The only explicit OS-specific note is that JavaScript UDFs work only on Windows, but otherwise, the documentation assumes a Windows/PowerShell environment throughout.
Recommendations
  • Provide bash/sh/zsh examples alongside PowerShell for all CLI commands, especially for npm install and azure-streamanalytics-cicd usage.
  • Include Azure CLI deployment instructions (az deployment group create) as an alternative to PowerShell for ARM template deployment.
  • Clarify cross-platform compatibility of the npm package and commands, noting any Windows-only features (e.g., JavaScript UDFs).
  • Explicitly state OS requirements and limitations at the top of the documentation.
  • Reorder examples or provide tabs for Windows (PowerShell) and Linux/macOS (bash) usage to improve parity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation exclusively provides Azure PowerShell commands for critical RBAC configuration, with no mention of Linux/macOS alternatives such as Azure CLI or REST API. This creates friction for users on non-Windows platforms, as PowerShell is not natively available and may require extra installation or adaptation.
Recommendations
  • Add equivalent Azure CLI commands for role assignment to Cosmos DB.
  • Include REST API example for RBAC configuration.
  • Explicitly mention cross-platform options and provide guidance for Linux/macOS users.
  • Clarify PowerShell requirements and link to installation instructions for non-Windows environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell in the 'Next steps' section as the recommended tool for monitoring and managing Azure Stream Analytics jobs, without mentioning or providing Linux/macOS alternatives such as Azure CLI or Bash. This creates a subtle Windows bias by implying PowerShell is the primary or only method, which may cause friction for Linux/macOS users.
Recommendations
  • Include equivalent Azure CLI or Bash examples for monitoring and managing Stream Analytics jobs.
  • Explicitly mention that PowerShell is available cross-platform, but also provide links or instructions for Linux/macOS users.
  • Reorder or supplement the 'Next steps' to present platform-neutral tools first, or in parallel.
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-11 06:20
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: all command-line examples use PowerShell syntax, and deployment instructions rely on PowerShell-specific Azure modules (Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment). There are no bash, shell, or Azure CLI equivalents provided, nor is there mention of how Linux/macOS users should adapt these steps. The CI/CD tool is installed via npm, which is cross-platform, but all usage and deployment guidance is Windows-centric.
Recommendations
  • Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for deployment steps.
  • Explicitly mention that the CI/CD tool works on Linux/macOS and provide any OS-specific notes if needed.
  • Add a section or callouts for Linux/macOS users, including how to authenticate and deploy using Azure CLI.
  • Reorder examples so that cross-platform commands (npm, Azure CLI) are shown before or alongside PowerShell examples.
GitHub Create Pull Request
Stream Analytics Deploy Azure Stream Analytics jobs using Bicep files ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax (e.g., .\ paths, az CLI commands with Windows path separators) and does not provide any Linux/macOS shell examples. All command-line instructions assume a Windows environment, which may confuse or hinder Linux/macOS users.
Recommendations
  • Provide equivalent Bash examples for Linux/macOS, using forward slashes (/) in paths.
  • Explicitly mention that the az CLI and npm commands work cross-platform, and note any OS-specific differences.
  • Add a section or callout for Linux/macOS users, clarifying how to adapt commands (e.g., path separators, shell syntax).
  • Consider alternating or combining Windows and Linux/macOS examples to demonstrate parity.
GitHub Create Pull Request
Stream Analytics Stream data from confluent cloud Kafka with Azure Stream Analytics ...ain/articles/stream-analytics/confluent-kafka-input.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 several areas. All Azure CLI usage examples are shown in PowerShell syntax, with explicit references to using PowerShell and Windows-style file paths (e.g., C:\Users\Downloads\...). There are no equivalent Linux/macOS shell examples, nor any mention of how to perform the same steps on those platforms. The instructions for copying file paths and configuring Azure CLI are written from a Windows perspective, potentially confusing or excluding Linux/macOS users.
Recommendations
  • Provide Azure CLI examples using Bash syntax and Linux/macOS file paths (e.g., /home/user/downloads/isrgrootx1.pem).
  • Explicitly state that Azure CLI works cross-platform and provide instructions for installing and using it on Linux/macOS.
  • Include notes or examples for copying file paths on Linux/macOS.
  • Avoid language that assumes PowerShell or Windows as the default environment.
  • Where screenshots or instructions reference Windows-specific UI elements, add Linux/macOS equivalents or clarifications.
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-11 06:20
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 its instructions for uploading certificates to Azure Key Vault. All CLI examples are shown using PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\...), with explicit instructions to use PowerShell and references to right-clicking files to copy pathsβ€”a Windows-specific action. There are no Linux/macOS shell examples, nor guidance for Linux file paths or alternative methods for uploading certificates. This may create friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide equivalent Azure CLI examples using bash/zsh syntax, with Linux/macOS-style file paths (e.g., /home/user/Downloads/isrgrootx1.pem).
  • Clarify that Azure CLI can be used on Linux/macOS and provide installation/setup instructions for those platforms.
  • Replace or supplement instructions about copying file paths with platform-agnostic guidance.
  • Explicitly mention that the steps apply to all platforms, and highlight any platform-specific differences.
  • Include screenshots or notes relevant to Linux/macOS environments where appropriate.
GitHub Create Pull Request
Stream Analytics Integrating with GitHub Actions .../main/articles/stream-analytics/cicd-github-actions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 by instructing users to run Azure CLI commands specifically in PowerShell, linking only to the Windows installation guide for Azure CLI, and showing screenshots from PowerShell. There are no examples or instructions for running the same commands in Linux/macOS terminals, nor are there references to Bash or other common shells. This may cause friction for Linux/macOS users who need to adapt the instructions to their environments.
Recommendations
  • Explicitly state that Azure CLI can be run in Bash, zsh, or other Linux/macOS terminals, not just PowerShell.
  • Provide links to Azure CLI installation guides for Linux and macOS alongside the Windows guide.
  • Include example commands and screenshots for Linux/macOS terminals (e.g., Bash) where appropriate.
  • Avoid specifying PowerShell unless there is a Windows-specific requirement; use 'terminal' or 'command line' generically.
  • Clarify that the instructions are cross-platform and highlight any OS-specific differences.
GitHub Create Pull Request
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation consistently uses PowerShell syntax and Windows-specific tools (e.g., Connect-AzAccount, New-AzResourceGroupDeployment) for all command-line examples, with no mention or examples for Linux/macOS shells (bash, sh, etc.) or Azure CLI equivalents. The only explicit OS note is that JavaScript UDFs only work on Windows, but otherwise, Linux users are left to infer compatibility and usage. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Provide bash/sh examples alongside PowerShell for all CLI commands, especially npm and azure-streamanalytics-cicd usage.
  • Include Azure CLI equivalents for deployment steps, not just Azure PowerShell.
  • Explicitly state OS compatibility for the npm package and commands.
  • Add notes or troubleshooting for common Linux/macOS issues (e.g., path separators, permissions).
  • Reorder examples so that cross-platform or Linux/macOS instructions are shown first or 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-11 06:20
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 on uploading certificates to Azure Key Vault. All CLI examples are shown using PowerShell syntax, with explicit references to Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem) and instructions to configure Azure CLI 'locally with PowerShell.' There are no equivalent Linux/macOS shell examples, nor any mention of Linux/macOS file path conventions. This may create friction for non-Windows users attempting to follow the steps.
Recommendations
  • Provide CLI command examples using Bash syntax and Linux/macOS file paths (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI works on Linux/macOS and provide setup instructions for those platforms.
  • Avoid language that implies PowerShell is required; instead, refer to 'your preferred shell.'
  • Add notes or examples for Linux/macOS users where file paths or shell commands differ.
  • Consider reordering examples or providing parallel examples for both Windows and Linux/macOS.
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-12 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 (PowerShell, Visual Studio) before Linux-friendly alternatives (Azure CLI, Visual Studio Code) in the 'Next steps' section. PowerShell and Visual Studio are traditionally Windows-focused, and their inclusion before cross-platform options may create a perception of Windows preference. No explicit Linux/macOS examples or guidance are provided, and there is no mention of platform-specific considerations for Linux users.
Recommendations
  • List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific options in the 'Next steps' section.
  • Explicitly mention that Azure CLI and Visual Studio Code are available on Linux/macOS and provide links or notes for Linux/macOS users.
  • Add example workflows or commands for Linux/macOS environments where relevant.
  • Clarify any platform-specific limitations or differences in the main documentation body.
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-12 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, ARM templates, Visual Studio Code) in the 'Next steps' section. While the main content is platform-neutral, the ordering and inclusion of Windows tools may subtly prioritize Windows workflows.
Recommendations
  • Reorder the 'Next steps' section to list cross-platform tools (CLI, ARM templates, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio).
  • Explicitly note which tools are cross-platform and which are Windows-only, helping users choose appropriate options.
  • Add Linux/macOS-specific guidance or links where relevant, especially for PowerShell and Visual Studio steps.
  • Ensure code samples and walkthroughs are provided for both Windows and Linux/macOS environments.
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-11 06:20
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 workflows (PowerShell, Visual Studio) before Linux-friendly alternatives (CLI, VS Code). PowerShell and Visual Studio are Windows-first tools, and their quickstarts are highlighted alongside more cross-platform options, but Windows examples/tools are given prominence. There are no explicit Linux/macOS examples or notes about platform differences.
Recommendations
  • Ensure that cross-platform tools (Azure CLI, VS Code) are listed before Windows-specific tools in quickstart sections.
  • Add explicit Linux/macOS examples or notes where workflows differ, especially for CLI usage.
  • Clarify which tools are cross-platform and which are Windows-only, so users can choose appropriately.
  • Provide parity in walkthroughs and screenshots for Linux/macOS environments where relevant.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation page does not provide explicit OS-specific examples, but the 'Next steps' section lists Windows-centric tools (PowerShell, Visual Studio) before Linux-friendly alternatives (CLI, ARM template, VS Code). PowerShell and Visual Studio are primarily Windows tools, and their inclusion ahead of CLI and VS Code may signal a subtle Windows-first bias. No Linux/macOS-specific instructions or examples are provided, and there is no mention of platform-specific considerations for running Azure Functions or Stream Analytics jobs.
Recommendations
  • Reorder the 'Next steps' section to list cross-platform tools (Azure CLI, ARM template, VS Code) before Windows-only tools (PowerShell, Visual Studio).
  • Explicitly mention that Azure CLI and VS Code are cross-platform and provide links or notes for Linux/macOS users.
  • Add a brief section noting that all features described are available on Linux/macOS, or call out any platform-specific caveats if they exist.
  • Where PowerShell or Visual Studio are mentioned, add equivalent instructions or links for Linux/macOS users (e.g., Bash scripts, VS Code usage).
GitHub Create Pull Request