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 1-25 of 98 flagged pages
Stream Analytics include file ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-13 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 a command prompt example using Windows syntax. There is no mention of Linux/macOS alternatives, nor are cross-platform instructions or tools provided for generating event data. The use of a .exe file and Windows command syntax creates friction for non-Windows users.
Recommendations
  • Provide a cross-platform event generator tool (e.g., a .NET Core, Python, or Java version) or instructions for running the existing tool on Linux/macOS (such as via Mono or Wine, if feasible).
  • Include Linux/macOS command-line examples (e.g., using bash/sh syntax) alongside Windows examples.
  • Explicitly state platform requirements and offer alternatives or workarounds for non-Windows users.
  • Consider distributing the event generator as a platform-agnostic package (e.g., Docker container, Python script, or .NET Core app).
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into Kafka ...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority View Details →
Scanned: 2026-01-11 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 several ways: Azure CLI usage is shown exclusively via PowerShell syntax, with explicit instructions to configure Azure CLI locally with PowerShell. Example file paths use Windows conventions (e.g., C:\Users\Downloads\certificatefile.pem), and there are no Linux or macOS equivalents or guidance. The documentation does not mention Bash, Linux, or cross-platform considerations for Azure CLI, nor does it provide examples for non-Windows environments.
Recommendations
  • Provide Azure CLI examples using Bash syntax, including Linux/macOS file paths (e.g., /home/user/certificatefile.pem).
  • Add a note clarifying that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Include instructions or links for installing and configuring Azure CLI on Linux and macOS.
  • Show example commands for uploading certificates from Linux/macOS environments.
  • Avoid language such as 'configured locally with PowerShell' and use more inclusive phrasing like 'configured locally with your preferred shell (PowerShell, Bash, etc.)'.
GitHub Create Pull Request
Stream Analytics Azure Cosmos DB output from Azure Stream Analytics ...in/articles/stream-analytics/azure-cosmos-db-output.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows evidence of Windows bias in the 'Next steps' section, where Windows-centric tools (PowerShell, Visual Studio) are listed before cross-platform or Linux-friendly options (Azure CLI, Visual Studio Code). PowerShell and Visual Studio are primarily Windows tools, and their inclusion (and ordering) suggests a preference for Windows environments. There are no Linux-specific examples, nor is there mention of Linux-native tools or patterns.
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 and provide examples or links for Linux users, such as using Azure CLI on Linux.
  • Add a note clarifying which tools are cross-platform and which are Windows-only.
  • Include Linux-specific instructions or troubleshooting tips where relevant.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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 using PowerShell commands and Azure PowerShell modules for all examples, without providing equivalent Bash or Linux shell commands. The deployment steps rely on Windows-centric tools (PowerShell, Connect-AzAccount, New-AzResourceGroupDeployment), and there is no mention of Linux alternatives or cross-platform CLI usage. All code samples and instructions assume a Windows environment, making it difficult for Linux or macOS users to follow along.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell commands, especially for deployment steps (e.g., using az login, az deployment group create).
  • Explicitly mention that the CI/CD tool can be used on Linux/macOS and provide instructions for those platforms.
  • Add notes or sections highlighting cross-platform compatibility and any platform-specific considerations.
  • Avoid assuming PowerShell as the default shell; offer both PowerShell and Bash syntax where possible.
  • Reference Linux and macOS environments in prerequisites and examples, ensuring parity in guidance.
GitHub Create Pull Request
Stream Analytics Automate builds, tests, and deployments using CI/CD tools ...docs/blob/main/articles/stream-analytics/cicd-tools.md
High Priority View Details →
Scanned: 2026-01-11 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 exhibits a strong Windows bias. All command-line examples use PowerShell syntax, and Windows-specific tools (e.g., PowerShell cmdlets like Connect-AzAccount, New-AzResourceGroupDeployment) are exclusively referenced for deployment. There are no Linux shell (bash/sh) equivalents or examples, and Windows is mentioned as a requirement for JavaScript UDFs. The documentation does not provide guidance for Linux or macOS users, nor does it mention cross-platform alternatives for Azure CLI or deployment steps.
Recommendations
  • Provide equivalent bash/sh examples for all commands, especially npm install and azure-streamanalytics-cicd usage.
  • Include Azure CLI deployment instructions alongside PowerShell, as Azure CLI is cross-platform.
  • Explicitly state platform compatibility for all features and commands (e.g., which commands work on Windows, Linux, macOS).
  • Add notes or sections for Linux/macOS users, including troubleshooting and environment setup.
  • Where PowerShell is used, clarify that commands can be run in any shell and provide syntax for bash (e.g., export variables, file paths).
  • Mention limitations or alternatives for features that are Windows-only (e.g., JavaScript UDFs), and suggest Linux-compatible approaches if available.
GitHub Create Pull Request
Stream Analytics Deploy Azure Stream Analytics jobs using Bicep files ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
High Priority View Details →
Scanned: 2026-01-11 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 by providing all command-line examples in PowerShell syntax (e.g., using backslashes in paths, PowerShell prompt style), and does not mention or provide equivalent Bash/Linux shell commands. There is no guidance for Linux or macOS users, nor are there examples using Linux path conventions or shell environments.
Recommendations
  • Include Bash/Linux shell examples alongside PowerShell commands, using forward slashes for paths and appropriate shell syntax.
  • Explicitly state that the tools and commands work cross-platform, and provide installation and usage instructions for Linux/macOS.
  • Add notes or sections for Linux/macOS users, highlighting any differences in command usage, file paths, or prerequisites.
  • Use generic CLI syntax (e.g., az CLI) where possible, and avoid Windows-specific conventions unless necessary.
GitHub Create Pull Request
Stream Analytics Integrating with GitHub Actions .../main/articles/stream-analytics/cicd-github-actions.md
High Priority View Details →
Scanned: 2026-01-11 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 by exclusively referencing PowerShell for command execution and providing installation instructions for the Azure CLI only for Windows. There are no examples or instructions for running commands on Linux or macOS, nor are alternative shells (such as Bash) mentioned. This may hinder Linux and macOS users from following the guide seamlessly.
Recommendations
  • Include instructions for installing Azure CLI on Linux and macOS, with appropriate links.
  • Provide command examples using Bash or generic shell syntax alongside PowerShell.
  • Clarify that the az CLI commands can be run in any terminal (PowerShell, Bash, etc.) and specify any OS-specific differences if relevant.
  • Add screenshots or terminal examples from Linux/macOS environments where applicable.
  • Avoid language that implies PowerShell is required; use more inclusive phrasing such as 'Open your terminal (PowerShell, Bash, etc.)'.
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into confluent cloud kafka ...in/articles/stream-analytics/confluent-kafka-output.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily in the section on uploading certificates to Azure Key Vault. All CLI examples are shown using PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\...), with instructions such as 'right-click on the certificate and copy the path' that are specific to Windows. There are no Linux/macOS equivalents or examples, and the guidance for installing/configuring Azure CLI refers to PowerShell. This may hinder Linux users or those on non-Windows platforms.
Recommendations
  • Provide CLI examples using Bash syntax and Linux/macOS file paths (e.g., /home/user/Downloads/isrgrootx1.pem) alongside PowerShell examples.
  • Include instructions for copying file paths or locating files on Linux/macOS systems.
  • Clarify that Azure CLI is cross-platform and provide installation/configuration guidance for Linux/macOS users.
  • Explicitly state that the commands work on all platforms and highlight any platform-specific considerations.
  • Add screenshots or notes relevant to Linux/macOS environments where appropriate.
GitHub Create Pull Request
Stream Analytics include file ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing only Windows-specific instructions and examples for running the TelcoGenerator application (e.g., using .exe files and Windows command prompt syntax). There are no instructions or examples for running the event generator on Linux or macOS, nor is there mention of cross-platform alternatives or prerequisites. The documentation assumes the user is on a Windows environment, both in tooling and in command-line usage.
Recommendations
  • Provide explicit instructions for running the TelcoGenerator application on Linux and macOS, including any prerequisites such as Mono or .NET Core if applicable.
  • Include Linux/macOS command-line examples (e.g., using ./telcodatagen.exe with mono, or a platform-agnostic .NET command if available).
  • Mention any platform limitations or required dependencies for non-Windows users.
  • If the event generator is Windows-only, suggest or provide a cross-platform alternative or sample script for Linux/macOS users.
  • Ensure screenshots and terminology are inclusive of all supported platforms (e.g., refer to 'terminal' instead of 'command window' where appropriate).
GitHub Create Pull Request
Stream Analytics Stream data from confluent cloud Kafka with Azure Stream Analytics ...ain/articles/stream-analytics/confluent-kafka-input.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily in the section on uploading certificates to Azure Key Vault. All command-line examples use PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\...), and instructions reference configuring Azure CLI with PowerShell. There are no equivalent examples or guidance for Linux/macOS users, such as using Bash or providing Linux-style file paths. The documentation assumes a Windows environment for local operations, potentially excluding or confusing users on other platforms.
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 link to installation instructions for Linux and macOS.
  • Add a note or section clarifying how to perform certificate upload and related tasks on Linux/macOS, including how to find and reference file paths.
  • Avoid referencing PowerShell exclusively; use neutral language or show both PowerShell and Bash examples side-by-side.
  • Review screenshots and instructions to ensure they are not Windows-specific, or supplement with Linux/macOS equivalents where relevant.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
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 that would be more cross-platform and Linux-friendly. The instructions and tooling references are Windows-centric, and there is no mention of how to perform the same steps on Linux or macOS environments.
Recommendations
  • Add Azure CLI examples for role assignment to Azure Cosmos DB, as Azure CLI is cross-platform and widely used on Linux.
  • Include REST API or ARM template instructions for users who may automate deployments from non-Windows environments.
  • Explicitly mention Linux/macOS compatibility and provide guidance for those platforms.
  • Reorder instructions so that cross-platform methods (CLI/REST) are presented before or alongside PowerShell examples.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but recommend CLI for native Linux workflows.
GitHub Create Pull Request
Stream Analytics Achieve geo-redundancy for Azure Stream Analytics jobs .../blob/main/articles/stream-analytics/geo-redundancy.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing PowerShell for monitoring and managing Azure Stream Analytics jobs in the 'Next steps' section. There are no examples or mentions of Linux-native tools, such as Azure CLI or Bash scripts, nor are cross-platform alternatives presented. The documentation assumes familiarity with Windows tooling and does not provide parity for Linux users.
Recommendations
  • Include Azure CLI examples for monitoring and managing Stream Analytics jobs alongside PowerShell references.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and provide links to relevant Linux-compatible documentation.
  • Add sample Bash scripts or command-line instructions for Linux users where appropriate.
  • Ensure that cross-platform tools are presented before or alongside Windows-specific tools to avoid implicit prioritization.
GitHub Create Pull Request
Stream Analytics Azure Cosmos DB output from Azure Stream Analytics ...in/articles/stream-analytics/azure-cosmos-db-output.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before Linux-friendly alternatives, and by including multiple quickstarts for Windows-specific environments (PowerShell, Visual Studio) while only briefly mentioning the Azure CLI and Visual Studio Code, which are more cross-platform. There are no explicit Linux examples or references to Linux-specific workflows, and Windows tools are given prominence in the 'Next steps' section.
Recommendations
  • Add explicit Linux examples or workflows, such as using Bash or Linux shell scripts for Azure Stream Analytics job creation.
  • Reorder the 'Next steps' section to present cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio).
  • Include notes or guidance for Linux users, such as package installation instructions or environment setup steps.
  • Ensure parity in documentation by providing equivalent instructions for both Windows and Linux environments wherever possible.
GitHub Create Pull Request
Stream Analytics Deploy Azure Stream Analytics jobs using Bicep files ...in/articles/stream-analytics/cicd-deploy-with-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily uses PowerShell syntax in all command-line examples, including npm installation and Azure CLI deployment commands. There are no Bash or Linux shell equivalents provided, and Windows-style paths (e.g., .\DeployV2\...) are used exclusively. This suggests a Windows-first approach and may hinder Linux users from following the instructions directly.
Recommendations
  • Provide Bash/Linux shell equivalents for all command-line examples, especially for npm and Azure CLI commands.
  • Use cross-platform path notation (e.g., ./DeployV2/{project-name}.JobTemplate.bicep) in examples, or show both Windows and Linux path formats.
  • Explicitly mention that the Azure CLI commands work on both Windows and Linux, and provide any necessary notes about differences (such as path separators).
  • Include a note or section for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Stream Analytics Integrating with GitHub Actions .../main/articles/stream-analytics/cicd-github-actions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias by exclusively referencing PowerShell for command-line operations (e.g., running az CLI commands), linking only to Windows installation instructions for Azure CLI, and omitting any mention of Linux or macOS equivalents. All screenshots and instructions assume a Windows environment, with no guidance for users on other platforms.
Recommendations
  • Include instructions and screenshots for running az CLI commands in Linux and macOS terminals, not just PowerShell.
  • Provide links to Azure CLI installation guides for Linux and macOS alongside the Windows guide.
  • Use platform-agnostic language when referring to command-line operations (e.g., 'open a terminal' instead of 'open PowerShell').
  • Add notes or sections highlighting any platform-specific differences or considerations.
  • Ensure that all example commands work equally well on Linux, macOS, and Windows, and clarify any platform-specific syntax if necessary.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 using PowerShell for all command-line examples, referencing Windows-specific tools (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment), and omitting equivalent Linux/macOS shell commands. There are no bash or CLI examples, and the workflow assumes a Windows environment for deployment and configuration steps. The documentation does not mention or prioritize Linux or cross-platform usage, despite the CI/CD tool being Node.js-based and potentially usable on other platforms.
Recommendations
  • Provide equivalent bash/zsh shell examples for all command-line steps, especially for npm installation and CI/CD tool usage.
  • Include Azure CLI commands for authentication and deployment, which work cross-platform (e.g., az login, az deployment group create).
  • Explicitly state platform compatibility for the Stream Analytics CI/CD tool and clarify any OS-specific requirements.
  • Reorder or balance examples so that Linux/macOS instructions are presented alongside or before Windows/PowerShell instructions.
  • Add notes or sections for common Linux/macOS workflows, including file path conventions and terminal usage.
GitHub Create Pull Request
Stream Analytics Automate builds, tests, and deployments using CI/CD tools ...docs/blob/main/articles/stream-analytics/cicd-tools.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a strong Windows bias. All command-line examples use PowerShell syntax, and there are no bash or Linux shell equivalents provided. Windows-specific tools and patterns (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment) are used exclusively, with no mention of cross-platform alternatives like Azure CLI. The documentation notes that JavaScript UDFs only work on Windows, but does not offer Linux alternatives or guidance. The overall structure and examples assume a Windows environment, potentially excluding Linux users.
Recommendations
  • Provide equivalent bash/Linux shell examples for all commands, especially npm install and azure-streamanalytics-cicd usage.
  • Include Azure CLI examples for authentication and deployment, alongside PowerShell.
  • Explicitly state platform compatibility for all features and commands, and offer Linux/macOS-specific guidance where Windows-only features exist.
  • Add notes or sections for Linux users, including troubleshooting and environment setup tips.
  • Where features are Windows-only (e.g., JavaScript UDF), suggest alternative approaches or clarify limitations for Linux users.
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into confluent cloud kafka ...in/articles/stream-analytics/confluent-kafka-output.md
High Priority View Details →
Scanned: 2026-01-10 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 several ways: all command-line examples use PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\...), and instructions reference copying file paths via right-click, a Windows-specific pattern. There are no examples or guidance for Linux or macOS users, such as using bash, Linux file paths, or alternative methods for uploading certificates. The Azure CLI is cross-platform, but its usage is only shown in a Windows context.
Recommendations
  • Provide parallel command-line examples using bash syntax and Linux/macOS file paths (e.g., /home/user/Downloads/isrgrootx1.pem).
  • Explicitly mention that Azure CLI works on Linux and macOS, and provide installation/setup links for those platforms.
  • Describe how to copy file paths or locate downloaded files on Linux/macOS.
  • Include screenshots or instructions relevant to Linux/macOS environments where appropriate.
  • Avoid language that assumes a Windows environment (e.g., 'right-click to copy path'), or provide alternatives for other platforms.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, without mentioning or providing equivalent Azure CLI or REST API examples that are more cross-platform and Linux-friendly. The instructions and tooling references are centered on PowerShell, which is traditionally a Windows tool, and there is no guidance for users on Linux or macOS systems. The documentation also refers to the Azure Portal UI, which is platform-agnostic, but the only automation example is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI commands for role assignment to Azure Cosmos DB, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API examples for role assignment to support automation from any OS.
  • Explicitly mention that PowerShell is available on Linux and macOS, but recommend Azure CLI for cross-platform compatibility.
  • Add a section or note for Linux/macOS users, outlining steps and tools they can use to achieve the same outcome.
  • Ensure that all code samples and instructions are presented in a way that does not assume a Windows environment.
GitHub Create Pull Request
Stream Analytics Stream data from confluent cloud Kafka with Azure Stream Analytics ...ain/articles/stream-analytics/confluent-kafka-input.md
High Priority View Details →
Scanned: 2026-01-10 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 by providing all Azure CLI command examples in PowerShell syntax, referencing Windows file paths (e.g., C:\Users\Downloads\...), and instructing users to use PowerShell for Azure CLI setup. There are no Linux or macOS shell examples, nor any mention of Linux-specific patterns for file paths or command usage. The instructions and screenshots are tailored to Windows environments, potentially excluding or confusing Linux users.
Recommendations
  • Provide equivalent Azure CLI command examples using bash/zsh syntax for Linux/macOS users.
  • Include notes or sections on how to locate file paths and upload certificates on Linux (e.g., /home/user/Downloads/isrgrootx1.pem).
  • Avoid language such as 'right-click and copy the path' which is Windows-specific; instead, suggest cross-platform methods for finding file paths.
  • Clarify that Azure CLI works cross-platform and provide installation/setup instructions for Linux and macOS.
  • Add screenshots or instructions that are not OS-specific, or explicitly mention differences for Linux/macOS users.
GitHub Create Pull Request
Stream Analytics Stream data from Azure Stream Analytics into Kafka ...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias primarily in the section describing how to upload certificates to Azure Key Vault. All CLI examples are provided using PowerShell syntax and Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem), with explicit instructions to configure Azure CLI locally with PowerShell. There is no mention of Linux/macOS equivalents, nor are bash or cross-platform examples provided. The guidance assumes a Windows environment for local setup and file path conventions.
Recommendations
  • Provide Azure CLI examples using bash syntax and Linux/macOS file paths (e.g., /home/user/certificatefile.pem) alongside PowerShell examples.
  • Clarify that Azure CLI can be used on Windows, Linux, and macOS, and provide setup instructions for all platforms.
  • Avoid language that assumes PowerShell is the default shell; mention bash/zsh as alternatives.
  • Add notes or examples for uploading certificates from Linux/macOS environments, including how to locate file paths and run CLI commands.
  • Ensure screenshots and instructions are platform-neutral or provide variants for both Windows and Linux/macOS.
GitHub Create Pull Request
Stream Analytics include file ...icles/stream-analytics/includes/event-generator-app.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by only providing instructions and examples for running the TelcoGenerator application using Windows command prompt and referencing a Windows executable (.exe). There are no examples or guidance for running the application on Linux or macOS, nor are alternative tools or commands suggested for non-Windows environments.
Recommendations
  • Provide instructions for running the TelcoGenerator application on Linux and macOS, including any prerequisites (such as Mono or .NET runtime) and equivalent terminal commands.
  • If the application is Windows-only, explicitly state this limitation and suggest alternatives or workarounds for Linux users.
  • Include cross-platform command-line examples (e.g., bash/zsh) alongside Windows cmd examples.
  • Mention any dependencies or compatibility notes for non-Windows users, and provide troubleshooting tips for running the application outside of Windows.
GitHub Create Pull Request
Stream Analytics Achieve geo-redundancy for Azure Stream Analytics jobs .../blob/main/articles/stream-analytics/geo-redundancy.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by exclusively referencing PowerShell for monitoring and managing Azure Stream Analytics jobs in the 'Next steps' section. There are no Linux or cross-platform alternatives mentioned, such as Azure CLI or Bash scripts, and no examples or guidance for non-Windows environments. This can lead Linux users to feel unsupported or unclear about how to achieve parity in management tasks.
Recommendations
  • Include Azure CLI examples for monitoring and managing Stream Analytics jobs alongside PowerShell instructions.
  • Explicitly mention cross-platform tools and provide links or code samples for Linux and macOS users.
  • Balance references to PowerShell with equivalent Bash or shell script examples where applicable.
  • Add a section or note clarifying that management tasks can be performed from Linux and macOS environments, not just Windows.
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: 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 on uploading certificates to Azure Key Vault. All command-line examples use PowerShell syntax and Windows-style file paths (e.g., C:\Users\Downloads\...), and instructions reference copying file paths using Windows Explorer. There are no examples or guidance for Linux or macOS users, such as Bash syntax, Linux file paths, or alternative methods for copying file paths. The documentation assumes the user is operating on Windows and using PowerShell, omitting equivalent Linux workflows.
Recommendations
  • Provide parallel command-line examples using Bash syntax for Linux/macOS users.
  • Include Linux-style file path examples (e.g., /home/user/downloads/isrgrootx1.pem) alongside Windows paths.
  • Add instructions for copying file paths on Linux/macOS (e.g., using the terminal or file manager).
  • Clarify that Azure CLI works cross-platform and specify any OS-specific considerations.
  • Mention that the Azure CLI commands can be run in Bash, Zsh, or other shells, not just PowerShell.
  • Review screenshots and instructions to ensure they are not exclusively Windows-centric.
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: 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 exclusively referencing PowerShell for running Azure CLI commands, linking only to the Windows installation guide for Azure CLI, and omitting any mention or examples for Linux or macOS environments. All screenshots and instructions assume a Windows setup, with no guidance for users on other platforms.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, including terminal commands and screenshots.
  • Link to Azure CLI installation guides for Linux and macOS alongside the Windows guide.
  • Clarify that Azure CLI can be run in any terminal (e.g., Bash, zsh), not just PowerShell.
  • Include notes or sections for cross-platform compatibility, highlighting any differences in command syntax or environment setup.
  • Ensure that all steps, especially those involving command-line operations, are platform-agnostic or offer alternatives for non-Windows users.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →