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 51-75 of 98 flagged pages
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell examples for Azure CLI commands, referencing Windows file paths (e.g., C:\Users\Downloads\...), 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.
Create Pull Request
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/includes/event-generator-app.md
...icles/stream-analytics/includes/event-generator-app.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-tools.md
...docs/blob/main/articles/stream-analytics/cicd-tools.md
High Priority
View Details →
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 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.
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 →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-autoscale.md
.../blob/main/articles/stream-analytics/cicd-autoscale.md
High Priority
View Details →
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 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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cosmos-db-managed-identity.md
...rticles/stream-analytics/cosmos-db-managed-identity.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-cosmos-db-output.md
...in/articles/stream-analytics/azure-cosmos-db-output.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/debug-locally-using-job-diagram.md
...es/stream-analytics/debug-locally-using-job-diagram.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/azure-data-explorer-managed-identity.md
...ream-analytics/azure-data-explorer-managed-identity.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/cicd-deploy-with-bicep.md
...in/articles/stream-analytics/cicd-deploy-with-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively uses PowerShell syntax (e.g., .\ paths, PowerShell prompt) for all command-line examples, 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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/kafka-output.md
...cs/blob/main/articles/stream-analytics/kafka-output.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/feature-comparison.md
...b/main/articles/stream-analytics/feature-comparison.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/stream-analytics/geo-redundancy.md
.../blob/main/articles/stream-analytics/geo-redundancy.md
High Priority
View Details →
Detected Bias Types
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.
Stream Analytics
Stream data from Azure Stream Analytics into confluent cloud kafka
...in/articles/stream-analytics/confluent-kafka-output.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides Azure CLI commands exclusively in PowerShell syntax and references Windows file paths and usage patterns (e.g., 'C:\Users\Downloads\isrgrootx1.pem', right-clicking to copy file path). There are no Linux/macOS shell examples, and the instructions assume a Windows environment for Azure CLI usage, which may create friction for Linux/macOS users.
Recommendations
- Include Azure CLI command examples using Bash syntax (e.g., $HOME/Downloads/isrgrootx1.pem) alongside PowerShell examples.
- Clarify that Azure CLI works cross-platform and provide guidance for Linux/macOS users on locating and referencing certificate files.
- Replace Windows-specific instructions like 'right-click to copy the path' with platform-agnostic alternatives, such as using the terminal to find file paths.
- Explicitly mention that the Azure CLI commands are valid on Linux/macOS and provide any necessary adjustments (e.g., path separators, shell syntax).
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation requires users to assign Cosmos DB RBAC permissions using Azure PowerShell (New-AzCosmosDBSqlRoleAssignment), with no mention of Azure CLI, REST API, or other cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-native tools.
Recommendations
- Add equivalent instructions and examples using Azure CLI (if supported) or REST API for role assignment.
- Explicitly mention platform requirements for PowerShell, and provide guidance for installing PowerShell Core on Linux/macOS if no alternatives exist.
- Where possible, link to cross-platform tooling documentation for Cosmos DB RBAC management.
Stream Analytics
Deploy Azure Stream Analytics jobs using Bicep files
...in/articles/stream-analytics/cicd-deploy-with-bicep.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides all command-line examples using PowerShell syntax (e.g., .\ paths, no Bash equivalents), and does not mention or show Linux/macOS shell commands or path formats. This may create friction for non-Windows users, especially when using Azure CLI and npm on Linux/macOS.
Recommendations
- Add Bash/zsh equivalents for all command-line examples, using appropriate path separators (e.g., ./DeployV2/{project-name}.JobTemplate.bicep).
- Explicitly mention that the Azure CLI and npm commands work cross-platform, and provide guidance for Linux/macOS users.
- Include a note or section clarifying any platform-specific differences (such as path formats) when running commands.
- Consider showing both Windows and Linux/macOS examples side-by-side where relevant.
Stream Analytics
Automate builds, tests, and deployments using CI/CD tools
...docs/blob/main/articles/stream-analytics/cicd-tools.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page consistently uses PowerShell syntax and Windows-style commands for all CLI examples, including npm installation, project build, local run, test case management, and Azure deployment. There are no bash, sh, or Linux/macOS terminal examples, and the use of PowerShell is assumed throughout. The deployment section relies exclusively on Azure PowerShell, with no mention of Azure CLI or ARM template deployment via bash. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
- Provide bash/sh examples alongside PowerShell for all CLI commands, especially for npm installation, project build, local run, and test case management.
- In the deployment section, include Azure CLI equivalents (e.g., az deployment group create) for ARM template deployment.
- Clarify that the npm package and CLI commands work cross-platform, and specify any OS-specific limitations (other than the noted JavaScript UDF Windows-only restriction).
- Explicitly mention prerequisites for Linux/macOS users, such as installing PowerShell Core if needed, or alternatives using native shells.
- Reorder examples so that cross-platform or OS-neutral instructions appear before Windows/PowerShell-specific ones.
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation for the event generator application (TelcoGenerator) provides instructions and examples only for running a Windows executable (.exe) via a Windows command prompt. There are no instructions or examples for running the event generator on Linux or macOS, nor is there mention of a cross-platform alternative or compatibility. This creates friction for non-Windows users who wish to follow the tutorial.
Recommendations
- Clarify whether TelcoGenerator is Windows-only. If so, explicitly state this early in the documentation.
- If a cross-platform or Linux-compatible event generator exists, provide instructions and examples for Linux/macOS users.
- If TelcoGenerator can run under Mono or Wine, provide guidance for Linux/macOS users on how to do so.
- Consider offering a simple script or open-source tool for generating sample data that works natively on Linux/macOS.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively provides PowerShell commands and patterns for installing, configuring, and deploying Stream Analytics autoscale settings via the CI/CD tool. There are no examples or guidance for Bash, Linux, or macOS users, despite the tool being installed via npm and Visual Studio Code being cross-platform. All command-line instructions and Azure CLI interactions use PowerShell syntax, which may not work natively on Linux/macOS terminals.
Recommendations
- Add equivalent Bash or shell command examples for Linux/macOS users, especially for npm installation and file path syntax.
- Provide Azure CLI alternatives to PowerShell-specific cmdlets (e.g., use 'az deployment group create' instead of 'New-AzResourceGroupDeployment').
- Clarify that the CI/CD tool and deployment steps are cross-platform and specify any OS-specific requirements or limitations.
- Include screenshots or terminal output from Linux/macOS environments to demonstrate parity.
Stream Analytics
Integrating with GitHub Actions
.../main/articles/stream-analytics/cicd-github-actions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows and PowerShell environments. It instructs users to run Azure CLI commands specifically in PowerShell, provides a link to install Azure CLI on Windows, and shows screenshots of PowerShell and Windows environments. There are no examples or instructions for running the same commands on Linux or macOS, nor are there references to Bash or cross-platform terminal usage.
Recommendations
- Clarify that Azure CLI can be run in any terminal (PowerShell, Bash, etc.) on Windows, Linux, and macOS.
- Provide installation instructions for Azure CLI on Linux and macOS alongside the Windows link.
- Include example commands and screenshots for Bash or other common Linux/macOS terminals.
- Avoid specifying 'Open PowerShell' unless a PowerShell-specific feature is required; use 'Open a terminal' or 'Open your command prompt/terminal' instead.
- Add a note that the workflow and commands are cross-platform unless there are genuine platform-specific limitations.
Stream Analytics
Stream data from confluent cloud Kafka with Azure Stream Analytics
...ain/articles/stream-analytics/confluent-kafka-input.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section describing how to upload a certificate to Azure Key Vault using Azure CLI. All command examples are shown in PowerShell syntax, and file path examples use Windows-style paths (e.g., C:\Users\Downloads\isrgrootx1.pem). There is no mention of Linux/macOS equivalents, such as Bash syntax or Unix-style file paths, nor any guidance for non-Windows users on how to perform these steps.
Recommendations
- Provide Azure CLI command examples in Bash syntax alongside PowerShell, especially for cross-platform tools like Azure CLI.
- Include file path examples using Unix-style paths (e.g., /home/user/isrgrootx1.pem) in addition to Windows paths.
- Explicitly state that Azure CLI is cross-platform and can be used on Linux/macOS, with links to installation instructions for those platforms.
- Add notes or sections for Linux/macOS users, clarifying any differences in command usage or environment setup.
Stream Analytics
Stream data from Azure Stream Analytics into Kafka
...cs/blob/main/articles/stream-analytics/kafka-output.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section describing how to upload certificates to Azure Key Vault using Azure CLI. All example commands are presented in PowerShell syntax, with file paths using Windows conventions (e.g., C:\Users\Downloads\certificatefile.pem), and instructions reference copying file paths in a Windows context. There are no equivalent examples for Linux/macOS users, such as Bash commands or POSIX-style file paths.
Recommendations
- Provide Azure CLI examples using Bash syntax and POSIX file paths (e.g., /home/user/certificatefile.pem) alongside PowerShell examples.
- Explicitly state that Azure CLI works on Linux/macOS and provide guidance for those platforms.
- Include notes or examples on how to obtain file paths on Linux/macOS.
- Avoid language that assumes a Windows environment (e.g., 'right-click and copy the path') or provide alternative instructions for other platforms.
Stream Analytics
Integrating with GitHub Actions
.../main/articles/stream-analytics/cicd-github-actions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a notable Windows bias. It instructs users to run Azure CLI commands specifically in PowerShell, links only to Windows installation instructions for Azure CLI, and provides screenshots and examples exclusively from Windows environments. There are no Linux/macOS equivalents or guidance, and the use of PowerShell is assumed throughout critical steps.
Recommendations
- Provide Azure CLI installation instructions for Linux and macOS alongside Windows.
- Clarify that Azure CLI commands can be run in any terminal (e.g., Bash, zsh, Terminal.app), not just PowerShell.
- Include screenshots or terminal examples from Linux/macOS environments.
- Avoid language that assumes Windows (e.g., 'Open PowerShell'), and instead use platform-neutral phrasing like 'Open your terminal'.
- Mention keyboard shortcuts for opening terminals in VS Code for macOS (e.g., Cmd+J) as well as Windows (Ctrl+J).
Stream Analytics
Stream data from confluent cloud Kafka with Azure Stream Analytics
...ain/articles/stream-analytics/confluent-kafka-input.md
Medium Priority
View Details →
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 Azure CLI usage examples are shown in PowerShell syntax, with explicit references to Windows file paths (e.g., C:\Users\Downloads\...), and guidance such as 'configured and installed locally with PowerShell.' There are no Linux/macOS shell examples, nor any mention of how to adapt the commands or file paths for those platforms. This may create friction for non-Windows users attempting to follow the guide.
Recommendations
- Provide Azure CLI examples using Bash syntax alongside PowerShell, including Linux/macOS file path formats (e.g., /home/user/Downloads/isrgrootx1.pem).
- Clarify that Azure CLI works cross-platform and can be used from Bash, zsh, etc., not just PowerShell.
- Remove or rephrase instructions that imply PowerShell is required (e.g., 'configured and installed locally with PowerShell').
- Add notes or sections for Linux/macOS users, highlighting any differences in command usage or environment setup.
Stream Analytics
Deploy Azure Stream Analytics jobs using Bicep files
...in/articles/stream-analytics/cicd-deploy-with-bicep.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively uses PowerShell syntax for all command-line examples, including npm installation and Azure CLI deployment commands. There are no Bash or Linux/macOS shell equivalents provided, and Windows-style path separators (\) are used in file paths. This creates friction for Linux/macOS users, who may need to adapt commands and paths to their environment.
Recommendations
- Provide Bash/Linux/macOS shell examples alongside PowerShell commands.
- Use cross-platform path separators (/) or clarify path conventions for different OSes.
- Explicitly mention that Azure CLI and npm commands work on Linux/macOS, and note any OS-specific differences.
- Add a section or note for Linux/macOS users highlighting any required adaptations.