Azure Functions
385
Total Pages
248
Linux-Friendly Pages
137
Pages with Bias
35.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1023 issues found
Showing 1001-1023 of 1023 flagged pages
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely cross-platform and avoids explicit Windows or PowerShell bias in its main instructions. However, in the Troubleshooting section, Windows-specific advice is given ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') before any mention of Linux or macOS environments, and there are no Linux/macOS-specific troubleshooting tips. There are no PowerShell-specific commands or Windows-only tools mentioned, but the troubleshooting guidance subtly prioritizes Windows scenarios.
Recommendations
- Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell configuration, or dependencies on those platforms.
- When mentioning Windows-specific advice, provide equivalent guidance for Linux/macOS or clarify that the advice is only relevant to Windows users.
- Explicitly state that the instructions are cross-platform and that all steps apply equally to Windows, Linux, and macOS unless otherwise noted.
- Consider including a table or section that lists any platform-specific considerations for all supported OSes.
Create Pull Request
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-orchestration-versioning.md
.../durable/durable-functions-orchestration-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples, tooling, or explicit mention of Windows-specific patterns. However, all code samples are in C# (a language most commonly associated with Windows/.NET development), and there are no examples or instructions for Linux-based environments, such as Bash shell commands, Linux file paths, or deployment instructions for non-Windows platforms. There is also no mention of cross-platform considerations or parity for Linux users.
Recommendations
- Add examples or notes for Linux/macOS users, such as how to edit host.json, deploy Azure Functions, or manage Durable Functions on Linux.
- Include at least one code sample in a language commonly used on Linux (e.g., Python, JavaScript/TypeScript) if supported by Durable Functions.
- Mention any platform-specific considerations, such as file path differences or deployment nuances between Windows and Linux.
- Clarify that the instructions and examples are applicable to both Windows and Linux environments, or specify any limitations.
- If using .NET isolated model is required, note its cross-platform support and provide guidance for Linux users (e.g., .NET SDK installation on Linux).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform, focusing on Visual Studio Code and Azure Functions, which are available on both Windows and Linux. However, there is a subtle Windows-first bias in the troubleshooting section, where a specific issue and solution for Windows users (regarding WSL Bash as the default terminal) is mentioned before any Linux-specific troubleshooting. There are no explicit PowerShell-heavy examples, exclusive use of Windows tools, or missing Linux examples, but the only OS-specific troubleshooting tip is for Windows.
Recommendations
- Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell environments, or dependencies on those platforms.
- When mentioning Windows-specific issues (e.g., WSL Bash), provide equivalent guidance for Linux/macOS users, or clarify that the step is only relevant for Windows.
- Explicitly state that all steps work on Windows, Linux, and macOS, and highlight any platform-specific differences where applicable.
- Consider including a table or section summarizing any known OS-specific behaviors or requirements for full parity.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focuses on Visual Studio Code, which is available on Windows, Linux, and macOS. However, there is a subtle Windows bias in the troubleshooting section, where a specific troubleshooting step for Windows users is mentioned before any Linux-specific guidance, and there is no equivalent Linux troubleshooting advice. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, but the mention of WSL Bash as a potential issue for Windows users is the only OS-specific guidance given.
Recommendations
- Add Linux-specific troubleshooting tips, such as common issues with permissions, shell environments, or dependencies on Linux.
- Balance OS-specific troubleshooting by including macOS and Linux notes where relevant, not just Windows.
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS, and provide links to platform-specific setup guides if available.
- If mentioning WSL Bash as a potential issue, also mention common shell or terminal issues that may occur on Linux or macOS.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-orchestration-versioning.md
.../durable/durable-functions-orchestration-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not display overt Windows bias in terms of command-line examples, tooling, or explicit mention of Windows-specific patterns. However, it is missing any platform-specific operational examples (such as deployment, configuration, or troubleshooting steps) for either Windows or Linux. All code samples are in C# and focus on Azure Functions' .NET isolated worker model, which is cross-platform, but there are no examples or notes addressing Linux-specific scenarios, nor any mention of Linux shell commands, deployment scripts, or environment differences. This absence could be considered a subtle bias by omission, as it does not acknowledge or assist Linux users with platform-specific guidance.
Recommendations
- Add explicit notes or examples for both Windows and Linux environments where operational steps are relevant (e.g., how to edit host.json, deploy, or manage worker processes on each OS).
- If any command-line or scripting is referenced in future updates, provide both PowerShell (Windows) and Bash (Linux) equivalents.
- Mention any OS-specific considerations for Durable Functions (such as file system paths, environment variable differences, or deployment nuances) where applicable.
- Clarify in the prerequisites or troubleshooting sections that the .NET isolated worker model and Durable Functions are supported on both Windows and Linux, and link to relevant cross-platform deployment documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md
...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias in terms of command-line examples or tool references (e.g., no PowerShell or Windows-only tools are shown). However, there is a lack of parity for Linux users: there are no examples or instructions for running or configuring Durable Task Scheduler on Linux, nor is there mention of Linux-specific considerations or cross-platform command-line usage. The documentation focuses exclusively on SDK usage (C#, Java, JavaScript, Python) and does not address OS-level setup or differences, which may implicitly bias the content toward users already familiar with Windows or .NET environments.
Recommendations
- Add explicit instructions or notes about running Durable Task Scheduler on Linux, including any prerequisites or differences in setup compared to Windows.
- Include cross-platform command-line examples (e.g., Bash, CLI) where relevant, especially for setup or deployment steps.
- Mention any Linux-specific considerations, such as environment variables, file paths, or service management.
- Clarify that the SDKs and orchestration features are cross-platform (if true), and provide guidance for Linux/macOS users where appropriate.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md
...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias in terms of using Windows-specific tools, PowerShell, or Windows-first patterns. However, it lacks any mention of Linux-specific instructions, tools, or examples. There are no shell/terminal commands, deployment instructions, or troubleshooting steps for either Windows or Linux, but the absence of any Linux context or parity checks (such as bash examples, Linux environment notes, or cross-platform deployment guidance) constitutes a subtle bias by omission.
Recommendations
- Add explicit notes or examples for Linux environments, such as how to configure Durable Task Scheduler on Linux hosts.
- If there are any OS-specific steps (e.g., environment variables, file paths, service management), provide both Windows and Linux variants.
- Include bash or shell command equivalents where appropriate, especially if PowerShell or Windows CLI examples are ever added.
- Clarify that the SDKs and features work identically on both Windows and Linux, or note any differences.
- Consider adding a section or callout on cross-platform support and any known issues or best practices for Linux users.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and avoids explicit Windows bias in its main instructions, focusing on Visual Studio Code and Azure Functions tooling, which are available on all major platforms. However, in the Troubleshooting section, there is a Windows-specific note ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') that places Windows considerations before Linux/WSL ones and does not mention equivalent issues or solutions for Linux or macOS users. There are no PowerShell-specific commands, Windows-only tools, or missing Linux/macOS examples, but the troubleshooting advice is Windows-centric.
Recommendations
- In the Troubleshooting section, provide equivalent troubleshooting steps for Linux and macOS users, such as checking the default terminal shell or addressing common issues specific to those platforms.
- When mentioning Windows-specific advice, also mention if similar issues can occur on Linux/macOS, or clarify that the advice is only relevant for Windows users.
- Consider adding a note at the start of the troubleshooting table indicating that solutions are applicable to all platforms unless otherwise specified, and explicitly call out platform-specific steps.
- Review included files (INCLUDEs) to ensure they do not introduce additional Windows bias, such as only referencing Windows paths or commands.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md
...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, but it does show a bias by omission: there are no Linux- or Unix-specific instructions, shell commands, or references. The only OS-specific pivot is 'powershell', which is present but contains only a generic limitations include, not actual PowerShell commands. No Windows tools, file paths, or patterns are mentioned, but Linux/Unix parity is not addressed, and there are no bash or shell examples. The documentation focuses on SDKs (C#, Java, JavaScript, Python), but the Python SDK is noted as unsupported for this feature.
Recommendations
- If any OS-specific setup or orchestration management is required (such as CLI commands, environment variables, or deployment scripts), provide both Windows (PowerShell/CMD) and Linux (bash/sh) examples.
- If the 'powershell' pivot is included, consider adding a corresponding 'bash' or 'shell' pivot for Linux users, even if only to state limitations or provide parity.
- Explicitly mention that the SDKs and features are cross-platform, and clarify any OS-specific requirements or differences.
- If there are no OS-specific steps, state this clearly to reassure Linux users that the instructions are applicable to their environment.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focuses on Visual Studio Code, which is available on Windows, macOS, and Linux. However, there is a subtle Windows bias in the troubleshooting section, where a specific issue and solution are called out for Windows users ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') without mentioning equivalent Linux or macOS troubleshooting steps. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, but the only OS-specific troubleshooting tip is for Windows, indicating a 'windows_first' bias.
Recommendations
- Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell configuration, or dependencies on those platforms.
- Where OS-specific guidance is given (such as the WSL Bash note), provide parallel advice for Linux and macOS users, or clarify that the guidance is only relevant to Windows.
- Explicitly state that all steps are applicable to Windows, Linux, and macOS unless otherwise noted, to reinforce cross-platform parity.
- If possible, include a table or section summarizing any platform-specific considerations for all supported operating systems.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md
...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, but it does include a 'powershell' pivot without a corresponding Linux shell (e.g., Bash) or CLI example. There are no explicit Windows tools or patterns, but the absence of Linux/Unix shell examples or references creates an implicit bias by omission.
Recommendations
- If a 'powershell' pivot is included, add a corresponding 'bash' or 'shell' pivot with equivalent Linux/Unix command-line examples.
- Ensure that any CLI or scripting examples are provided for both Windows and Linux environments, or clarify when examples are OS-agnostic.
- Review the documentation for any implicit assumptions about the user's operating system and explicitly mention cross-platform support where applicable.
- If the feature is not available or behaves differently on Linux, state this clearly in the documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focuses on Visual Studio Code, which is available on Windows, macOS, and Linux. However, there is a subtle Windows bias in the Troubleshooting section, where a Windows-specific issue (default terminal shell set to WSL Bash) is mentioned before any Linux/macOS-specific troubleshooting. No explicit Linux or macOS examples or troubleshooting tips are provided, and no Linux-specific tools or shell commands are referenced. The rest of the guide avoids platform-specific instructions, but the troubleshooting section assumes a Windows-first perspective.
Recommendations
- Add troubleshooting tips relevant to Linux and macOS users, such as common shell or permission issues.
- When mentioning Windows-specific issues (e.g., WSL Bash), also mention potential equivalents or common issues on Linux/macOS.
- Explicitly state that the instructions apply to all supported platforms, and provide clarifications if any steps differ on Linux or macOS.
- Where possible, include screenshots or terminal output from both Windows and Linux/macOS environments to reinforce parity.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely cross-platform and avoids explicit Windows or PowerShell bias in its main instructions, as it focuses on Visual Studio Code and the Azure Functions extension. However, in the Troubleshooting section, there is a Windows-first bias: the only OS-specific advice is for Windows users regarding the default terminal shell, with no equivalent troubleshooting guidance for Linux or macOS users. There are no PowerShell-specific commands, Windows-only tools, or missing Linux examples, but the troubleshooting advice implicitly prioritizes Windows scenarios.
Recommendations
- Add troubleshooting notes for Linux and macOS users, such as common issues with permissions, shell configuration, or dependencies on those platforms.
- Where OS-specific advice is given (e.g., about the default terminal shell), provide equivalent guidance for Linux (e.g., bash/zsh issues) and macOS users.
- Explicitly state that the instructions apply to all supported platforms, and clarify any steps that differ by OS.
- Consider including a table or section listing any known OS-specific issues or differences in workflow.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-java-gradle.md
.../azure-functions/functions-create-first-java-gradle.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation specifies 'os = windows' as the default runtime in the Gradle configuration, without mentioning Linux or cross-platform alternatives. This may lead users to assume Windows is the primary or only supported OS, despite Java and Azure Functions supporting Linux. No PowerShell or Windows-specific command-line tools are used, and all shell commands are cross-platform (bash/curl/gradle). However, the lack of explicit Linux parity in the runtime configuration is a subtle Windows-first bias.
Recommendations
- Explicitly mention that both Windows and Linux are supported as runtime OS options in the Gradle configuration.
- Show how to set 'os = linux' in the azurefunctions.runtime block, or provide a table comparing both options.
- Add a note clarifying that the instructions and commands work on both Windows and Linux, and that the default 'os = windows' can be changed as needed.
- If there are any platform-specific considerations (e.g., Java 21 only on Linux), highlight them in context and provide guidance for both platforms.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-code-constraints.md
...unctions/durable/durable-functions-code-constraints.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, JavaScript, Python, PowerShell, and Java. While PowerShell is included as a first-class language, there is no explicit Windows bias in terms of tools, shell commands, or patterns that would exclude or disadvantage Linux users. However, the inclusion of PowerShell as a primary example language (rather than, for example, Bash or a Linux-native shell) may be seen as a subtle bias toward Windows environments, since PowerShell is more commonly associated with Windows, even though it is now cross-platform.
Recommendations
- Clarify that PowerShell examples are cross-platform and not Windows-specific, or provide equivalent Bash/shell script examples where relevant.
- Explicitly mention that all code examples (including PowerShell) are intended to work on both Windows and Linux environments, or provide notes about any platform-specific considerations.
- If possible, add a Bash or Linux shell scripting tab for parity with PowerShell, especially if scripting is a common use case for Durable Functions.
- Continue to ensure that all tooling and patterns described are platform-agnostic, and avoid references to Windows-only tools or workflows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0001.md
...tions/errors-diagnostics/diagnostic-events/azfd0001.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of how to set the AzureWebJobsStorage app setting from Linux environments (e.g., using Azure CLI or bash), which could be helpful for non-Windows users.
Recommendations
- Add explicit examples for setting the AzureWebJobsStorage app setting using cross-platform tools such as Azure CLI or bash scripts.
- If relevant, mention both Windows (e.g., PowerShell, Azure Portal) and Linux (e.g., bash, Azure CLI) methods for configuring app settings.
- Ensure that links to further documentation include Linux-friendly instructions or note any platform-specific differences.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md
...tions/errors-diagnostics/diagnostic-events/azfd0011.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention Linux or cross-platform workflows. There are no Windows-specific tools or commands, but the lack of Linux (or general cross-platform) command-line examples or instructions may leave Linux users without clear guidance.
Recommendations
- Add explicit examples for setting the FUNCTIONS_WORKER_RUNTIME variable using both Windows (e.g., PowerShell, Azure CLI on Windows) and Linux (e.g., Bash, Azure CLI on Linux).
- Include notes or sections that clarify how to update application settings on different platforms, such as Linux, macOS, and Windows.
- Provide sample commands for editing local.settings.json using common cross-platform editors or command-line tools.
- Ensure parity in troubleshooting steps and instructions for both Windows and Linux environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-textcompletion-input.md
...ions/functions-bindings-openai-textcompletion-input.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, Java, JavaScript, TypeScript, PowerShell, and Python. While PowerShell is included as a first-class language alongside others, there is no evidence of exclusive Windows bias: there are no Windows-only tools, no Windows-first ordering, and no missing Linux equivalents. However, the inclusion of PowerShell as a primary example language (rather than, for example, Bash or shell scripting) may be seen as a mild bias towards Windows environments, since PowerShell is most commonly associated with Windows, even though it is now cross-platform.
Recommendations
- Consider adding Bash or shell scripting examples, especially in sections where PowerShell is used, to provide parity for Linux users.
- Explicitly note that PowerShell Core is cross-platform, or provide guidance for Linux/macOS users where PowerShell is referenced.
- Ensure that any references to tools, file paths, or environment variables are platform-agnostic or provide both Windows and Linux/macOS variants.
- If possible, include a section or note on how to use the binding in a Linux environment, or link to Linux-specific setup guides.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-input.md
...azure-functions/functions-bindings-web-pubsub-input.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code samples for C#, JavaScript, and Python, with explicit notes that PowerShell and Java samples are pending. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the Python examples assume a generic cross-platform environment but do not provide explicit Linux-specific instructions or terminal commands. There are no references to Windows-only tools or patterns, but the lack of Linux-specific guidance (such as bash commands or Linux environment notes) may leave Linux users without full parity.
Recommendations
- Add explicit Linux shell/terminal instructions where relevant, such as for creating folders or deploying functions.
- Include notes or examples for running and testing Azure Functions on Linux (e.g., using Azure Functions Core Tools in bash).
- Ensure parity in sample completeness for all supported languages, including PowerShell and Java, and clarify if any samples are Windows-only.
- If any steps differ between Windows and Linux (such as file paths or environment variable syntax), document both variants.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-kafka-trigger.md
...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, JavaScript, PowerShell, Python, and Java. While most examples are language-focused and cross-platform, the inclusion of PowerShell as a primary language (alongside Python and JavaScript) may indicate a slight Windows bias, as PowerShell is traditionally associated with Windows environments, although it is now cross-platform. However, there are no explicit Windows-only tools, Windows-first ordering, or missing Linux examples. No Windows-specific commands, paths, or tools are mentioned, and all code samples are language-agnostic or cross-platform.
Recommendations
- Clarify that PowerShell examples are intended to be cross-platform (PowerShell Core), not Windows PowerShell, to avoid confusion.
- Consider including bash or shell script examples for Linux users, especially if scripting is relevant for operational tasks.
- Explicitly state in the introduction or relevant sections that all examples are intended to work on both Windows and Linux, unless otherwise noted.
- If any operational steps (such as local development, deployment, or troubleshooting) are added in the future, ensure both Windows and Linux command-line instructions are provided.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-textcompletion-input.md
...ions/functions-bindings-openai-textcompletion-input.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, Java, JavaScript, TypeScript, PowerShell, and Python. While there is no overt Windows bias in the form of Windows-only tools or commands, the inclusion of PowerShell as a primary example language (with detailed configuration and code samples) can be seen as a subtle Windows bias, since PowerShell is most commonly associated with Windows environments. However, there are no missing Linux examples, and no Windows-specific tools or patterns are mentioned exclusively or prioritized before Linux equivalents.
Recommendations
- Clarify that PowerShell examples are cross-platform, as PowerShell Core runs on Linux and macOS as well as Windows.
- Consider adding Bash or shell script examples if relevant for parity with PowerShell, especially in sections where scripting is demonstrated.
- Explicitly mention that all code samples are platform-agnostic unless otherwise noted, to reassure Linux users.
- If any setup, deployment, or CLI instructions are added in the future, ensure both Windows (PowerShell/CMD) and Linux (Bash) equivalents are provided.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-input.md
...azure-functions/functions-bindings-web-pubsub-input.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias in terms of command-line examples, tools, or patterns. However, there is a lack of parity for PowerShell: while a placeholder for PowerShell examples is present, no actual PowerShell (or platform-specific) samples are provided. There are no references to Windows-only tools, nor are Windows-specific instructions or patterns prioritized over Linux equivalents. All code samples are cross-platform (C#, JavaScript, Python), and there is no mention of Windows-specific behaviors or requirements. However, the absence of any Linux- or bash-specific examples or notes, especially in sections where PowerShell is mentioned, may leave Linux users underserved.
Recommendations
- If PowerShell samples are to be included, ensure equivalent bash or shell script examples are also provided for Linux users.
- Explicitly state that all code samples are cross-platform unless otherwise noted.
- If any platform-specific setup or troubleshooting is required (e.g., for local development), provide both Windows and Linux instructions.
- When mentioning PowerShell, clarify its cross-platform availability or provide alternatives for Linux (such as bash).
- Consider adding a section or note on running these samples on Linux/macOS, including any necessary environment setup or differences.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-output.md
...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code examples for C# and JavaScript, but for Python and PowerShell, it states that complete samples are pending. There are no explicit Windows-specific tools, commands, or PowerShell-heavy content, nor is there a 'Windows-first' ordering. However, the lack of Linux-oriented or cross-platform examples (especially for Python, which is popular on Linux) indicates a bias by omission.
Recommendations
- Add complete Python and PowerShell code samples to achieve parity with C# and JavaScript.
- Ensure that any future troubleshooting or setup instructions include both Windows and Linux command-line examples (e.g., Bash and PowerShell).
- Explicitly mention cross-platform compatibility where relevant, and avoid assuming a Windows environment.
- If referencing configuration files or environment variables, provide examples for both Windows (e.g., %ENV_VAR%) and Linux/macOS (e.g., $ENV_VAR) syntax.