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 2051-2075 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-code-constraints.md
...unctions/durable/durable-functions-code-constraints.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, JavaScript, Python, PowerShell, and Java. While PowerShell is included as a first-class language (with dedicated code tabs and guidance), there is no explicit Windows bias in terms of tools, shell commands, or patterns that would disadvantage Linux users. However, the inclusion of PowerShell as a primary example may be seen as a Windows-centric choice, since PowerShell is more commonly used on Windows, although it is now cross-platform. There are no examples or references to Linux-specific shells (e.g., Bash), nor are there any Windows-only tools or patterns mentioned. All examples are language-focused and do not reference OS-specific behaviors.
Recommendations
- Consider clarifying that PowerShell examples are also valid on Linux, given PowerShell Core's cross-platform support.
- If shell-based examples are needed in the future, provide Bash or POSIX shell equivalents alongside PowerShell to ensure Linux parity.
- Continue to avoid referencing Windows-only tools or patterns unless Linux equivalents are also provided.
- Explicitly mention in the documentation that all language examples are intended to be cross-platform where applicable.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md
...tions/errors-diagnostics/diagnostic-events/azfd0011.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also omits any mention of Linux, macOS, or cross-platform command-line methods for setting the FUNCTIONS_WORKER_RUNTIME variable. There are no Windows-specific tools or commands, but the lack of Linux or cross-platform guidance may leave non-Windows users underserved.
Recommendations
- Add explicit examples for setting the FUNCTIONS_WORKER_RUNTIME variable using both Azure CLI and PowerShell, making sure to include cross-platform (Linux/macOS) instructions.
- Mention how to set environment variables in both Windows and Linux environments, especially in deployment scripts.
- Provide sample commands for editing local.settings.json on different platforms, or clarify that the process is the same across platforms if applicable.
- Ensure parity in documentation by referencing both Windows and Linux tools and workflows where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0007.md
...tions/errors-diagnostics/diagnostic-events/azfd0007.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation describes how to resolve the error by deleting backup files from an Azure Storage container, but does not provide any concrete examples or command-line instructions. There is no explicit Windows or PowerShell bias, but the lack of any example commands (such as Azure CLI, PowerShell, or Linux shell) means Linux users are not given parity or guidance.
Recommendations
- Add example commands for deleting the backup files using cross-platform tools such as Azure CLI (az storage blob delete), which work on both Windows and Linux.
- If providing PowerShell examples, also provide equivalent Bash or Azure CLI examples.
- Explicitly mention that the instructions apply to all platforms and link to relevant Azure Storage tooling documentation for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-bindings-kafka-trigger.md
...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, JavaScript, PowerShell, Python, and Java. While there is no explicit Windows bias in terms of tools or instructions, the inclusion of PowerShell as a primary example language may suggest a slight Windows-centric approach, as PowerShell is more commonly associated with Windows environments (though it is now cross-platform). There are no exclusive references to Windows tools, no use of Windows-first patterns, and no missing Linux examples. All code samples and configuration instructions are platform-agnostic, and there is no mention of Windows-specific commands, paths, or behaviors.
Recommendations
- Clarify that PowerShell examples are cross-platform and work on Linux/macOS as well as Windows.
- Consider adding Bash or shell script examples if relevant, to further demonstrate Linux parity.
- Explicitly mention in introductory sections that all examples are intended to work on both Windows and Linux environments.
- If any troubleshooting or environment setup is discussed elsewhere, ensure Linux-specific instructions are provided alongside Windows ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-attach-detach-data-disk.md
...es/devtest-labs/devtest-lab-attach-detach-data-disk.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions exclusively for using the Azure portal GUI to attach or detach data disks, without mentioning or providing any examples for post-attachment steps that are required on the VM's operating system. There are no OS-specific instructions, but this omission results in a subtle bias: common post-attachment steps (such as mounting and formatting disks) are often needed, and these are typically described for Windows (using Disk Management or PowerShell) and Linux (using fdisk, mkfs, mount, etc.) in Azure VM documentation. The lack of any such guidance, especially for Linux users, may leave them without crucial information, as Windows users are more likely to be familiar with GUI-based disk management.
Recommendations
- Add a section describing post-attachment steps for both Windows and Linux VMs, including how to initialize, format, and mount the new disk.
- Provide example commands for Linux (e.g., using lsblk, fdisk, mkfs, mount) and for Windows (e.g., using Disk Management or PowerShell).
- Include links to official Azure documentation for managing disks on both Windows and Linux VMs.
- Ensure that any screenshots or instructions that are OS-specific are presented in parallel for both Windows and Linux, or clarify when steps are OS-agnostic.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-bindings-web-pubsub-output.md
...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code examples for C# and JavaScript, but for Python and PowerShell, it states that complete samples are pending. There is no evidence of explicit Windows bias such as Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented (or cross-platform) examples, especially for Python (commonly used on Linux), results in a 'missing_linux_example' bias.
Recommendations
- Add complete code samples for Python and PowerShell to ensure parity with C# and JavaScript.
- Where possible, include examples or notes that are platform-agnostic or clarify that the examples work on both Windows and Linux.
- If there are any platform-specific considerations (e.g., file paths, environment variables), document both Windows and Linux variants.
- Regularly review documentation to ensure all supported languages and platforms have up-to-date and equivalent examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-configure-cost-management.md
.../devtest-labs/devtest-lab-configure-cost-management.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not show explicit Windows bias in terms of examples or tools, as it primarily focuses on Azure portal workflows and generic Azure features. However, the only script referenced for propagating tags is not described in terms of its platform compatibility, and there are no command-line examples (for either Windows or Linux). There is a subtle bias in that the script is linked without clarifying whether Linux/bash/CLI alternatives exist, which may leave Linux users uncertain.
Recommendations
- Explicitly state whether the referenced Update-DevTestLabsTags script is platform-agnostic or provide both PowerShell and Bash/Azure CLI examples for propagating tags.
- Include Azure CLI (cross-platform) commands for tagging and cost management tasks alongside portal instructions.
- If scripts or automation are recommended, provide equivalent instructions or scripts for Linux environments (e.g., Bash, Python, or Azure CLI).
- Clarify in notes or callouts when a method is platform-independent or provide links to platform-specific guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-twitter-email.md
...n//articles/azure-functions/functions-twitter-email.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 instructions, tools, or PowerShell usage. However, it is missing any mention of Linux or cross-platform development environments, CLI usage, or deployment options outside the Azure Portal. All steps are performed via the Azure Portal UI, which is platform-agnostic, but there is no guidance for users who may prefer or require CLI-based workflows (e.g., Azure CLI, Bash, or cross-platform tools), which are especially relevant for Linux users.
Recommendations
- Add instructions for creating and deploying the Azure Function using the Azure CLI or Azure Functions Core Tools, including Bash examples.
- Include notes or sections on how to perform key steps (resource creation, function deployment, testing) from a Linux or macOS environment.
- Where code is provided, mention that the workflow is platform-agnostic, and provide links to cross-platform tools and documentation.
- If possible, provide equivalent steps for both Portal UI and CLI-based workflows, and clarify that the tutorial can be followed from any OS.
- Mention prerequisites for Linux users (e.g., installing Azure CLI, .NET SDK on Linux) if CLI or local development is covered.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-health-insights/use-containers.md
...main//articles/azure-health-insights/use-containers.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias by mentioning Windows-specific Docker configuration before Linux, specifically noting that 'On Windows, Docker must also be configured to support Linux containers.' However, all command-line examples use cross-platform tools (Docker, cURL, docker-compose) and are presented in Bash syntax, which is more common on Linux/macOS. There are no PowerShell-specific commands or Windows-only tools, and Linux is implicitly supported throughout. There are no missing Linux examples, but the initial mention of Windows could be interpreted as prioritizing Windows users.
Recommendations
- When mentioning platform-specific requirements, present Linux and Windows equally, or mention Linux first since the containers are Linux-based.
- Explicitly state that all examples are cross-platform and provide any necessary notes for both Linux and Windows users (e.g., line continuation characters, environment variable syntax).
- Consider including a brief section or note confirming that all commands work on Linux, macOS, and Windows (with WSL or Docker Desktop), and clarify any platform-specific differences.
- If referencing Windows-specific configuration, also mention any common Linux/macOS configuration steps for parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-creator-wfs.md
...s/blob/main//articles/azure-maps/how-to-creator-wfs.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only HTTP request URLs and JSON responses, without any platform-specific command-line examples (such as curl, PowerShell, or CLI). However, it also does not provide any Linux-specific examples or mention tools commonly used on Linux (e.g., curl, wget). This omission may disadvantage Linux users who expect to see command-line usage patterns relevant to their environment.
Recommendations
- Add example commands using curl (commonly available on Linux and macOS) to demonstrate how to make the HTTP GET requests.
- If providing PowerShell or Windows command-line examples in the future, ensure equivalent Linux (bash/curl) examples are included.
- Explicitly mention that the API can be accessed from any platform using standard HTTP tools, and provide sample commands for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/spatial-io-read-write-spatial-data.md
...icles/azure-maps/spatial-io-read-write-spatial-data.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is generally cross-platform and browser/JavaScript focused, but there is a subtle Windows bias in the proxy service example, which uses an '.ashx' handler (a Windows/IIS/ASP.NET-specific pattern) for the proxy endpoint. There are no explicit Linux or cross-platform proxy service examples, and the documentation does not mention Linux or non-Windows hosting environments for proxy services.
Recommendations
- Provide proxy service examples using cross-platform technologies, such as Node.js/Express, Python/Flask, or Nginx, in addition to or instead of the .ashx/IIS example.
- Explicitly mention that the proxy service can be implemented in any backend technology, not just ASP.NET/IIS.
- Add a note or example showing how to set up a simple proxy on Linux-based environments.
- Avoid using file extensions or handler names that are specific to Windows/IIS in generic code snippets.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md
...ure-netapp-files/azure-netapp-files-delegate-subnet.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for subnet delegation and does not include any command-line examples. There is no mention of Windows-specific tools or PowerShell, but there is also no coverage of CLI-based approaches (such as Azure CLI or Azure PowerShell), which are commonly used on both Windows and Linux. This omission results in a lack of parity for users who prefer or require Linux-based workflows.
Recommendations
- Add Azure CLI examples for subnet delegation, as the Azure CLI is cross-platform and widely used on Linux.
- If including PowerShell examples, ensure they are presented alongside Azure CLI examples, not before them.
- Explicitly mention that the steps can be performed via the Azure CLI or ARM templates, and provide links or code snippets.
- Review related documentation to ensure Linux and cross-platform users are equally supported in all procedural content.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/large-volumes-requirements-considerations.md
...app-files/large-volumes-requirements-considerations.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a mild 'windows_first' bias in the 'Register the feature' section, where the Azure PowerShell example is given first and in more detail, with the Azure CLI (cross-platform) option mentioned only secondarily and without a direct example. No explicit Windows-only tools or missing Linux examples are present, and Linux is referenced positively elsewhere (e.g., performance benchmarks).
Recommendations
- Provide both Azure PowerShell and Azure CLI examples side-by-side, or list the CLI example first to emphasize cross-platform parity.
- Include explicit Linux/Bash command examples where relevant, especially for feature registration and status checks.
- Ensure that all procedural steps are demonstrated with both Windows and Linux command-line tools, or clarify when a tool is cross-platform.
- Where possible, avoid presenting Windows-centric tools or patterns before their cross-platform or Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/monitor-volume-capacity.md
...articles/azure-netapp-files/monitor-volume-capacity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, but both platforms are covered with equivalent detail and screenshots. There are no exclusive Windows tools, PowerShell-heavy content, or missing Linux examples. REST API and Azure CLI sections are platform-neutral.
Recommendations
- Alternate the order of Windows and Linux sections in different documentation pages or explicitly state that the order does not imply preference.
- Consider combining Windows and Linux instructions under a unified heading with clear sub-sections, or present them in parallel to emphasize parity.
- Add a brief note at the start of the client section to clarify that both Windows and Linux are equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/monitor-azure-netapp-files.md
...icles/azure-netapp-files/monitor-azure-netapp-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains platform neutrality but contains a subtle 'windows_first' bias in the section on capacity utilization monitoring, where 'Windows or Linux clients' are mentioned, with Windows listed first. There are no explicit PowerShell-heavy examples, exclusive use of Windows tools, or missing Linux examples. However, the ordering could suggest a slight preference for Windows environments.
Recommendations
- When mentioning client platforms, alternate the order (e.g., 'Linux or Windows clients') or explicitly state that both are equally supported.
- Where command-line examples or tooling are referenced (such as PowerShell or CLI), ensure both Windows and Linux commands/examples are provided side-by-side.
- If any future sections include scripts or tools, provide equivalent instructions for both Windows (PowerShell, CMD) and Linux (Bash, shell commands).
- Consider adding a short note emphasizing cross-platform support for all monitoring features.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-federation-configuration.md
...cles/event-hubs/event-hubs-federation-configuration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but all referenced sample links point to .NET-based solutions, which are more commonly associated with Windows environments. There is no explicit mention of Linux, Linux tools, or cross-platform considerations.
Recommendations
- Include explicit notes or examples demonstrating how to run the provided .NET samples on Linux (e.g., using .NET Core/SDK on Linux).
- Add instructions or links for equivalent replication tasks using Linux-native tools or scripts (such as Bash, shell scripts, or cross-platform CLI commands).
- Clarify in the documentation that the provided samples are cross-platform if applicable, and provide any necessary prerequisites for Linux users.
- Consider providing sample code or walkthroughs in languages and frameworks popular on Linux (such as Python or Java) if possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-client.md
...brid-connections-http-requests-node-get-started-client.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation refers to running 'npm install hyco-https' from a 'Node command prompt', which is a Windows-centric term. There are no explicit Linux or cross-platform instructions or examples, and the language assumes a Windows environment by default.
Recommendations
- Replace 'Node command prompt' with 'terminal' or 'command line' to be platform-neutral.
- Explicitly mention that the instructions apply to both Windows, Linux, and macOS environments.
- If there are any platform-specific considerations (such as environment variables or file paths), provide examples for both Windows and Linux/macOS.
- Consider adding a note or section confirming that the package and code work cross-platform, and provide troubleshooting tips for Linux/macOS users if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operators-comparison.md
...s/azure-resource-manager/bicep/operators-comparison.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell for deploying Bicep files, but lists Azure PowerShell (a Windows-centric tool) before Azure CLI, which is cross-platform. No Linux-specific tools or shell examples are provided, and there is an implicit prioritization of Windows tooling in the introductory guidance.
Recommendations
- List Azure CLI before Azure PowerShell when describing deployment options, as Azure CLI is cross-platform and more inclusive for Linux users.
- Explicitly mention that both Azure CLI and Azure PowerShell are available on Windows, Linux, and macOS to avoid the perception of Windows bias.
- Provide example commands for deploying Bicep files using Azure CLI in both Windows (cmd/PowerShell) and Linux/macOS (bash) shells.
- If referencing Visual Studio Code, note that it is available on all major platforms, and consider linking to platform-specific setup guides if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operators-numeric.md
...cles/azure-resource-manager/bicep/operators-numeric.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions 'Azure CLI or Azure PowerShell' for deploying Bicep files, listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, but does not clarify cross-platform usage or provide Linux-specific guidance. There are no explicit Linux examples, but the bias is mild and limited to tool mention order.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
- Consider listing Azure CLI before Azure PowerShell to avoid implying a Windows-first workflow.
- Add a note or section explicitly stating that all examples and deployment steps work on Linux, macOS, and Windows when using Azure CLI.
- If referencing PowerShell, mention that PowerShell Core is available cross-platform, or provide Bash equivalents where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operators-logical.md
...cles/azure-resource-manager/bicep/operators-logical.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell for deploying Bicep files, but lists Azure PowerShell (a Windows-centric tool) before Azure CLI (which is cross-platform). No explicit Linux-only or Windows-only examples are given, but the ordering subtly prioritizes Windows tooling. No Linux-specific tools or shell examples are provided.
Recommendations
- List Azure CLI before Azure PowerShell when describing deployment options, as Azure CLI is cross-platform and more inclusive for Linux users.
- Explicitly mention that all examples work on Linux, macOS, and Windows when using Azure CLI.
- Consider including a Linux shell (bash) example for deploying Bicep files, to demonstrate parity.
- If referencing PowerShell, clarify that it is available cross-platform, or provide a bash equivalent for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/resource-declaration.md
...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for querying supported resource locations, but the PowerShell example is listed first. There are no exclusive Windows tools or patterns, and Linux/CLI parity is maintained in the examples provided. However, the ordering may subtly prioritize Windows users by placing PowerShell before CLI.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across documentation pages to avoid implicit prioritization.
- Explicitly state that both PowerShell and Azure CLI are cross-platform, and that users can choose either based on their environment.
- Consider providing Bash or shell script examples where relevant, especially for scripting scenarios.
- If possible, add a short note or tab for Linux/macOS users, clarifying that Azure CLI is fully supported on those platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authorize-access-event-hubs.md
...in//articles/event-hubs/authorize-access-event-hubs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by linking only to .NET (C#) Azure RBAC samples in the 'Next steps' section, which are typically associated with Windows environments. There are no explicit Linux, Bash, or cross-platform code samples or references, and no mention of Linux command-line tools or patterns. However, the main content is otherwise platform-neutral and does not include PowerShell-specific instructions or Windows-only tools.
Recommendations
- Include links to RBAC sample code in other languages/platforms (e.g., Python, Java, JavaScript) that are commonly used on Linux.
- Add explicit mention of cross-platform or Linux-compatible tools and workflows where relevant.
- Ensure that any referenced sample repositories or code snippets include Linux/Bash examples alongside Windows/.NET ones.
- Consider providing a table or section listing sample resources for multiple platforms to improve parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/create-private-link-access-portal.md
...anager/management/create-private-link-access-portal.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to create a private link using the Azure portal, with all instructions and screenshots focused on the graphical user interface. There are no command-line examples provided for any platform (Windows, Linux, or macOS), but the lack of CLI or scripting alternatives can be considered a bias, as many Linux users prefer or require command-line instructions. There is no explicit Windows bias in terms of mentioning Windows tools or PowerShell, but the absence of Linux-friendly alternatives (such as Azure CLI or Bash scripts) results in missing Linux parity.
Recommendations
- Add Azure CLI examples for each step, showing how to create and configure private links and private endpoints from the command line.
- Include Bash script snippets for automating the process, which would benefit Linux and macOS users.
- Where possible, provide PowerShell examples as well, but ensure they are presented alongside (not before) Azure CLI/Bash examples to maintain parity.
- Explicitly mention that all steps can be performed via the Azure CLI and provide a link to relevant CLI documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/manage-resource-groups-portal.md
...ce-manager/management/manage-resource-groups-portal.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes managing Azure resource groups using the Azure portal, with no mention of command-line tools or scripts. There are no examples or references to Windows-specific tools (such as PowerShell), but also no mention of cross-platform CLI tools like Azure CLI or Bash scripting. This omission results in a lack of parity for Linux users who commonly use CLI-based workflows.
Recommendations
- Add parallel instructions and examples for managing resource groups using the Azure CLI, which is cross-platform and widely used on Linux.
- Include command-line examples for creating, listing, and deleting resource groups, and show both Bash and PowerShell syntax where appropriate.
- Reference documentation for both Azure CLI and Azure PowerShell, making it clear that both are supported and providing links to relevant guides.
- Ensure that screenshots and walkthroughs are not exclusively portal-based, but also demonstrate equivalent command-line workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/manage-resources-cli.md
...re-resource-manager/management/manage-resources-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely cross-platform, using Azure CLI and Bash-style scripting, which works on both Linux and Windows. However, there is a notable instance of Windows-first bias: the link to the ARM template Quickstart specifically references Visual Studio Code with a PowerShell tab, suggesting a Windows-centric workflow before any Linux alternative. No explicit Linux examples are missing, but the reference to PowerShell in the context of template creation may imply a preference for Windows tools.
Recommendations
- When referencing external guides (such as the Quickstart for ARM templates), ensure that Linux/bash instructions are mentioned alongside or before PowerShell/Windows instructions.
- If linking to a guide with tabs for different platforms (e.g., PowerShell, Bash), default to the Bash or cross-platform tab, or mention both options explicitly.
- Review all external links and ensure parity in instructions for Linux and Windows users.
- Consider adding a note clarifying that all CLI examples are cross-platform and work on both Linux and Windows, to reinforce platform neutrality.