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 2026-2050 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-php-mysql-app/azure-portal-deploy-sample-code-3.md
...ial-php-mysql-app/azure-portal-deploy-sample-code-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples, but it also does not mention or demonstrate any Linux-specific tools, commands, or workflows. While there is no explicit Windows bias, the absence of Linux examples or references may leave Linux users without clear guidance.
Recommendations
- Include explicit instructions or notes for both Windows and Linux users where relevant.
- If platform-specific steps are required (e.g., file paths, environment variable configuration), provide examples for both Windows and Linux.
- Clarify that the instructions are platform-agnostic if that is the case, or specify any differences users might encounter on Linux.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
...-nodejs-mongodb-app/deploy-local-git-azure-portal-4.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides generic instructions for obtaining deployment credentials but does not include any platform-specific examples or guidance. There are no explicit Windows tools or commands, but there is also a lack of Linux (or macOS) specific instructions or examples, which may leave Linux users without clear guidance on how to use the credentials.
Recommendations
- Add example commands for pushing code using both Windows (e.g., PowerShell or Command Prompt) and Linux/macOS (e.g., Bash).
- Include screenshots or terminal snippets from both Windows and Linux environments.
- Mention any platform-specific considerations for using the credentials (such as where to store them securely or how to input them in different shells).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-nodejs-mongodb-app/build-settings-azure-portal-2.md
...al-nodejs-mongodb-app/build-settings-azure-portal-2.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions using a generic 'dialog' interface without specifying any platform, but it does not offer command-line examples or alternative methods for Linux users (e.g., using Bash or Linux-native tools). This omission may disadvantage users who prefer or require non-GUI or Linux-based workflows.
Recommendations
- Add command-line examples for setting the configuration using both Windows (e.g., PowerShell, CMD) and Linux (e.g., Bash, Azure CLI).
- Explicitly mention if the dialog is available cross-platform or provide equivalent steps for Linux environments.
- Ensure that future documentation includes parity between Windows and Linux instructions, especially for environment variable or configuration changes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/includes/tutorial-python-postgresql-app/deploy-local-git-azure-portal-3.md
...thon-postgresql-app/deploy-local-git-azure-portal-3.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation references copying the 'Git Clone Uri' for later use but does not provide any platform-specific instructions or examples. However, it implicitly assumes a generic workflow and does not mention or demonstrate Linux-specific commands or tools, nor does it provide parity examples for Linux users.
Recommendations
- Add explicit instructions or examples for both Windows (e.g., PowerShell, Command Prompt) and Linux/macOS (e.g., Bash) for setting up a Git remote using the copied URI.
- Include sample commands for cloning the repository on both Windows and Linux platforms.
- Clarify that the instructions are platform-agnostic if that is the intent, or otherwise provide parity in examples and tool references.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/app-service/overview-app-gateway-integration.md
...ticles/app-service/overview-app-gateway-integration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure CLI commands for configuration examples and does not provide any OS-specific (Windows or Linux) shell or scripting examples. There are no references to Windows tools, PowerShell, or Windows-first patterns, but there is also a lack of parity for Linux-specific command-line examples or considerations. The documentation assumes the use of Azure CLI, which is cross-platform, but does not explicitly mention or demonstrate usage in Linux environments (e.g., bash scripts, Linux shell nuances).
Recommendations
- Explicitly state that Azure CLI commands work on Windows, macOS, and Linux to reassure users of cross-platform compatibility.
- Where relevant, provide example command invocations in both Windows (PowerShell/CMD) and Linux (bash) shells, especially if there are any differences in quoting, environment variables, or command syntax.
- If any step has OS-specific considerations (such as file paths, authentication methods, or environment setup), call these out in dedicated sections or notes.
- Include a brief section or note confirming that all examples are tested and supported on Linux environments.
- If possible, add links to Azure CLI installation and usage guides for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/create-gateway-internal-load-balancer-app-service-environment.md
...gateway-internal-load-balancer-app-service-environment.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples, but when describing how to export the ILB certificate, it only mentions using a browser to export the certificate in Base-64 encoded CER format. There are no instructions or examples for how to retrieve the certificate using command-line tools (such as OpenSSL) commonly used on Linux systems, nor is there mention of PowerShell or Windows-specific tools. This omission may disadvantage Linux users who prefer or require CLI-based workflows.
Recommendations
- Add step-by-step instructions for exporting the ILB certificate using OpenSSL or similar command-line tools on Linux.
- Provide both browser-based and CLI-based (Windows and Linux) methods for retrieving and exporting certificates.
- Explicitly mention cross-platform approaches and tools to ensure users on all operating systems can follow the troubleshooting steps.
- Where relevant, include example commands for both Windows (e.g., PowerShell) and Linux (e.g., Bash/OpenSSL) environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/how-to-project-admin.md
...cs/blob/main//articles/dev-box/how-to-project-admin.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to grant admin access using the Azure Portal GUI, with no mention of command-line alternatives such as Azure CLI, PowerShell, or Bash. While no explicit Windows tools or PowerShell commands are present, the lack of CLI examples (which are often more accessible on Linux) and the focus on GUI workflows can be considered a subtle bias, as Linux users may prefer or require command-line instructions.
Recommendations
- Add equivalent instructions for assigning roles using the Azure CLI, including example commands.
- If possible, provide Bash and PowerShell command examples side by side for cross-platform parity.
- Explicitly mention that the Azure Portal is web-based and platform-agnostic, but highlight CLI alternatives for users who prefer or require them.
- Include links to official Azure CLI documentation for role assignments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/application-gateway/use-server-sent-events.md
...articles/application-gateway/use-server-sent-events.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific configuration examples or commands, but it also does not include any examples at all—neither for Windows nor Linux. There is no explicit Windows bias in terms of tools, commands, or ordering, but the absence of any example code or CLI instructions means Linux parity is not addressed.
Recommendations
- Add concrete configuration examples for both Windows (e.g., using PowerShell or CMD) and Linux (e.g., using Bash or curl) to illustrate how to set the required HTTP headers for SSE.
- Include sample backend server code snippets in both Windows (e.g., .NET) and Linux-friendly languages (e.g., Python, Node.js) to demonstrate header configuration.
- If referencing log file access or configuration, provide instructions for both Windows and Linux environments.
- Explicitly mention that the guidance applies equally to both Windows and Linux backend servers, or clarify any platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/how-to-disable-automanage.md
...main//articles/automanage/how-to-disable-automanage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions only for disabling Azure Automanage via the Azure portal, with no mention of command-line or scripting methods (such as PowerShell, Azure CLI, or REST API). While this avoids explicit Windows bias, it also omits Linux parity by not offering CLI examples, which are especially relevant for Linux administrators. There is no evidence of Windows-specific tools or patterns, but the lack of Linux/CLI guidance is a notable omission.
Recommendations
- Add instructions for disabling Automanage using the Azure CLI, which is cross-platform and commonly used by Linux users.
- If PowerShell examples are provided in the future, ensure equivalent Azure CLI or Bash examples are included.
- Explicitly mention that the portal method works for both Windows and Linux VMs, if applicable.
- Consider including REST API examples for automation scenarios relevant to both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automanage/overview-about.md
...-docs/blob/main//articles/automanage/overview-about.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux support, but consistently mentions Windows first (e.g., 'Supported Windows Server versions and Linux distros', 'Automanage for Linux' and 'Automanage for Windows Server'—with Windows listed first in the main text and Linux only as a secondary mention). There are no command-line examples or tool references, so there is no evidence of PowerShell-heavy content or exclusive mention of Windows tools. However, the ordering and phrasing suggest a subtle 'windows_first' bias.
Recommendations
- Alternate the order in which Windows and Linux are mentioned (e.g., sometimes list Linux first).
- Where possible, provide parallel examples or references for both Windows and Linux, ensuring neither is consistently prioritized.
- Explicitly state parity of features and support for both platforms where applicable.
- Consider adding a section or callout highlighting Linux-specific considerations or workflows, to balance the focus.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-add-functions.md
...e-manager/templates/template-tutorial-add-functions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for deploying ARM templates, but the PowerShell example is listed first. There are no Linux-specific instructions, but the CLI example is cross-platform. There is a slight 'windows_first' bias due to ordering, but no exclusive use of Windows tools or missing Linux examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples in tutorials, or explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS.
- Where possible, include terminal screenshots or instructions that reflect both Windows and Linux environments (e.g., file path formats, shell differences).
- Ensure that references to prerequisites or setup steps (such as installing Azure CLI) include links or notes for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/automation/includes/automation-dsc-linux-retirement-announcement.md
...cludes/automation-dsc-linux-retirement-announcement.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page only mentions the retirement of Azure Automation DSC for Linux, without providing any guidance or examples for Linux users on alternatives or migration steps. There is no mention of Windows-specific tools or examples, but the lack of Linux-focused content creates a gap for Linux users.
Recommendations
- Provide clear migration guidance for Linux users, such as steps to move from Azure Automation DSC for Linux to supported alternatives (e.g., Azure Policy Guest Configuration).
- Include examples or links to documentation specifically for Linux environments.
- Ensure parity by mentioning both Windows and Linux scenarios where relevant, especially when announcing deprecations or changes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/azure-pipeline-import-task.md
.../azure-app-configuration/azure-pipeline-import-task.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, tool references, or screenshots. However, it lacks any mention or examples specific to Linux environments, such as Linux-based Azure Pipelines agents, file path conventions, or troubleshooting steps for Linux users. This omission may make it less approachable for users running pipelines on Linux agents.
Recommendations
- Explicitly mention that the Azure Pipelines agent and the App Configuration Import task are cross-platform and supported on both Windows and Linux agents.
- Include examples or notes on specifying file paths using both Windows (\) and Linux (/) conventions in the 'Configuration File Path' parameter.
- Add troubleshooting tips or notes for common issues that may differ between Windows and Linux agents (e.g., file permissions, case sensitivity).
- If screenshots or UI elements differ between platforms, provide clarifications or alternative visuals.
- State any platform-specific prerequisites or limitations, if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/avere-vfxt/avere-vfxt-deploy.md
...cs/blob/main//articles/avere-vfxt/avere-vfxt-deploy.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 or tool references. However, there is a subtle bias in the SSH key creation help link, which points only to instructions for creating SSH keys from Windows, without mentioning or linking to Linux or macOS equivalents. No PowerShell or Windows-specific tools are otherwise referenced, and the workflow is primarily portal-based and OS-agnostic.
Recommendations
- Provide links to SSH key creation instructions for Linux and macOS users alongside the Windows link.
- Explicitly mention that the deployment process is platform-agnostic and can be performed from any OS with browser access.
- Where authentication or connection steps are described, ensure parity by referencing both Windows and Linux/macOS workflows or tools if relevant.
- Review any other linked prerequisite or follow-up documentation to ensure Linux users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-telemetry-javascript.md
.../azure-app-configuration/howto-telemetry-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before macOS/Linux (bash), which is an example of 'windows_first' bias. However, all major platforms are covered, and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present environment variable setup instructions for all platforms in parallel, or list Linux/macOS first to avoid implicit prioritization of Windows.
- Consider using tabbed or side-by-side code blocks for platform-specific commands to improve parity and clarity.
- Review other sections for similar ordering or implicit prioritization, and ensure Linux/macOS users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-targetingfilter-javascript.md
...-app-configuration/howto-targetingfilter-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on all major platforms (Windows Command Prompt, PowerShell, macOS/Linux), but lists Windows methods (cmd, PowerShell) before the Linux/macOS equivalent. There are no missing Linux examples or exclusive use of Windows tools, but the ordering may subtly prioritize Windows users.
Recommendations
- List Linux/macOS and Windows instructions in parallel (side-by-side) or alternate the order in which they are presented to avoid always putting Windows first.
- Consider using tabs or collapsible sections for platform-specific instructions to give equal prominence.
- Explicitly state that the instructions apply to all platforms and that the order is arbitrary, or clarify that users should follow the steps for their OS.
- Review other sections for subtle prioritization and ensure parity in tool and example coverage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-targetingfilter-aspnet-core.md
...app-configuration/howto-targetingfilter-aspnet-core.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only .NET CLI and C# code examples, which are cross-platform, but omits any mention of OS-specific steps, shell commands, or environment differences. There are no explicit Windows-only commands (such as PowerShell), but there is also no guidance or examples for Linux or macOS users, especially regarding environment setup, user secrets storage, or running the application. The documentation implicitly assumes parity but does not confirm or demonstrate it.
Recommendations
- Explicitly state that all CLI commands and instructions work on Windows, Linux, and macOS, or note any OS-specific differences if they exist.
- If there are differences in using the Secret Manager tool or running the application on Linux/macOS (such as prerequisites or environment variables), provide those details.
- Add example shell commands for Linux/macOS where appropriate (e.g., using bash/zsh instead of only dotnet CLI, if relevant).
- Include screenshots or terminal output from Linux/macOS environments to demonstrate true cross-platform support.
- Mention any required dependencies or steps for Linux/macOS users, such as installing the .NET SDK or configuring permissions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-telemetry-python.md
...cles/azure-app-configuration/howto-telemetry-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning the equivalent command for macOS/Linux. All other examples (Python, HTML, Kusto) are cross-platform and do not show Windows-specific bias. No Linux examples are missing, and no Windows-only tools or patterns are used.
Recommendations
- Present environment variable instructions for all platforms together, or list Linux/macOS first to avoid implicit prioritization of Windows.
- Consider using a table or side-by-side format for environment variable setup commands to give equal prominence to all platforms.
- Review other documentation pages for similar ordering and ensure Linux/macOS users are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/howto-variant-feature-flags-javascript.md
...onfiguration/howto-variant-feature-flags-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for setting environment variables on Windows (cmd and PowerShell) before mentioning the macOS/Linux equivalent. All platforms are covered, but Windows instructions are listed first, which may suggest a subtle Windows-first bias.
Recommendations
- Present platform instructions in parallel (side-by-side table or tabs) rather than sequentially, or rotate the order in which platforms are listed to avoid always putting Windows first.
- Explicitly state that the instructions apply equally to all platforms, and avoid implying a primary platform.
- Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
- Consider using cross-platform tools or commands (such as dotenv files) for environment variable management, or mention them as alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-app-configuration/quickstart-python.md
.../articles/azure-app-configuration/quickstart-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias. In the prerequisites, the only platform-specific setup link is for Python on Windows, with no equivalent for Linux or macOS. In the environment variable setup section, Windows command prompt and PowerShell instructions are listed before macOS/Linux, but all platforms are covered and the instructions are clearly separated. No PowerShell-heavy scripting, exclusive use of Windows tools, or missing Linux examples are present.
Recommendations
- In the prerequisites, provide links for setting up Python on Linux and macOS alongside the Windows link.
- When presenting environment variable setup commands, consider listing all platforms in parallel (e.g., in a table or side-by-side tabs) or rotating the order so Linux/macOS is not always last.
- Where possible, ensure parity in references and guidance for all major platforms to avoid the perception of Windows as the default or primary environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/quickstart-team-customizations.md
...in//articles/dev-box/quickstart-team-customizations.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or tooling, but it also does not mention or demonstrate Linux-specific workflows, tools, or considerations. The process is described entirely through the Azure Portal and GitHub UI, which are cross-platform, but there is no explicit mention of Linux compatibility or parity, nor are there any CLI or script examples (Windows or Linux). This omission could be seen as a subtle bias, as it does not reassure Linux users or provide guidance for Linux-specific scenarios.
Recommendations
- Explicitly state that the process is OS-agnostic and works equally well for Windows and Linux-based dev boxes, if that is the case.
- If there are any differences or considerations for Linux-based dev boxes (such as customization file syntax, supported tools, or post-deployment validation), document them.
- Provide examples or screenshots that show Linux-based dev boxes or environments, to reassure users that Linux is a first-class citizen.
- If CLI or scripting options exist (e.g., Azure CLI, Bash scripts), provide equivalent examples for both Windows (PowerShell) and Linux (Bash).
- Include a section or FAQ entry addressing Linux users and common questions or troubleshooting steps relevant to Linux dev boxes.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-compute-fleet/modify-fleet.md
...lob/main//articles/azure-compute-fleet/modify-fleet.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to modify a Compute Fleet using the Azure portal, without providing any command-line examples or automation workflows. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI (such as Azure CLI), Bash, or Linux-oriented instructions. This omission may disadvantage users who prefer or require Linux-based or cross-platform command-line management.
Recommendations
- Add Azure CLI examples for modifying target capacity and VM size selection, including sample commands for both Windows and Linux shells.
- Include Bash script snippets for automation scenarios, ensuring parity with any PowerShell or portal-based workflows.
- Explicitly mention that these operations can be performed via CLI or REST API, and link to relevant documentation.
- Consider providing a table or section comparing portal, CLI, and API approaches for cross-platform clarity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-cloud-backup.md
...re-functions/durable/durable-functions-cloud-backup.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows-specific examples (e.g., directory paths like 'D:\home\LogFiles') before Linux equivalents, especially in the 'Run the sample' section. While both Windows and Linux examples are eventually provided, Windows is consistently mentioned first, which may subtly prioritize Windows users. There are no exclusive references to Windows-only tools, PowerShell, or missing Linux examples, and the code samples themselves are cross-platform.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first to avoid implicit prioritization.
- Explicitly state that the code and instructions are cross-platform where applicable.
- Where platform-specific details are required (such as file paths), provide both Windows and Linux examples together in all relevant sections.
- Consider using neutral or environment-agnostic examples (e.g., '/path/to/files') where possible, or clarify that the sample paths are just for illustration.
Azure Docs
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 ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') is mentioned without any equivalent Linux or macOS troubleshooting advice. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, 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 configuration, or dependencies on those platforms.
- Where OS-specific advice is given (such as the WSL Bash note), consider providing equivalent notes for Linux and macOS, or clarify that the guidance is only relevant to Windows users.
- Explicitly state that all steps are cross-platform unless otherwise noted, and provide links to platform-specific setup guides if available.
Azure Docs
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 Linux-specific guidance or CLI commands. While it avoids explicit Windows or PowerShell bias, it lacks parity by not including Linux or cross-platform command-line examples for setting app settings.
Recommendations
- Add explicit examples for setting the AzureWebJobsStorage app setting using both Azure CLI (cross-platform) and PowerShell (Windows).
- Include instructions or links for configuring app settings via the Azure Portal, Azure CLI, and Azure PowerShell, making clear which are cross-platform.
- Ensure that any future troubleshooting steps or code snippets are provided for both Windows and Linux environments, or use cross-platform tools by default.