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 (38)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cosmos-db-managed-identity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, with no equivalent Azure CLI or REST API examples. It explicitly states that role assignment must be done via Azure PowerShell, which is primarily a Windows-centric tool, and does not mention or provide guidance for Linux or cross-platform users. There are no Bash or Linux shell examples, and the documentation assumes access to PowerShell.
Recommendations:
  • Provide equivalent Azure CLI (az) commands for role assignment, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API or ARM template examples for users who may want to automate the process in a platform-agnostic way.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, if PowerShell is truly required, and provide installation instructions or links.
  • Add a note or section addressing Linux/macOS users, ensuring parity in instructions and tooling.
  • Where possible, avoid language that implies PowerShell is the only supported method, unless it is a technical limitation, and clarify if so.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily focused on using Visual Studio for local debugging of Azure Stream Analytics queries, which is a Windows-centric tool. There are no examples or instructions for Linux users, nor are any cross-platform alternatives (such as Visual Studio Code or CLI-based workflows) mentioned. All steps, screenshots, and references assume the use of Visual Studio on Windows, and there is no guidance for achieving similar functionality on Linux or macOS.
Recommendations:
  • Provide equivalent instructions for Linux users, such as using Visual Studio Code with relevant extensions or Azure CLI for local testing and debugging.
  • Explicitly mention platform requirements and, if the feature is Windows-only, suggest alternative workflows for non-Windows users.
  • Include cross-platform examples and screenshots, or clarify which steps are not available on Linux/macOS.
  • Reference any available tools or SDKs that support local debugging on Linux, or provide a roadmap for such support if it does not exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-cosmos-db-output.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page shows a mild Windows bias in the 'Next steps' section, where Windows-centric tools and workflows (PowerShell, Visual Studio) are listed before cross-platform or Linux-friendly options (Azure CLI, Visual Studio Code). There is a dedicated PowerShell quickstart, and Visual Studio (Windows-only) is mentioned before Visual Studio Code. No Linux-specific examples or tools are highlighted, and there is no mention of Linux shell or scripting environments.
Recommendations:
  • List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio) in the 'Next steps' section.
  • Explicitly mention Linux and macOS compatibility where applicable, especially for Azure CLI and Visual Studio Code.
  • Provide Linux shell (bash) examples or references alongside PowerShell examples.
  • Add a note clarifying which tools are cross-platform and which are Windows-only.
  • Consider including a Linux-specific quickstart or troubleshooting guide.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-functions-output.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page exhibits subtle Windows bias, particularly in the 'Next steps' section, where Windows-centric tools (PowerShell, Visual Studio) are listed before or alongside cross-platform alternatives. There is a dedicated quickstart for Azure PowerShell and Visual Studio (both Windows-focused), while Linux-native or cross-platform command-line examples (like Bash or Linux shell) are not specifically highlighted. No explicit Linux examples or tools are mentioned, and the ordering of next steps may suggest a preference for Windows environments.
Recommendations:
  • Add explicit Linux/bash shell examples or quickstarts, especially for common tasks (e.g., using Azure CLI from Bash).
  • Ensure that cross-platform tools (Azure CLI, Visual Studio Code) are listed before or at least alongside Windows-specific tools in 'Next steps'.
  • Include notes or sections clarifying that all features and instructions apply equally to Linux and macOS environments where applicable.
  • Where PowerShell is mentioned, also provide equivalent Bash or shell commands for Linux users.
  • Consider adding a table or section comparing tool availability and usage across Windows, Linux, and macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-output.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing Windows file paths (e.g., C:\Users\Downloads), and instructing users to use PowerShell for Azure CLI operations. There are no Linux/macOS equivalents or notes, and instructions such as 'right-click and copy the path' are Windows-specific. No mention is made of Linux or cross-platform considerations, despite Azure CLI being cross-platform.
Recommendations:
  • Provide command-line examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, especially for Azure CLI commands.
  • Use generic or platform-neutral file paths in examples (e.g., /home/user/Downloads/isrgrootx1.pem for Linux/macOS).
  • Add notes or sections explaining how to perform steps (such as copying file paths) on Linux/macOS.
  • Explicitly state that Azure CLI can be used on Windows, Linux, and macOS, and link to relevant installation guides for each platform.
  • Where screenshots or UI steps are shown, clarify if there are any platform-specific differences or confirm that the steps are the same across platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/includes/event-generator-app.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/geo-redundancy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page references PowerShell specifically in the 'Next steps' section, suggesting it as the primary tool for monitoring and managing Azure Stream Analytics jobs. There are no examples or mentions of Linux-native tools, Bash, or cross-platform alternatives, which may make Linux users feel unsupported.
Recommendations:
  • Include equivalent Bash or Azure CLI examples and links alongside PowerShell references.
  • Explicitly mention that Azure Stream Analytics management can be performed from Linux, macOS, and Windows, and provide cross-platform instructions.
  • Balance the 'Next steps' section by linking to documentation for both PowerShell and Azure CLI/Bash management.
  • Where possible, use neutral language (e.g., 'use your preferred shell or scripting environment') and provide code snippets for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/feature-comparison.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a moderate Windows bias. Visual Studio (a Windows-only tool) is mentioned in the commented-out sections and in the 'Next steps' links, sometimes before Visual Studio Code (which is cross-platform). The feature table for JavaScript UDF and UDA explicitly states 'Windows only' for Visual Studio Code, without further explanation or Linux alternatives. There are no Linux-specific examples, troubleshooting, or parity notes, and the documentation does not highlight or address limitations/workarounds for non-Windows users.
Recommendations:
  • Ensure all feature tables and descriptions clarify platform limitations, and provide workarounds or alternatives for Linux/macOS users where possible.
  • In 'Next steps' and throughout the documentation, list cross-platform tools (like Visual Studio Code) before Windows-only tools (like Visual Studio) to avoid Windows-first bias.
  • Where features are Windows-only (e.g., JavaScript UDF/UDA), explicitly state the limitation and, if possible, provide a roadmap or alternatives for Linux/macOS users.
  • Add Linux/macOS-specific examples, troubleshooting tips, or notes to improve parity and inclusivity.
  • Consider a dedicated section summarizing platform support and limitations for all major features.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing only PowerShell examples for Azure CLI commands, referencing Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem), and instructing users to configure Azure CLI locally with PowerShell. There are no equivalent Linux/macOS command-line examples, nor are Linux file path conventions or shell environments mentioned.
Recommendations:
  • Provide Azure CLI command examples using Bash (or generic shell) syntax alongside PowerShell, including Linux/macOS file path examples (e.g., /home/user/certificatefile.pem).
  • Clarify that Azure CLI can be used on Windows, Linux, and macOS, and provide links or instructions for installing and using Azure CLI on non-Windows platforms.
  • Avoid language that assumes PowerShell as the default shell; instead, offer both PowerShell and Bash command blocks where appropriate.
  • Include notes or callouts for any platform-specific considerations, such as file path formats or shell differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/input-validation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram-vs-code.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Windows First
Summary:
The documentation page is generally cross-platform as it focuses on Visual Studio Code, which is available on both Windows and Linux. However, there is a notable Windows bias in the 'Limitations' section, where it states that running jobs locally with JavaScript functions is only supported on Windows. No Linux-specific instructions, troubleshooting, or parity notes are provided elsewhere. There are no Linux or macOS examples, nor are there alternative workflows or caveats for non-Windows users.
Recommendations:
  • Explicitly state which features are supported on Linux and macOS, not just Windows.
  • Provide alternative instructions or workarounds for Linux/macOS users where features are Windows-only.
  • Add Linux/macOS-specific troubleshooting tips or known issues if certain features are unavailable.
  • Include parity tables or notes to clarify which features are cross-platform and which are not.
  • If possible, prioritize cross-platform support for local JavaScript function execution or provide a roadmap for Linux/macOS support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-tools.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias: all code examples use PowerShell syntax, Windows-specific tools (such as Connect-AzAccount and New-AzResourceGroupDeployment) are used exclusively, and there are no Bash or Linux shell equivalents provided. The only mention of platform differences is a note that JavaScript UDFs only work on Windows, but no guidance or alternatives are offered for Linux users. This could make it difficult for Linux or macOS users to follow the instructions or adapt them to their environments.
Recommendations:
  • Provide all command-line examples in both PowerShell and Bash (or generic shell) syntax, especially for npm commands and directory navigation.
  • Include Azure CLI equivalents for deployment steps (e.g., az login, az deployment group create) alongside PowerShell cmdlets.
  • Explicitly state platform requirements or limitations at the beginning of the article, and offer alternatives or workarounds for non-Windows users where possible.
  • Add notes or sections for Linux/macOS users, including any differences in file paths, environment setup, or tool installation.
  • Where features are Windows-only (e.g., JavaScript UDFs), suggest alternative approaches or clarify the impact for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-deploy-with-bicep.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt, and commands) for all CLI examples, including npm installation and Azure CLI deployment. There are no Linux/macOS shell equivalents, and Windows path separators are used throughout, which may confuse or exclude Linux/macOS users.
Recommendations:
  • Provide equivalent Bash examples alongside PowerShell, using appropriate path separators (e.g., ./ instead of .\).
  • Explicitly mention that the commands work cross-platform and clarify any OS-specific differences.
  • Use platform-agnostic syntax in documentation when possible, or provide tabs/switches for Windows and Linux/macOS instructions.
  • Add a note about prerequisites or shell environments for each platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-data-explorer-managed-identity.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively describes how to configure managed identities and permissions using the Azure portal, which is a graphical tool most commonly used on Windows. There are no examples or instructions for performing these tasks using cross-platform command-line tools such as Azure CLI, PowerShell, or REST APIs. No Linux-specific or CLI-based workflows are mentioned, and the documentation assumes the user is interacting with the Azure portal UI, which may not be the preferred or available method for Linux users or those automating deployments.
Recommendations:
  • Add equivalent instructions for configuring managed identities and role assignments using the Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are given equal or higher prominence.
  • Provide REST API examples or references for users who need to automate these tasks in a platform-agnostic way.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using the CLI or API, not just the Azure portal.
  • Where screenshots are used, consider including CLI output or code snippets as alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows/Powershell bias. All command-line examples, including installation, project build, autoscale configuration, Azure login, and deployment, are shown exclusively using Powershell syntax and cmdlets (e.g., Connect-AzAccount, Set-AzContext, New-AzResourceGroupDeployment). There are no Bash, Linux shell, or cross-platform CLI equivalents provided, despite the fact that the Stream Analytics CI/CD tool is installed via npm and could be used on Linux/macOS. The documentation assumes a Windows environment for Azure authentication and deployment, omitting az CLI or Bash alternatives.
Recommendations:
  • Provide equivalent Bash/Linux/macOS shell commands for all steps, especially for npm installation, project build, and running the CI/CD tool.
  • Include Azure CLI (az) commands for authentication and deployment, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly state that the CI/CD tool and deployment steps can be performed on Linux/macOS, and highlight any platform-specific considerations.
  • Reorder or parallelize examples so that Linux/Bash and Windows/Powershell instructions are given equal prominence.
  • Add a section or callout for Linux/macOS users, clarifying any differences in file paths, environment setup, or command syntax.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/capture-event-hub-data-parquet.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-github-actions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively referencing PowerShell for command-line instructions, linking only to Windows-specific Azure CLI installation guides, and omitting any mention or examples for Linux or macOS environments. All screenshots and terminal instructions assume a Windows/PowerShell context, with no alternatives or parity for other platforms.
Recommendations:
  • Provide equivalent command-line instructions for Linux and macOS users, using Bash or sh syntax where appropriate.
  • Include links to Azure CLI installation guides for Linux and macOS alongside the Windows link.
  • Add screenshots or notes indicating how to open the terminal and run commands in VS Code on Linux/macOS.
  • Use platform-agnostic language (e.g., 'open a terminal' instead of 'open PowerShell') and clarify that the Azure CLI works across operating systems.
  • Where referencing PowerShell, also show the Bash equivalent, especially for commands that may differ in syntax or environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-data-explorer-managed-identity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively describes how to configure managed identities and outputs using the Azure portal, which is a GUI tool most commonly used on Windows. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), and no mention of how to perform these actions on Linux or cross-platform environments. The instructions and screenshots are tailored to the Azure portal interface, which may not be the primary tool for Linux users or those who prefer automation.
Recommendations:
  • Add equivalent instructions for configuring managed identities and outputs using the Azure CLI, which is cross-platform and widely used on Linux.
  • Provide Bash and/or PowerShell command examples for each step, ensuring parity between Windows and Linux environments.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but highlight and link to CLI-based alternatives for automation and scripting.
  • Include a section or note about using Infrastructure as Code (e.g., ARM templates, Bicep, Terraform) to configure these resources, which is platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-deploy-with-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt) for all command-line examples, and does not provide equivalent Bash/Linux commands or path formats. There is no mention of Linux or cross-platform usage, and the instructions implicitly assume a Windows environment.
Recommendations:
  • Provide Bash/Linux equivalents for all command-line examples, including path separators (e.g., ./ instead of .\).
  • Explicitly mention that the tools and commands work on Linux/macOS as well as Windows, if applicable.
  • Show both PowerShell and Bash command blocks side-by-side or in tabs to ensure parity.
  • Avoid using Windows-specific path formats in generic instructions.
  • Add a note about any platform-specific prerequisites or differences, if they exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation exclusively references Visual Studio and its tools for local debugging of Azure Stream Analytics queries, which are primarily available on Windows. There are no mentions of Linux-compatible tools, alternative editors, or cross-platform workflows. All instructions and screenshots assume the use of Visual Studio, and there are no examples or guidance for users on Linux or macOS.
Recommendations:
  • Include information about cross-platform alternatives to Visual Studio, such as Visual Studio Code with relevant extensions, or command-line tools that can be used on Linux.
  • Provide explicit instructions or links for setting up and debugging Azure Stream Analytics queries on Linux and macOS.
  • Add examples and screenshots for Linux environments, or clarify if local debugging is only supported on Windows.
  • If local debugging is not supported on Linux, state this limitation clearly and suggest possible workarounds or cloud-based alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-cosmos-db-output.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page lists Windows-centric tools and workflows (PowerShell, Visual Studio) before cross-platform or Linux-friendly alternatives (Azure CLI, Visual Studio Code). PowerShell and Visual Studio are highlighted as primary options, which may suggest a Windows-first approach, even though Azure CLI and VS Code are available cross-platform. There are no explicit Linux examples or mentions of Linux-specific workflows.
Recommendations:
  • List cross-platform tools (Azure CLI, Visual Studio Code) before Windows-specific tools (PowerShell, Visual Studio) in the 'Next steps' section.
  • Explicitly mention that Azure CLI and Visual Studio Code are available on Linux and macOS, and provide links or notes for Linux users.
  • Add Linux-specific examples or notes where relevant, especially for command-line operations.
  • Balance the documentation by ensuring that Windows-only tools are not presented as the default or primary workflow.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-functions-output.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cosmos-db-managed-identity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell commands for role assignment, with no mention of Azure CLI or REST API alternatives that are cross-platform and commonly used on Linux/macOS. The instructions explicitly state that the required RBAC operation must be performed via Azure PowerShell, and no Linux-friendly or platform-neutral options are presented.
Recommendations:
  • Provide equivalent Azure CLI commands for assigning the Cosmos DB role, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API or ARM template examples for role assignment to support automation and platform neutrality.
  • Explicitly state that the PowerShell example is one option, and link to documentation for other methods (CLI, REST, Portal) if available.
  • Consider rephrasing statements that imply PowerShell is the only way, or clarify if there are technical limitations that prevent using other tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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 Windows-specific commands (e.g., Connect-AzAccount, New-AzResourceGroupDeployment). There are no examples or instructions for Linux or macOS users, such as using Bash, Azure CLI equivalents, or cross-platform shell commands. The documentation assumes a Windows environment throughout, both in deployment and configuration steps.
Recommendations:
  • Provide equivalent Bash or Azure CLI examples for all PowerShell commands, especially for deployment and Azure authentication steps.
  • Explicitly mention cross-platform compatibility of the Stream Analytics CI/CD tool and clarify any OS-specific requirements.
  • Add a section or callouts for Linux/macOS users, including how to install and use the tool in those environments.
  • When listing commands, present Bash/Azure CLI and PowerShell examples side by side or in tabs, rather than only PowerShell.
  • Avoid using Windows file path conventions (e.g., .\Deploy\file.json) exclusively; show POSIX-style paths as well.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-github-actions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by instructing users to run Azure CLI commands specifically in PowerShell, linking only to Windows installation instructions for the Azure CLI, and providing screenshots and terminal instructions that assume a Windows environment. There are no examples or guidance for Linux or macOS users, nor are alternative shell environments mentioned.
Recommendations:
  • Provide instructions and screenshots for running Azure CLI commands in cross-platform terminals (e.g., Bash, Terminal, or integrated VS Code terminal on Linux/macOS).
  • Include links to Azure CLI installation guides for Linux and macOS, not just Windows.
  • Avoid specifying 'PowerShell' unless it is required; use 'terminal' or 'command line' to be inclusive.
  • Add explicit notes or sections for Linux/macOS users, including any OS-specific steps or differences.
  • Ensure that all command examples are cross-platform or provide alternatives where necessary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-tools.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias. All command-line examples are shown using PowerShell syntax, and there are no bash or Linux shell equivalents. Windows-specific tools and patterns (such as Connect-AzAccount, Set-AzContext, and New-AzResourceGroupDeployment) are used exclusively, and there is no mention of how to perform these tasks on Linux or macOS. The only explicit OS note is a warning that JavaScript UDFs only work on Windows, but no guidance is given for Linux users. This may make it difficult for users on non-Windows platforms to follow the documentation or understand how to adapt the instructions.
Recommendations:
  • Provide all CLI examples in both PowerShell and bash (Linux/macOS) syntax, or use a neutral shell syntax where possible.
  • Include instructions for installing and using the Azure CLI (az) as an alternative to Azure PowerShell, especially for deployment steps.
  • Explicitly mention OS compatibility for all commands and features, and provide alternatives or workarounds for Linux/macOS users.
  • Add a section or callouts for Linux/macOS users, highlighting any differences or limitations.
  • Avoid using Windows-specific path separators (\) in examples, or show both Windows and Linux/macOS path formats.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/includes/event-generator-app.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation page demonstrates a bias toward Windows by providing only Windows-specific instructions and examples for running the TelcoGenerator application. It references a Windows executable (.exe), uses Windows command prompt syntax, and does not mention or provide alternatives for Linux or macOS users. There are no instructions for running the event generator on non-Windows platforms, nor are there references to cross-platform tools or patterns.
Recommendations:
  • Provide instructions for running the TelcoGenerator application on Linux and macOS, such as using Mono or a cross-platform .NET runtime if available.
  • Include Linux/macOS command-line examples (e.g., using ./telcodatagen.exe with mono, or a native binary if available).
  • Mention any prerequisites or limitations for non-Windows users (e.g., needing to install Mono or .NET Core).
  • If the event generator is Windows-only, explicitly state this and suggest alternative ways for Linux/macOS users to generate and send sample data (such as using a Python script or Azure CLI).
  • Ensure that screenshots and UI instructions are labeled as Windows-specific if they differ on other platforms, or provide parallel guidance for other OSes where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/blob-output-managed-identity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-output.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing only PowerShell examples for Azure CLI commands, referencing Windows file paths (e.g., C:\Users\Downloads\...), and instructing users to use PowerShell to set up and run Azure CLI. There are no Linux/macOS shell examples, and instructions for copying file paths or interacting with the filesystem are written from a Windows perspective. This may hinder Linux or macOS users attempting to follow the guide.
Recommendations:
  • Provide parallel command-line examples using Bash (sh) syntax for Linux/macOS alongside PowerShell examples.
  • Use platform-agnostic file path placeholders (e.g., <path/to/certificate.pem>) or show both Windows and Unix-style paths in examples.
  • Clarify that Azure CLI can be used from any OS and provide links or notes for Linux/macOS installation and usage.
  • Include instructions for copying file paths or locating files on Linux/macOS systems.
  • Avoid language such as 'right-click and copy the path' which is specific to Windows Explorer; instead, offer cross-platform alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram-vs-code.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/confluent-kafka-input.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias in the section on uploading certificates to Azure Key Vault. All command-line examples are shown using PowerShell syntax and Windows-style file paths (e.g., C:\Users\Downloads\...), with no equivalent Linux/macOS examples or mention of cross-platform compatibility. The guidance assumes the user is running Azure CLI from PowerShell, and instructions such as 'right-click and copy the path' are Windows-centric. There is no mention of how to perform these steps on Linux or macOS, nor are there examples using Unix-style paths or shells.
Recommendations:
  • Provide Azure CLI command examples using both PowerShell (Windows) and Bash (Linux/macOS) syntax.
  • Include file path examples for both Windows (C:\...) and Linux/macOS (/home/user/...).
  • Clarify that Azure CLI is cross-platform and can be used from any shell, not just PowerShell.
  • Replace or supplement 'right-click and copy the path' with platform-agnostic instructions.
  • Explicitly mention any platform-specific requirements or differences, if any, for Linux/macOS users.
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/feature-comparison.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias by emphasizing Visual Studio (a Windows-only tool) in both the main and commented-out tables, and by providing a feature (JavaScript UDF and UDA) that is 'Windows only' in Visual Studio Code without explanation or Linux alternatives. There are no Linux-specific examples or guidance, and Windows tools are mentioned explicitly and sometimes exclusively.
Recommendations:
  • Provide explicit Linux and Mac instructions or notes where features are Windows-only (e.g., for JavaScript UDF/UDA), and suggest workarounds or alternatives for non-Windows users.
  • Balance tool coverage by including more information about cross-platform tools (such as Visual Studio Code) and de-emphasizing Windows-only tools unless necessary.
  • Add Linux/macOS-specific examples or troubleshooting tips where relevant, especially for features that are not supported on those platforms.
  • Clarify in the documentation why certain features are Windows-only and, if possible, provide a roadmap or links to feature requests for Linux/macOS support.
  • Consider reordering or rephrasing content so that cross-platform tools and features are mentioned before or alongside Windows-only tools, to avoid the perception of Windows as the default or preferred platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/input-validation.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/geo-redundancy.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page references PowerShell specifically in the 'Next steps' section, suggesting Windows-centric tooling for monitoring and managing Azure Stream Analytics jobs. There are no examples or mentions of Linux or cross-platform alternatives such as Azure CLI or Bash scripts. This may lead Linux users to feel unsupported or unaware of equivalent workflows.
Recommendations:
  • Include Azure CLI examples alongside or instead of PowerShell for managing Stream Analytics jobs, as Azure CLI is cross-platform.
  • Explicitly mention that management tasks can be performed from Linux, macOS, or Windows, and provide links to relevant documentation.
  • Balance references to Windows tools with Linux-friendly alternatives in 'Next steps' and throughout the documentation.
  • If PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide Bash equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/job-config-json.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exhibits a Windows bias in the section on uploading certificates to Azure Key Vault. All Azure CLI usage examples are shown in PowerShell syntax, with explicit references to using PowerShell and Windows file paths (e.g., C:\Users\Downloads\certificatefile.pem). There are no equivalent examples or guidance for Linux/macOS users, and the instructions assume a Windows environment by default.
Recommendations:
  • Provide Azure CLI command examples using Bash syntax and Linux/macOS file paths (e.g., /home/user/certificatefile.pem) alongside PowerShell/Windows examples.
  • Remove or rephrase statements like 'Make sure you have Azure CLI configured locally with PowerShell' to be platform-neutral, or add 'or Bash' to acknowledge cross-platform usage.
  • Include a note or section explicitly stating that Azure CLI works on Windows, Linux, and macOS, and provide links to platform-specific installation guides.
  • Where file paths are referenced, show both Windows and Linux/macOS path formats.
  • Consider including screenshots or terminal output from Linux/macOS environments, not just Windows.