Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 351-375 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-customize-devbox-azure-image-builder.md
...dev-box/how-to-customize-devbox-azure-image-builder.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All command-line examples use PowerShell, and instructions reference Windows-specific tools and file paths (e.g., c:/temp). There are no examples or guidance for Linux or cross-platform users, despite Azure CLI being mentioned briefly. The image customization steps use Windows images and PowerShell scripts exclusively, with no mention of Linux equivalents or how to adapt the process for Linux environments.
Recommendations
- Provide parallel examples using Azure CLI and Bash for all PowerShell commands, ensuring Linux and macOS users can follow along.
- Include instructions for installing Azure CLI and required modules on Linux, not just PowerShell on Windows.
- Demonstrate how to create and customize Linux images with Azure VM Image Builder, including sample templates and scripts.
- Use cross-platform file paths (e.g., /tmp/mytemplate.txt) or clarify file path differences for Windows and Linux.
- When referencing tools like Chocolatey (Windows), also mention Linux package managers (e.g., apt, yum) for Linux image customization scenarios.
- Explicitly state which steps or features are Windows-only and provide alternatives or links for Linux users where possible.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/configure-monitoring.md
...main//articles/azure-functions/configure-monitoring.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates some Windows bias, primarily by providing PowerShell examples for configuration changes and mentioning PowerShell as a first-class scripting option. In the section on overriding monitoring configuration at runtime, both Azure CLI and PowerShell examples are given, but PowerShell is presented as a tab alongside Azure CLI, which may suggest parity but still prioritizes Windows tooling. There is also a note about app settings with periods not being supported on Linux in certain plans, but the workaround is to use host.json, which is not as convenient as app settings. No explicit Linux shell (bash) examples are provided, and the documentation does not mention Linux tools or patterns (e.g., exporting environment variables, editing files via bash, etc.), nor does it provide Linux-first or cross-platform guidance for scripting or automation.
Recommendations
- Provide bash or cross-platform shell examples alongside PowerShell and Azure CLI, especially for configuration tasks.
- Explicitly mention Linux support and any differences or caveats in configuration, not just as a note about unsupported features.
- Where PowerShell is shown, add equivalent bash commands for Linux/macOS users.
- Clarify when instructions or tools are Windows-specific and offer Linux alternatives.
- Consider reordering examples so that cross-platform or CLI-first approaches are presented before Windows/PowerShell-specific ones.
- Highlight any platform-specific limitations more prominently, and suggest best practices for Linux users (e.g., using host.json for overrides).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/create-first-function-cli-node.md
...cles/azure-functions/create-first-function-cli-node.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for Azure resource creation, providing Azure PowerShell examples alongside Azure CLI, and referencing the Az PowerShell module as a prerequisite. There is no mention of Linux-specific shell environments or guidance for non-Windows users, and PowerShell examples are given equal prominence to CLI examples, which can be confusing or less relevant for Linux/macOS users.
Recommendations
- Clearly indicate which commands are cross-platform (e.g., Azure CLI) and which are Windows-specific (e.g., Azure PowerShell), and recommend CLI as the default for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, clarifying that Azure CLI commands work natively in Bash and other Unix shells.
- Where PowerShell is mentioned, provide equivalent Bash or shell commands if any setup or scripting is required.
- In the prerequisites, clarify that PowerShell is optional and primarily for Windows users, and that Linux/macOS users can use Azure CLI.
- Consider reordering examples to present Azure CLI first, as it is cross-platform, and PowerShell second, or move PowerShell to an appendix or separate tab.
- Add troubleshooting or environment-specific notes for common Linux/macOS issues (e.g., file permissions, path separators) if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/configure-encrypt-at-rest-using-cmk.md
...azure-functions/configure-encrypt-at-rest-using-cmk.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by referencing Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and by providing a link to a Storage Explorer guide that defaults to Windows tabs. There are no examples or instructions for Linux-native tools (such as azcopy, Azure CLI, or standard shell commands) for these tasks. This may disadvantage Linux users or those working in headless/server environments.
Recommendations
- Provide equivalent instructions and examples for uploading files and generating SAS tokens using cross-platform CLI tools such as Azure CLI (az storage blob upload, az storage blob generate-sas) or azcopy.
- Avoid referencing GUI tools (like Storage Explorer) as the primary or sole method, or at least present CLI alternatives first or alongside.
- Ensure that links to further documentation include Linux/macOS tabs or instructions, not just Windows.
- Explicitly mention that all Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- If referencing Storage Explorer, clarify its availability on Linux and macOS, or provide a note about alternative tools for those platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/create-first-function-cli-java.md
...cles/azure-functions/create-first-function-cli-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas. The default configuration in the Maven-generated pom.xml is set to deploy to Windows, with Linux deployment mentioned only as an alternative. There is a lack of Linux-specific examples or guidance, and Windows is presented as the default or primary platform for hosting the function app. Additionally, the documentation references Windows-specific patterns (e.g., defaulting to Windows in deployment), and Linux users are required to manually alter configuration files to achieve parity.
Recommendations
- Present Linux and Windows options equally, both in configuration and in examples. For instance, show both 'runtime.os: windows' and 'runtime.os: linux' in the pom.xml example, or provide a clear side-by-side comparison.
- Include explicit Linux-focused instructions and examples, such as deployment to a Linux-based function app, and highlight any differences in behavior or requirements.
- Avoid language that positions Windows as the default or preferred option. Instead, use neutral phrasing or clarify that both platforms are supported equally.
- Where platform-specific commands or tools are shown (e.g., PowerShell, Cmd), ensure that Bash/Linux shell examples are given first or at least with equal prominence.
- Add troubleshooting or notes specific to Linux environments, such as file permissions, case sensitivity, or common issues encountered on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/bring-dependency-to-functions.md
...icles/azure-functions/bring-dependency-to-functions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the Java example where the ffmpeg path is hardcoded to use the Windows-style executable (ffmpeg.exe) and there is no mention of Linux equivalents or cross-platform considerations. Additionally, the Java example only references the Windows path and does not provide a Linux-compatible example or guidance. The Python sections are more Linux-oriented, especially in the file share mounting section, but the Java section lacks parity.
Recommendations
- In the Java example, provide both Windows and Linux examples for the ffmpeg path (e.g., ffmpeg.exe for Windows and ffmpeg for Linux), and explain how to detect or configure the correct path based on the environment.
- Explicitly mention cross-platform considerations in all code examples, such as file path separators and executable extensions.
- Add a note or example for Java on how to set executable permissions on Linux (e.g., using chmod), similar to the note provided in the Python section.
- Ensure that all references to tools (like ffmpeg) and file paths are platform-agnostic or provide both Windows and Linux variants.
- Where PowerShell or Windows-specific tools are mentioned (such as in the upload section), ensure Linux CLI alternatives are equally described and not listed after Windows tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/create-first-function-azure-developer-cli.md
...functions/create-first-function-azure-developer-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides cross-platform instructions, but there are several areas where Windows-specific tools, shells, or patterns are given prominence or appear before Linux equivalents. PowerShell is treated as a first-class language, and Windows command-line (Cmd) and PowerShell examples are often shown before or alongside bash, sometimes with more detail. Some instructions and prerequisites reference Windows-specific paths or tools, and in a few places, Windows-centric terminology is used (e.g., 'command prompt').
Recommendations
- Ensure that bash/Linux examples are always presented before or alongside Windows Cmd/PowerShell examples, not after.
- Where possible, use neutral terms like 'terminal' instead of 'command prompt', or clarify with 'terminal or command prompt (Linux/macOS/Windows)'.
- For PowerShell-specific instructions, ensure parity by providing bash/zsh/fish equivalents where appropriate, especially for scripting or environment variable manipulation.
- Review all code blocks and tabs to ensure Linux/macOS users are not required to infer steps from Windows examples (e.g., activating Python venv, environment variable setting).
- When referencing tools, clarify their cross-platform availability (e.g., Azurite, Azure Functions Core Tools) and provide installation links or instructions for Linux/macOS as well as Windows.
- Avoid assuming Windows directory structures (e.g., .venv/scripts/activate vs .venv/bin/activate) without explicit cross-platform notes.
- Consider adding a summary table or section at the start that clearly states all instructions are cross-platform, with explicit notes for any OS-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/dotnet-aspire-integration.md
.../articles/azure-functions/dotnet-aspire-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio (a primarily Windows tool) for setup and update instructions, and by providing step-by-step update instructions only for Visual Studio. There are no equivalent instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or CLI-only workflows). No Linux-specific considerations or examples are provided, and the documentation assumes a Windows-centric development environment.
Recommendations
- Add equivalent setup and update instructions for Linux and macOS users, including how to install and update Azure Functions tools using the .NET CLI or other cross-platform editors like VS Code.
- Include examples or notes for using cross-platform tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Mention any platform-specific requirements or differences, such as using the Azure Storage emulator or alternatives on Linux/macOS.
- Ensure that all code and configuration examples are platform-agnostic, or provide platform-specific notes where necessary.
- Explicitly state that the guidance applies to all supported platforms, and highlight any known limitations or differences for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/create-first-function-vs-code-other.md
...azure-functions/create-first-function-vs-code-other.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows File Naming
Summary
The documentation generally maintains good cross-platform parity, but there is a subtle Windows bias in the order and phrasing of some instructions. Windows-specific file naming conventions (e.g., 'handler.exe') are mentioned first or as the default, and Windows-specific commands (e.g., 'set' in cmd) are given in a dedicated section, while Linux/macOS equivalents are grouped together. In configuration steps, Windows is often referenced explicitly or first, and Linux is sometimes presented as an alternative rather than the default, despite the deployment target being Linux.
Recommendations
- When referencing executable names, mention the Linux version ('handler') first, with Windows ('handler.exe') as a note or alternative.
- In configuration instructions, avoid phrasing like 'on Windows, set it to handler.exe'—instead, use 'set to handler (or handler.exe on Windows)'.
- Present Linux/macOS instructions before Windows, especially since the deployment target is Linux.
- Where possible, use cross-platform command syntax or provide all platform variants together, not with Windows as a separate afterthought.
- Explicitly state that the primary deployment and runtime environment is Linux, and clarify that Windows-specific steps are only needed for local development on Windows.
- Ensure that screenshots and terminal outputs are balanced between platforms or are platform-neutral.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md
...able/durable-functions-isolated-create-first-csharp.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Visual Studio and Visual Studio Code workflows, both of which are most commonly associated with Windows environments. All step-by-step instructions, screenshots, and tool recommendations (e.g., Visual Studio, Azurite extension for VS Code, Azure Functions Core Tools) are tailored to Windows users. There are no explicit instructions or examples for Linux (or macOS) users, such as command-line alternatives, Linux-specific installation steps, or screenshots from non-Windows environments. The use of Visual Studio (not available on Linux) as a primary workflow further reinforces the Windows-centric approach.
Recommendations
- Add explicit instructions and examples for Linux users, including terminal/command-line steps for creating, running, and debugging Durable Functions apps.
- Include installation instructions for Azure Functions Core Tools and .NET SDK on Linux (and macOS), with appropriate package manager commands (e.g., apt, yum, brew).
- Provide screenshots or terminal output examples from Linux environments to demonstrate parity.
- Mention and demonstrate the use of cross-platform editors (such as VS Code) in a way that highlights their use on Linux and macOS, not just Windows.
- Clarify which steps are cross-platform and which are Windows-specific, and provide alternatives where necessary.
- If Visual Studio is referenced, note that it is Windows-only and suggest Visual Studio Code or command-line alternatives for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-add-openai-text-completion.md
...zure-functions/functions-add-openai-text-completion.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of Windows-centric tools and workflows, such as Visual Studio Code, Azurite, and the use of the F1 command palette and F5 debugging instructions. There is an assumption of a Windows-like environment, with no explicit mention of Linux or macOS alternatives for key steps (e.g., starting Azurite, running/debugging the function app, or managing environment variables). There are no terminal or shell command examples for Linux/macOS users, and no mention of platform-specific differences or considerations.
Recommendations
- Add explicit instructions and examples for Linux and macOS users, especially for steps involving Azurite, debugging, and environment variable management.
- Include terminal/bash command alternatives for starting Azurite and running/debugging the function app, not just VS Code F1/F5 instructions.
- Clarify any platform-specific requirements or differences (e.g., installation steps, file paths, permissions).
- Where possible, use cross-platform language and tools, or provide equivalent steps for each major OS.
- Consider adding a prerequisites section that lists supported operating systems and any OS-specific setup steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-roslyn-analyzer.md
...functions/durable/durable-functions-roslyn-analyzer.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page focuses on configuring the Roslyn Analyzer using Visual Studio and Visual Studio Code, both of which are primarily associated with Windows environments. The Visual Studio instructions are detailed and Windows-specific, and there is no mention of Linux-native editors or command-line configuration methods. There are no examples or guidance for Linux users or for using the analyzer outside of Microsoft IDEs.
Recommendations
- Include instructions for configuring the Roslyn Analyzer using .NET CLI commands (e.g., dotnet build, dotnet format) that work cross-platform.
- Provide examples for popular Linux editors such as JetBrains Rider or Vim/Emacs with OmniSharp.
- Clarify whether Visual Studio Code instructions apply equally on Linux and macOS, and mention any platform-specific caveats.
- Add a section on manual configuration via project files (e.g., editing .csproj) for users who do not use Visual Studio or Visual Studio Code.
- Reference any available command-line or CI/CD integration options for analyzer usage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/add-artifact-repository.md
...main//articles/devtest-labs/add-artifact-repository.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/PowerShell bias by providing only PowerShell-based automation examples and scripts for adding artifact repositories. While it mentions Azure CLI as an alternative, no CLI or Linux shell examples are actually provided. The step-by-step automation and scripting guidance is exclusively in PowerShell, which is most familiar to Windows users. There are no Bash, Linux shell, or cross-platform CLI script examples, and the documentation assumes use of PowerShell cmdlets for deployment and management tasks.
Recommendations
- Add equivalent Azure CLI (az) command examples for all automation and deployment steps, including adding artifact repositories and deploying ARM templates.
- Provide Bash or shell script examples for Linux/macOS users, especially for common automation scenarios.
- Explicitly mention cross-platform support and clarify when steps or scripts are Windows/PowerShell-specific.
- Reorder or parallelize sections so that CLI and PowerShell examples are presented together, rather than PowerShell first or exclusively.
- Include notes or links to Linux/macOS setup and usage guides where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/create-environment-service-fabric-cluster.md
...test-labs/create-environment-service-fabric-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by defaulting to Windows as the operating system for the cluster, providing certificate creation instructions exclusively via a PowerShell script (.ps1), and referencing Windows tools (PowerShell, Notepad) without Linux equivalents. There are no Linux-specific instructions or examples for certificate creation or cluster setup, and the process for Linux users is not addressed.
Recommendations
- Provide parallel instructions for Linux users, including how to generate the required certificate using common Linux tools (e.g., OpenSSL) and how to supply the certificate information.
- Include Linux shell (bash) command examples alongside PowerShell examples for all relevant steps.
- Explicitly mention that both Windows and Linux are supported, and clarify any differences in setup or requirements.
- Avoid defaulting to Windows in UI screenshots and instructions; instead, show both options or clarify that the default can be changed.
- Reference Linux text editors (e.g., nano, vim) or platform-agnostic methods for viewing output files, rather than only Notepad.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-sub-orchestrations.md
...ctions/durable/durable-functions-sub-orchestrations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation includes a prominent PowerShell-specific note and full PowerShell code examples alongside other languages, which may indicate a bias towards Windows-centric tooling and scripting environments. The PowerShell note appears before any mention of Linux or cross-platform considerations, and there is no explicit mention of Linux shell or Bash equivalents. The documentation does not provide Linux-specific guidance or highlight parity for Linux users, especially in the context of scripting and SDK support.
Recommendations
- Add explicit notes about Linux support and any differences or limitations for Linux users, especially regarding the PowerShell SDK and its cross-platform compatibility.
- Include Bash or shell script examples if relevant, or clarify that PowerShell examples are cross-platform (if true), or provide alternatives for Linux users.
- Ensure that introductory notes and tooling guidance mention cross-platform scenarios and not just Windows/PowerShell environments.
- Consider reordering notes and examples so that Windows/PowerShell-specific content does not always appear first or exclusively.
- If PowerShell is not cross-platform in this context, provide clear guidance or links for Linux users to achieve similar functionality.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-webjobs-sdk.md
...ure-functions/durable/durable-functions-webjobs-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by prioritizing Windows-specific tools (Visual Studio, Windows Classic Desktop templates), providing only PowerShell/NuGet Package Manager Console commands, and omitting Linux/macOS equivalents or instructions. There are no examples or guidance for developing, running, or deploying WebJobs/Durable Functions on Linux or with cross-platform tools beyond a brief mention of Visual Studio Code. The workflow assumes a Windows environment throughout.
Recommendations
- Provide equivalent instructions and screenshots for Linux/macOS users, including how to create and run .NET console apps using the dotnet CLI.
- Include bash/zsh shell commands for installing NuGet packages via the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell examples.
- Mention and document cross-platform editors (e.g., Visual Studio Code, JetBrains Rider) with relevant steps.
- Clarify how to run and debug WebJobs/Durable Functions on Linux/macOS, including any platform-specific requirements or limitations.
- Reference cross-platform storage emulators or provide guidance for connecting to Azure Storage directly when Azurite or Windows emulators are not available.
- Ensure deployment steps cover both Windows and Linux App Service environments, highlighting any differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/quickstart-mssql.md
...//articles/azure-functions/durable/quickstart-mssql.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas: it provides only PowerShell commands for setting up the local SQL Server instance (even though PowerShell is cross-platform, Bash is more common on Linux/macOS); it mentions SQL Server Express specifically as an option for 'your local Windows computer' before mentioning Docker as a cross-platform solution; and it omits explicit Bash or Linux-native command examples for local setup. The troubleshooting and validation steps also assume familiarity with Windows tooling and patterns, and there are no Linux/macOS-specific instructions or screenshots.
Recommendations
- Provide equivalent Bash shell commands for all PowerShell setup steps, especially for Docker-based SQL Server setup and validation.
- Explicitly mention and show how to install and use Docker and SQL Server on Linux and macOS, not just Windows.
- Avoid language like 'on your local Windows computer' when discussing cross-platform tools; instead, clarify when instructions apply to all platforms.
- Include screenshots or terminal output from Linux/macOS environments where appropriate.
- List Linux/macOS options first or alongside Windows options when describing local development environments.
- Add troubleshooting tips relevant to Linux/macOS users (e.g., file permissions, Docker group membership, path differences).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/deliver-proof-concept.md
...b/main//articles/devtest-labs/deliver-proof-concept.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the prerequisites and subscription guidance. Windows client operating systems and Windows-specific licensing/subscription models (MSDN, Visual Studio, Enterprise Dev/Test) are discussed in detail, with no equivalent mention of Linux client OS options or licensing. The documentation references Windows 10/8.1/7 specifically, and does not provide examples or guidance for Linux-based development/test environments. There are no Linux-specific tools, patterns, or scenarios discussed, and no Linux-focused examples are provided.
Recommendations
- Include explicit references to Linux-based development and test scenarios, such as using Ubuntu or other popular Linux distributions in DevTest Labs.
- Provide guidance on using Linux VM images from the Azure Marketplace, including any licensing or cost considerations.
- Mention Linux-compatible subscription options or clarify that standard Azure subscriptions support Linux workloads without additional licensing requirements.
- Add examples or case studies that feature Linux development/test environments alongside Windows examples.
- Reference Linux remote access methods (such as SSH) with equal prominence to Windows RDP, and provide links to relevant documentation.
- Ensure that any tooling or collaboration recommendations (e.g., Azure Repos, Teams) are presented as cross-platform, and mention Linux-friendly alternatives if appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/quickstart-java.md
...n//articles/azure-functions/durable/quickstart-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias. In the manual setup section, the Maven plugin configuration explicitly sets the runtime OS to 'windows', with no mention of Linux or cross-platform options. In the Maven command section, while Bash, PowerShell, and Cmd examples are provided, the order is Bash first (good), but the presence of PowerShell and Cmd may reinforce Windows-centric workflows. Visual Studio Code instructions are cross-platform, but screenshots and language may be more familiar to Windows users. There is no explicit Linux example for configuring the runtime or deploying to a Linux-based Azure Functions host.
Recommendations
- In the Maven plugin configuration, provide examples for both Windows and Linux OS settings (e.g., <os>windows</os> and <os>linux</os>), or document that omitting the <os> tag allows cross-platform deployment.
- Clarify in the prerequisites and setup sections that all steps are supported on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Where command-line examples are given, ensure parity by including Bash (Linux/macOS) first, and clearly indicate which commands apply to which platforms.
- If screenshots are included, consider providing examples from both Windows and Linux environments.
- Explicitly mention that Azure Functions can be hosted on both Windows and Linux, and provide guidance or links for deploying to Linux-based Azure Functions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/quickstart-python-vscode.md
...es/azure-functions/durable/quickstart-python-vscode.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. While it does provide activation commands for Linux, macOS, and Windows, the structure and order of presentation often prioritize Windows (e.g., Windows activation command is last, but the Azurite emulator and Visual Studio Code workflows are Windows-centric). The use of PowerShell syntax for Windows activation, the focus on Visual Studio Code (a tool more popular on Windows), and the exclusive mention of Azurite (with no mention of Linux-native storage emulators or CLI alternatives) reinforce this bias. There are no explicit Linux command-line examples outside of the virtual environment activation, and the documentation does not mention Linux-specific tools or troubleshooting.
Recommendations
- Present Linux and macOS instructions before or alongside Windows instructions, not after.
- Include CLI-based alternatives for tasks like starting Azurite, not just Visual Studio Code commands.
- Provide explicit Linux troubleshooting tips or links for common issues (e.g., permissions, dependency installation).
- Mention and link to Linux-native tools or workflows where possible (e.g., running Azurite from the command line, using other editors).
- Ensure that all code snippets and instructions are equally detailed for Linux, macOS, and Windows.
- Consider adding a section or callout for Linux users, highlighting any differences or additional steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/quickstart-netherite.md
...ticles/azure-functions/durable/quickstart-netherite.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation shows mild Windows bias, primarily in the order and specificity of tool recommendations and examples. Windows tools and patterns (such as the deprecated Azure Storage Emulator) are mentioned explicitly, and there is a lack of Linux-specific instructions or examples. The section on local storage emulation references Windows and Azurite, but does not clarify Linux usage. There are no explicit Linux shell or deployment examples, and the only CLI example uses a generic command prompt block (cmd), which may imply Windows. The 64-bit architecture section is labeled 'Windows only', but does not provide equivalent Linux validation steps.
Recommendations
- Provide explicit Linux/macOS instructions and examples alongside Windows, especially for local development, storage emulation, and deployment.
- When referencing tools like Azurite, clarify installation and usage steps for Linux/macOS users, not just Windows.
- Use neutral shell blocks (e.g., 'bash' or 'sh') for CLI commands, or provide both Windows (cmd/PowerShell) and Linux/macOS (bash) variants.
- In sections that are Windows-specific (such as configuring 64-bit architecture), provide equivalent guidance or confirmation steps for Linux users.
- Avoid referencing deprecated Windows-only tools (like Azure Storage Emulator) without also providing up-to-date, cross-platform alternatives.
- Review screenshots and portal instructions to ensure they are not Windows-centric, or provide Linux/macOS equivalents where UI or experience differs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-add-output-binding-storage-queue-vs.md
...tions/functions-add-output-binding-storage-queue-vs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows and Visual Studio users, with all instructions and UI references specific to Visual Studio on Windows. There are no examples or guidance for Linux users or those using cross-platform tools like VS Code or the Azure Functions Core Tools CLI. The use of PowerShell/NuGet Package Manager Console and Visual Studio-specific workflows further reinforces a Windows-centric approach, despite Azure Storage Explorer being cross-platform.
Recommendations
- Provide parallel instructions for Linux and macOS users, including how to perform equivalent tasks using VS Code or the Azure Functions Core Tools CLI.
- Include command-line examples for installing binding extensions using dotnet CLI (e.g., 'dotnet add package ...') rather than only NuGet Package Manager Console.
- Clarify which steps are Visual Studio-specific and offer alternatives for non-Windows environments.
- Add explicit sections or callouts for Linux/macOS users, especially for steps like downloading app settings, running, and publishing the function.
- Reference cross-platform tools and workflows earlier and more prominently, rather than focusing exclusively on Windows/Visual Studio.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/function-keys-how-to.md
...main//articles/azure-functions/function-keys-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing access keys, but the PowerShell examples are more detailed and prominent. PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. In some cases, PowerShell scripts are provided with detailed variable setup and REST API usage, while the CLI examples are simpler. Additionally, the documentation notes that the Azure CLI example is designed for Azure Cloud Shell (Bash) and must be modified for Windows, but does not provide a native Linux terminal/bash example outside of Cloud Shell. There is a subtle 'windows_first' bias in the prominence and detail of PowerShell content, and a lack of parity for Linux users who may want bash or scripting examples outside of Cloud Shell.
Recommendations
- Add explicit bash/Linux shell script examples for all CLI operations, not just Azure Cloud Shell, to ensure Linux users have clear, native instructions.
- Balance the level of detail between PowerShell and CLI/bash examples, ensuring both platforms have equally comprehensive guidance.
- Where PowerShell is used for REST API calls, provide equivalent curl or HTTPie examples for Linux/macOS users.
- Clarify in each example whether it is cross-platform, and if not, provide platform-specific alternatives.
- Consider including a table or section summarizing which tools are available and recommended for Windows, Linux, and macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-add-vm.md
...blob/main//articles/devtest-labs/devtest-lab-add-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by using a Windows 11 Pro image as the example for VM creation, without mentioning or showing a Linux-based alternative. The only explicit script-based workflow for copying existing VMs uses PowerShell, with no Linux shell or cross-platform CLI example. While the intro mentions Azure CLI and ARM templates, the step-by-step instructions and screenshots focus solely on the Azure portal and Windows-centric workflows.
Recommendations
- Include parallel examples using a popular Linux image (e.g., Ubuntu) when demonstrating VM creation steps, and note any differences in settings or options.
- When referencing scripts for copying VMs, provide both PowerShell and Bash/Azure CLI examples, or clarify cross-platform alternatives.
- Balance screenshots and walkthroughs to show both Windows and Linux VM creation scenarios.
- Explicitly mention that the process supports both Windows and Linux images, and link to documentation or quickstarts for Linux VMs.
- If artifacts or advanced settings differ for Linux VMs, highlight those differences or provide links to Linux-specific guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md
...ask-scheduler/quickstart-portable-durable-task-sdks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the Python quickstart where Windows virtual environment activation commands are presented before Linux equivalents, and in the presence of a dedicated PowerShell pivot (even though the main quickstart content is for C#, Python, and Java). Docker Desktop is referenced as the recommended Docker installation, which is a Windows/Mac-specific tool, rather than mentioning Linux-native Docker. There are no Linux-specific tools or shell patterns highlighted, and Windows command patterns are sometimes shown first.
Recommendations
- In all code blocks or instructions that have OS-specific steps (such as activating Python virtual environments), present Linux and Windows instructions with equal prominence, and alternate which is shown first or present them side-by-side.
- Where Docker is required, mention both Docker Desktop (for Windows/Mac) and native Docker Engine (for Linux), and provide links to Linux installation instructions.
- If a PowerShell pivot is included, ensure there is parity with Bash or shell scripts for Linux users, or clarify that the PowerShell pivot is optional and not required for the main flow.
- Review all example paths and commands to ensure they are cross-platform (e.g., use forward slashes or explain path differences).
- Explicitly state that all instructions are supported on both Windows and Linux, and provide troubleshooting tips for common Linux issues (such as Docker permissions or executable flags).