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 476-500 of 1023 flagged pages
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-function-bicep.md
...ure-functions/functions-create-first-function-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for deploying Bicep files, but the inclusion of Azure PowerShell (which is primarily a Windows-centric tool) alongside Azure CLI (which is cross-platform) introduces a Windows bias. PowerShell examples are given equal prominence to CLI, and the documentation refers to 'Azure PowerShell' as a primary deployment method, which may not be as relevant for Linux users. There are no Linux-specific shell (bash) examples or explicit mention of Linux environments, and PowerShell is presented as a first-class option rather than as an alternative for Windows users.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows.
- Add bash/zsh shell examples for common Linux workflows, especially for validation and cleanup steps.
- If PowerShell is included, clarify its cross-platform availability but note its prevalence on Windows.
- Consider reordering sections to present Azure CLI (or bash) before PowerShell, or group PowerShell as a Windows-specific alternative.
- Explicitly mention Linux/macOS compatibility in the prerequisites and throughout the instructions.
Create Pull Request
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-3-version-4.md
...rticles/azure-functions/migrate-version-3-version-4.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell script for identifying function apps to migrate, referencing Azure PowerShell as the primary tool for this task, and omitting equivalent Bash, Azure CLI, or Linux-native instructions. The initial migration steps and tooling recommendations (e.g., Visual Studio, PowerShell) are presented from a Windows-centric perspective, with no parity for Linux or cross-platform users in the core discovery and migration workflow.
Recommendations
- Provide equivalent Azure CLI and/or Bash script examples alongside the PowerShell script for identifying function apps to migrate, ensuring Linux and macOS users have clear guidance.
- When referencing Azure PowerShell, also mention Azure CLI as an alternative, and provide links or examples for both.
- Avoid language such as 'use the following PowerShell script' without offering a cross-platform alternative.
- In sections discussing publishing or migration tooling (e.g., Visual Studio), mention and provide instructions for cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
- Audit all code snippets and workflow steps to ensure Linux users are not required to adapt Windows-specific instructions on their own.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-premium-plan.md
...ain/articles/azure-functions/functions-premium-plan.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI throughout, but there are no explicit Linux shell (bash) or scripting examples. Migration between plans is only supported on Windows, with Linux migration explicitly unsupported. In several places, Windows is mentioned first (e.g., in region scale-out tables and migration), and Windows-specific tools (PowerShell) are given equal prominence to cross-platform tools (CLI), but Linux-native scripting or commands are not. There is also a lack of Linux-specific guidance or parity in some features.
Recommendations
- Provide bash or Linux shell script equivalents for all Azure PowerShell examples, or clarify that Azure CLI commands are cross-platform and sufficient.
- When listing operating systems (e.g., in region tables, migration sections), alternate the order or explicitly address both equally, rather than defaulting to Windows-first.
- For migration, clarify the roadmap or alternatives for Linux users, or provide a workaround if possible.
- Include Linux-specific considerations or troubleshooting tips where relevant, especially in sections where Windows-specific behaviors or limitations are discussed.
- Review all examples and ensure that Linux users are not left without guidance or are not required to use Windows tools for management tasks.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-core-tools-reference.md
...cles/azure-functions/functions-core-tools-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation for Azure Functions Core Tools demonstrates a moderate Windows bias. The page references Windows-specific tools and patterns (such as func.exe and the use of .pfx certificates), and some features or instructions are described in a way that assumes a Windows environment. There is a lack of explicit Linux/macOS examples, and certain options (like certificate handling) are described in a way that is more familiar to Windows users. Additionally, PowerShell is mentioned as a supported runtime with special features, but there is little parity discussion for Linux shells or scripting environments.
Recommendations
- Provide explicit Linux/macOS command-line examples alongside or in place of Windows-centric ones.
- Avoid referencing Windows-specific binaries (e.g., func.exe) in the title or introductory text; use cross-platform terminology (e.g., Azure Functions Core Tools CLI).
- Where features are Windows-specific (such as .pfx certificate handling), clarify cross-platform support and provide equivalent instructions for Linux/macOS (e.g., using OpenSSL-generated certificates).
- When mentioning PowerShell-specific features, also discuss parity or alternatives for Bash or other common Linux shells.
- Ensure that any references to local emulators, encryption, or file paths include Linux/macOS equivalents.
- Add notes or tables indicating OS support for each feature or command where relevant.
Azure Functions
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI (which is cross-platform) and Azure PowerShell examples for managing access keys, but the PowerShell examples are given equal prominence and detail, despite PowerShell being primarily associated with Windows. There are no explicit Linux/Bash-native script examples, and the CLI example notes that it must be modified to run in a Windows terminal, but does not provide a corresponding Linux/Bash example. There is also no mention of Linux-specific tools or workflows, and the PowerShell examples are more verbose and detailed than the CLI ones.
Recommendations
- Provide explicit Bash/Linux shell script examples alongside Azure CLI and PowerShell, especially for key management tasks.
- Clarify that Azure CLI commands are cross-platform and provide any necessary modifications for both Windows and Linux shells.
- Avoid giving PowerShell examples equal or greater prominence than CLI/Bash unless there is a Windows-specific feature being demonstrated.
- Where PowerShell is used, consider providing a Bash equivalent for parity.
- Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide sample commands for each where syntax or environment differs.
Azure Functions
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 Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It assumes the use of Visual Studio Code and the Azurite storage emulator, both of which are cross-platform but have stronger adoption and easier setup on Windows. The instructions for starting Azurite and running the function app rely on VS Code's command palette and do not provide explicit CLI alternatives for Linux/macOS users. There are no explicit Linux/macOS shell commands or terminal instructions, and no mention of platform-specific differences or troubleshooting for non-Windows environments. The documentation also does not mention or link to Linux-native tools or workflows, such as using the Azure CLI directly in bash/zsh, or running Azurite from the command line outside VS Code.
Recommendations
- Add explicit instructions for starting Azurite from the command line (e.g., `npx azurite` or `azurite` if installed globally), and clarify that it works on Linux/macOS as well as Windows.
- Provide alternative instructions for running and debugging the function app using the Azure Functions Core Tools CLI (`func start`) for users who may not use VS Code or prefer terminal workflows.
- Include notes or links about installing prerequisites (such as .NET Core, Node.js, Python, Java) on Linux/macOS, not just Windows.
- Explicitly mention that all tools and steps are cross-platform, and call out any platform-specific caveats or troubleshooting steps.
- Where possible, provide bash/zsh shell command equivalents alongside any PowerShell or Windows-centric instructions.
- Consider adding a 'Platform differences' or 'Linux/macOS notes' section to address any subtle differences in setup or usage.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-app-settings.md
...ain/articles/azure-functions/functions-app-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally aims for cross-platform coverage, but there are subtle Windows biases. In several places, Windows-specific tools, settings, or patterns are mentioned before Linux equivalents, or are given more detailed explanations. Some settings and examples (such as environment variable delimiters, file paths, and PowerShell-specific settings) are Windows-centric or prioritize Windows terminology. PowerShell and Windows-specific configuration options are described in more detail than their Linux or cross-platform counterparts. In a few cases, Windows-only settings are called out, but Linux-only settings are less emphasized.
Recommendations
- Ensure that all examples and explanations are provided for both Windows and Linux, with equal detail and prominence.
- When describing environment variable delimiters or file paths, always show both Windows and Linux syntax side by side.
- For settings that are platform-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION for Windows), provide a corresponding note or section for Linux, even if just to state the equivalent or that it is not applicable.
- Avoid prioritizing Windows terminology or tools (such as Azure PowerShell) over cross-platform alternatives (like Azure CLI); mention both together or prefer cross-platform tools.
- Where PowerShell-specific settings are described in detail, ensure similar coverage for Bash or other Linux-relevant scripting environments if applicable.
- Review the order in which OS-specific information is presented, and alternate or balance Windows and Linux references to avoid implicit prioritization.
Azure Functions
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 towards Windows and Visual Studio users. All instructions and UI references are for Visual Studio, a Windows-first IDE, with no mention of cross-platform alternatives (such as VS Code or CLI). The use of Solution Explorer, Publish dialogs, and NuGet Package Manager Console (which is PowerShell-based) are all Windows-centric. There are no Linux/macOS-specific instructions or CLI-based alternatives provided, despite Azure Storage Explorer being cross-platform.
Recommendations
- Provide equivalent instructions for developing and running Azure Functions using cross-platform tools such as Visual Studio Code and the Azure Functions Core Tools CLI.
- Include examples of how to install dependencies and manage app settings using command-line tools (e.g., dotnet CLI, func CLI) that work on Linux and macOS.
- Reference cross-platform editors and workflows alongside Visual Studio, or link to relevant guides for non-Windows users.
- Avoid assuming the use of Solution Explorer, Publish dialogs, or NuGet Package Manager Console; instead, offer alternative steps for users on other platforms.
- Clearly indicate which steps are Windows-specific and provide parity for Linux/macOS users wherever possible.
Azure Functions
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 a Windows bias primarily in the Java example, where the ffmpeg path uses a Windows-style executable (ffmpeg.exe) and the instructions reference a Windows directory structure. There is no explicit Linux/Unix example for Java, and the use of .exe implies Windows as the default. In contrast, the Python examples and the file share mounting section are Linux-focused, but there is no parity in providing both Windows and Linux examples for all languages. Additionally, PowerShell is mentioned as an upload option, but not demonstrated, and Windows tools are referenced before Linux equivalents in some places.
Recommendations
- For Java, provide both Windows and Linux examples for accessing and executing dependencies, including paths and executable formats (e.g., ffmpeg.exe vs. ffmpeg).
- Avoid using Windows-specific file extensions (like .exe) in cross-platform documentation unless both alternatives are shown.
- Explicitly mention and demonstrate how to set up and use dependencies on both Windows and Linux environments for all supported languages.
- When referencing upload tools (Azure CLI, PowerShell, Portal), provide example commands for both Windows (PowerShell/CMD) and Linux (Bash) environments.
- Ensure that instructions and code snippets do not assume a default platform; clarify when steps or paths differ between Windows and Linux.
Azure Functions
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 moderate Windows bias. It references Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, and the link for generating SAS tokens is specifically tagged with '?tabs=windows'. There are no Linux-specific instructions or CLI alternatives for these steps, and no mention of Linux-native tools or workflows. The documentation assumes the use of Storage Explorer and does not provide parity for Linux users who may prefer CLI or cross-platform solutions.
Recommendations
- Provide explicit Azure CLI commands for uploading files to Azure Storage and generating SAS tokens, as these are cross-platform and suitable for Linux users.
- Avoid linking to documentation with Windows-specific tabs or, if necessary, ensure Linux/macOS tabs are equally visible and referenced.
- Mention and provide instructions for using Linux-native tools (e.g., azcopy, Azure CLI) for all storage operations.
- Clarify that Azure Storage Explorer is available on Linux and macOS, or suggest alternatives if certain features are Windows-only.
- Review all steps to ensure that Linux users can follow the workflow without needing to use Windows-specific tools or interfaces.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/configure-networking-how-to.md
...rticles/azure-functions/configure-networking-how-to.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates some Windows bias by only mentioning or providing examples with Windows-centric tools (such as AzCopy and Azure Storage Explorer), and by omitting any explicit Linux command-line or cross-platform alternatives for storage migration. There are no CLI or scripting examples (e.g., Bash, Azure CLI, PowerShell) for Linux users, and the tools referenced are more familiar or accessible to Windows users. The documentation also refers to UI navigation steps in the Azure portal, which are platform-agnostic, but the lack of command-line parity is notable.
Recommendations
- Add explicit Linux and cross-platform examples for copying storage data, such as using Azure CLI commands (az storage blob/file copy) or AzCopy examples with Bash.
- Mention that AzCopy is available cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux (Bash).
- Include references to open-source or cross-platform tools for storage management, not just Azure Storage Explorer.
- Where possible, provide both portal (UI) and CLI (Azure CLI, Bicep, ARM templates) instructions side-by-side, so users on any OS can follow along.
- Clarify that all steps can be performed from any OS, and highlight any OS-specific prerequisites or differences.
Azure Functions
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 and Windows-specific tools or patterns are prioritized or presented first. PowerShell is given its own programming language pivot, and in several command sections, Windows command-line (Cmd) and PowerShell examples are provided before or alongside bash/Linux equivalents. Some sections, such as virtual environment activation for Python, include multiple Windows-specific tabs (bash, Cmd), and PowerShell is treated as a first-class language option. There is also a tendency to refer to 'terminal or command prompt' generically, which can be ambiguous for Linux users.
Recommendations
- When presenting command examples, alternate the order of Windows and Linux/macOS instructions, or present Linux/macOS first where appropriate.
- Ensure that all command-line instructions are clearly labeled for each platform, and avoid ambiguous terms like 'command prompt' or 'terminal' without specifying the OS.
- For PowerShell, clarify cross-platform support and, where possible, provide bash/zsh equivalents for scripting tasks.
- In sections where Windows-specific tools or patterns are mentioned (such as PowerShell or Cmd), ensure that Linux/macOS alternatives are equally visible and easy to follow.
- Consider adding explicit Linux/macOS troubleshooting notes or common issues, especially for steps that may differ (e.g., file paths, environment variable syntax).
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page is generally cross-platform in intent, focusing on Visual Studio Code and Azure Functions, which are available on Windows, macOS, and Linux. However, there are subtle signs of Windows bias: troubleshooting advice specifically mentions Windows (e.g., WSL Bash), and there are no explicit Linux/macOS-specific instructions or examples. Windows-specific issues are called out, but Linux/macOS equivalents are not discussed, and no terminal or shell commands are shown for non-Windows users.
Recommendations
- Add troubleshooting steps relevant to Linux/macOS environments, such as common shell or permission issues.
- Where Windows-specific advice is given (e.g., about WSL Bash), provide equivalent guidance for Linux/macOS users (e.g., default terminal shell issues, permissions, or path differences).
- Include explicit notes or examples for Linux/macOS users, such as how to open the command palette or run commands in their environments.
- Ensure that any references to tools or extensions clarify their cross-platform compatibility.
- If possible, add screenshots or terminal snippets from both Windows and Linux/macOS to illustrate parity.
Azure Functions
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 Extensions
Summary
The documentation generally provides cross-platform instructions, but there are subtle signs of Windows bias. Windows-specific file extensions (e.g., 'handler.exe') are mentioned before or alongside Linux equivalents. Windows environment variable setting commands are shown after Unix-style commands, but the Windows instructions are sometimes more explicit. The documentation refers to Windows-specific behaviors (such as changing 'defaultExecutablePath' to 'handler.exe' on Windows) and includes Windows command syntax (e.g., 'set GOOS=linux') in separate tabs, but does not provide PowerShell examples or prioritize Windows tools. Linux and macOS instructions are present and generally complete.
Recommendations
- When referring to executable names, mention the Linux version ('handler') first, or present both at the same time (e.g., 'handler (or handler.exe on Windows)').
- Instruct users to set the 'defaultExecutablePath' to 'handler' by default, with a note for Windows users to use 'handler.exe' if needed.
- Ensure that Linux/macOS instructions are always presented before Windows, or group them together to avoid the perception of Windows-first bias.
- If possible, provide PowerShell equivalents for Windows commands, or clarify when to use Command Prompt vs. PowerShell.
- Explicitly state that all examples are cross-platform unless otherwise noted, and highlight any platform-specific differences in a dedicated section.
- Consider adding a table summarizing key platform differences (e.g., file extensions, environment variable syntax) for quick reference.
Azure Functions
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 demonstrates a subtle Windows bias. Windows is presented as the default or primary runtime for Azure Functions (e.g., in pom.xml examples and deployment defaults), and Linux support is mentioned only as an alternative. The configuration and deployment instructions focus on Windows first, with Linux-specific instructions relegated to notes or tips. There is also a lack of explicit Linux shell examples for some steps, and the use of Windows tools and patterns (such as PowerShell and Cmd) is given equal or more prominence than Linux/Bash, despite the cross-platform context.
Recommendations
- Present Linux and Windows options equally, e.g., by showing both 'runtime.os: windows' and 'runtime.os: linux' in configuration examples, or by defaulting to a cross-platform neutral value.
- When describing deployment and configuration, avoid language that assumes Windows as the default; instead, clarify that both Windows and Linux are supported and highlight any differences up front.
- Ensure that all command-line examples are provided for Bash (Linux/macOS), PowerShell, and Cmd, and that Bash is not treated as an afterthought.
- Where platform-specific instructions are necessary (e.g., setting JAVA_HOME), provide explicit examples for both Windows and Linux.
- Consider including a section or callout on developing and deploying on Linux, including any caveats or best practices.
- Review and update the documentation to ensure Linux users are not required to infer steps from Windows-centric instructions.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-cli-python.md
...es/azure-functions/create-first-function-cli-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Bash (Linux/macOS) and Windows (PowerShell, Cmd) examples for Python virtual environment setup, and both Azure CLI and Azure PowerShell examples for Azure resource creation. However, there is a slight Windows bias: PowerShell and Cmd are given equal prominence to Bash, and PowerShell is presented as a first-class alternative to Azure CLI throughout, despite Azure CLI being cross-platform. Windows-specific tools and patterns (PowerShell, Cmd, 'py' launcher) are mentioned alongside or before Linux equivalents, and some instructions (such as using 'py' instead of 'python') are more relevant to Windows users.
Recommendations
- Prioritize Bash (Linux/macOS) examples before PowerShell and Cmd, as Bash is the default shell on most non-Windows systems and is also available on Windows via WSL.
- Clearly indicate which commands are for which platforms, and consider grouping Windows-specific instructions after cross-platform or Linux-first instructions.
- Instruct users to use 'python' instead of 'py' for virtual environment creation, as 'py' is a Windows-specific launcher.
- Emphasize Azure CLI as the primary, cross-platform tool for resource creation, and present PowerShell as an alternative for Windows users.
- Add explicit notes or callouts for Linux/macOS users where necessary, especially for common issues (e.g., missing 'venv' package).
- Consider providing a single, cross-platform command block for steps that are identical across platforms, reducing fragmentation and potential confusion.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/disable-function.md
...blob/main/articles/azure-functions/disable-function.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation presents Azure PowerShell and Portal examples alongside Azure CLI, but does not provide any Linux- or bash-specific examples, nor does it mention Linux-native tools or workflows. PowerShell is given a dedicated section, and the CLI examples are generic but do not clarify Linux compatibility or provide bash-specific guidance. The Portal and PowerShell sections may imply a Windows-centric workflow, and the lack of explicit Linux shell examples or troubleshooting for Linux users (beyond a single note about hyphens in function names) suggests a Windows-first bias.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform and, where relevant, provide bash/zsh shell examples (e.g., with export statements or Linux environment variable syntax).
- Add a section or tab for bash/Linux shell users, especially for setting environment variables or editing local.settings.json using Linux tools.
- Clarify that PowerShell examples are primarily for Windows users, and offer equivalent bash commands where possible.
- Include troubleshooting or notes specific to Linux environments, such as file permissions or common shell differences.
- Where PowerShell is mentioned, ensure parity by offering bash or sh alternatives, or at least referencing their use.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dotnet-isolated-process-guide.md
...icles/azure-functions/dotnet-isolated-process-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows-specific tools and configuration steps (such as Visual Studio, PowerShell, and Windows-specific Azure CLI commands) are mentioned before or more prominently than their Linux equivalents. Some deployment and configuration examples are provided only for Windows or with Windows as the primary example, with Linux alternatives appearing later or not at all. There are also references to Windows-specific concepts (e.g., .NET Framework, win-x86/win-x64) without always providing equivalent Linux guidance or parity in examples.
Recommendations
- Ensure all CLI and deployment examples are provided for both Windows and Linux, with Linux examples given equal prominence and order.
- Where Visual Studio or PowerShell are mentioned, also mention and provide examples for cross-platform alternatives (e.g., Visual Studio Code, Bash, Azure CLI).
- In tables and lists of options, avoid listing Windows tools or workflows first by default; alternate or group by platform.
- When referencing runtime identifiers or build targets (e.g., win-x64), always include the Linux equivalents (e.g., linux-x64) in parallel.
- For debugging and local development, provide explicit Linux instructions and troubleshooting steps, not just Windows/Visual Studio.
- Add explicit notes or callouts where a feature or tool is Windows-only, and suggest Linux-compatible alternatives where possible.
- Review all code snippets and ensure any shell commands (e.g., Azure CLI) are shown with both Windows (cmd/PowerShell) and Linux (bash) syntax where differences exist.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-core-tools-reference.md
...cles/azure-functions/functions-core-tools-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits subtle Windows bias. It references Windows-specific tools (e.g., func.exe), mentions PowerShell as a supported runtime with special features, and refers to Windows patterns (such as .pfx certificates and trusted certificate creation) without clarifying Linux/Mac equivalents. There are no explicit Linux or cross-platform shell examples, and some features (like log streaming) are noted as unsupported on Linux in certain plans, but without offering Linux alternatives or parity guidance.
Recommendations
- Provide explicit Linux/macOS shell examples (e.g., bash/zsh) alongside or instead of Windows/PowerShell commands.
- Clarify cross-platform behavior for features like certificate creation, trusted certificates, and file paths (e.g., .pfx usage on Linux).
- Avoid referencing Windows-specific tools (like func.exe) in the title/description; use cross-platform terms (e.g., Azure Functions Core Tools CLI).
- For features not supported on Linux (e.g., log streaming in Consumption plan), offer alternative Linux-compatible workflows or clarify expected behavior.
- Ensure all examples and instructions are validated on Linux/macOS and highlight any OS-specific differences or requirements.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-function-bicep.md
...ure-functions/functions-create-first-function-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily a Windows-centric tool, and its inclusion as a first-class alternative (with full code samples for every language) indicates a Windows bias. There are no Linux-specific shell examples (e.g., Bash), and the PowerShell examples are given equal prominence to the CLI, which may confuse or disadvantage Linux users. Additionally, the documentation refers to saving files to your 'local computer' without clarifying cross-platform paths or shell conventions.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users alongside Azure CLI commands, including file path conventions (e.g., ./main.bicep).
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend it as the primary cross-platform tool.
- De-emphasize Azure PowerShell as a primary deployment method, or clearly label it as Windows-centric, with a note for Linux users about PowerShell Core availability.
- Include notes or examples for common Linux/macOS shell environments where relevant (e.g., using export for environment variables, file permissions, etc.).
- Ensure that any references to file paths or shell commands use cross-platform syntax or provide both Windows and Linux/macOS variants.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-maven-intellij.md
...les/azure-functions/functions-create-maven-intellij.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a Windows bias in several ways: it references Windows-specific platforms first (e.g., 'Windows-Java 17'), omits explicit Linux/macOS instructions or screenshots, and does not provide any Linux-specific examples or terminal commands. The workflow assumes the user is on Windows or using Windows defaults, with no mention of Linux-specific steps or troubleshooting.
Recommendations
- Provide explicit instructions and screenshots for Linux/macOS users, especially for steps that may differ (e.g., setting JAVA_HOME, running Maven, or using Azure Functions Core Tools).
- When listing platform options (such as during function app creation), mention Linux options alongside or before Windows, and clarify any differences (e.g., Java 21 support on Linux only).
- Include terminal/command-line examples for Linux/macOS (e.g., using bash instead of only referencing GUI steps or Windows paths).
- Add troubleshooting notes for common Linux/macOS issues (such as file permissions, environment variable setup, or dependency installation).
- Ensure parity in all screenshots and instructions, so Linux/macOS users are not left to infer or adapt Windows-centric guidance.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows users by focusing exclusively on Visual Studio (the full IDE), which is only fully supported on Windows. All instructions, screenshots, and workflows assume the use of Visual Studio, with no equivalent steps or examples for Linux users. There are no CLI or cross-platform alternatives provided within the main content, and Linux users are only briefly redirected to a separate Visual Studio Code article. The use of Windows-specific tools and UI patterns (e.g., Visual Studio menus, File Explorer) further reinforces the Windows bias.
Recommendations
- Provide parallel instructions for Linux users using Visual Studio Code and the Azure Functions Core Tools CLI within this article, or clearly indicate cross-platform alternatives at each step.
- Include CLI-based steps for creating, running, and deploying Azure Functions projects, which work on both Windows and Linux.
- Add screenshots and examples from Linux environments (e.g., using terminal, file managers) where appropriate.
- Clarify in the prerequisites and introduction that Visual Studio is only available on Windows, and offer a direct, prominent link to the cross-platform (VS Code/CLI) guide.
- Where Azurite or other tools are mentioned, note their installation and usage on Linux.
- Consider restructuring the article or providing tabs/sections for Windows (Visual Studio) and Linux/macOS (VS Code/CLI) users to ensure parity.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-based-connections-tutorial-2.md
...ons/functions-identity-based-connections-tutorial-2.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation is strongly Windows-centric, explicitly stating support for C# class library functions on Windows only. There are no examples or instructions for Linux-based Azure Functions, nor for other operating systems. All code and deployment steps assume a Windows environment, and there is no mention of Linux-specific considerations or parity.
Recommendations
- Add explicit instructions and examples for deploying and running Azure Functions with identity-based connections on Linux-based hosting plans.
- Clarify which steps are cross-platform and which are Windows-specific; provide alternative steps or notes for Linux users.
- Include examples for other supported languages and platforms, or at least acknowledge their support and provide links to relevant documentation.
- If certain features are not yet available on Linux, clearly state this and provide a roadmap or workaround if possible.
- Ensure that CLI commands and file paths are presented in a cross-platform manner (e.g., use forward slashes or note both Windows and Linux path formats).
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-deployment-technologies.md
...s/azure-functions/functions-deployment-technologies.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-based deployment options (such as source control, Local Git, and FTPS) are called out as 'Windows-only' in the technology availability table, while Linux equivalents are either less emphasized or described as limited. Windows-specific tools and patterns (e.g., Visual Studio, Kudu/SCM site) are mentioned first or in more detail, and some deployment methods (like source control and FTPS) are not available or are restricted on Linux. Linux-specific instructions are present but often secondary, and there are few Linux command-line or native tool examples.
Recommendations
- Provide Linux-first or Linux-parity examples for each deployment method, especially where Windows is called out as the default or primary platform.
- Where deployment technologies are Windows-only, offer clear Linux alternatives or workarounds, and link to relevant Linux documentation.
- Include more explicit Linux command-line examples (e.g., Bash, native Linux tools) alongside or before Windows/PowerShell/Visual Studio instructions.
- Clarify any limitations or differences for Linux users up front, and avoid presenting Windows tools as the default unless truly universal.
- Expand documentation on remote build and deployment for Linux, including troubleshooting and best practices.
- Where possible, avoid using 'Windows-only' as a default and instead structure tables and sections to give Linux and Windows equal prominence.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-vs.md
.../main/articles/azure-functions/functions-develop-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 on Windows. All instructions, screenshots, and workflows assume the use of Visual Studio 2022, which is only fully supported on Windows. There are no examples or guidance for developing Azure Functions using Visual Studio Code, .NET CLI, or other cross-platform tools. PowerShell is used in package installation examples, and Windows-specific UI elements and dialogs are referenced throughout. There is no mention of Linux or macOS development environments, nor are alternative workflows (such as using VS Code or CLI tools) provided.
Recommendations
- Add explicit guidance and examples for developing Azure Functions on Linux and macOS using Visual Studio Code and the .NET CLI.
- Include CLI-based instructions for project creation, dependency management, and publishing, alongside Visual Studio UI steps.
- Provide screenshots and workflow descriptions for cross-platform tools (e.g., VS Code, terminal) in addition to Visual Studio.
- Replace or supplement PowerShell commands with equivalent Bash commands for Linux/macOS users.
- Clearly indicate which steps or features are Windows/Visual Studio-specific, and offer alternatives where possible.
- Reference the Azure Functions Core Tools and Azure CLI for tasks like local development, configuration, and deployment, with examples for all supported platforms.