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 1601-1625 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/nfs-access-control-lists.md
...rticles/azure-netapp-files/nfs-access-control-lists.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by referencing Windows concepts and documentation before Linux equivalents, especially in the introduction where Windows ACLs and NTFS permissions are mentioned first and linked. Additionally, links to Windows-specific documentation (e.g., Microsoft's Windows ACLs and ACEs) are provided, while Linux/NFS documentation is referenced later or not at all in those sections. However, the majority of the technical content, examples, and command-line usage is Linux/NFS-centric, with extensive use of Linux tools and commands.
Recommendations
- When introducing NFSv4.x ACLs, reference Linux/NFS documentation and man pages (e.g., nfs4_acl(5), nfs4_getfacl(1)) alongside or before Windows equivalents.
- Provide links to relevant Linux/NFS documentation (such as kernel.org, die.net, or man7.org) for ACLs and ACEs, not just Windows documentation.
- Consider reordering introductory comparisons to mention Linux/NFS ACLs first, or present both Windows and Linux perspectives in parallel.
- If referencing Windows tools or concepts, ensure Linux equivalents are mentioned with equal prominence and clarity.
- Continue to provide Linux/NFS command examples, as is already done well throughout the document.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/snapshots-restore-file-client.md
...es/azure-netapp-files/snapshots-restore-file-client.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux (NFS) and Windows (SMB) client instructions for restoring files from snapshots, with clear parity in basic restore steps. However, the Windows section includes an additional method (using the 'Previous Versions' tab in Properties) that leverages Windows-specific GUI tools, while no comparable advanced or GUI-based Linux method (such as using file managers or desktop environments) is mentioned. Additionally, the Windows section is more visually detailed with multiple screenshots, while the Linux section is limited to command-line examples.
Recommendations
- Add advanced or GUI-based Linux restore methods (e.g., using Nautilus, Dolphin, or other file managers to access .snapshot directories) to match the Windows 'Previous Versions' approach.
- Include screenshots for the Linux section to provide visual parity with the Windows instructions.
- If possible, mention or link to third-party tools or desktop environment features on Linux that can facilitate snapshot browsing and file restoration.
- Ensure that any advanced restore features highlighted for Windows are also investigated and documented for Linux clients, or explicitly state if such features are unavailable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/solutions-benefits-azure-netapp-files-sql-server.md
...es/solutions-benefits-azure-netapp-files-sql-server.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively discusses SQL Server deployment, which is traditionally Windows-centric, and all examples, benchmarks, and tools referenced (such as perfmon and SSB) are focused on SQL Server on Azure VMs, with no mention of Linux-based SQL Server deployments or Linux tools. There are no examples, cost analyses, or performance discussions for SQL Server on Linux, nor are any Linux-native monitoring or benchmarking tools referenced.
Recommendations
- Include explicit mention of SQL Server on Linux, which is supported by Microsoft, and discuss any differences or considerations when using Azure NetApp Files.
- Provide cost and performance examples for SQL Server running on Linux-based Azure VMs, alongside the current Windows examples.
- Reference or provide examples using Linux-native monitoring and benchmarking tools (e.g., iostat, sar, vmstat, or Linux equivalents to perfmon) for performance measurement.
- If SSB or other tools are cross-platform, clarify their usage on Linux and provide Linux command-line examples.
- Ensure that solution architectures and next steps include links or guidance for both Windows and Linux SQL Server deployments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/volume-hard-quota-guidelines.md
...les/azure-netapp-files/volume-hard-quota-guidelines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the order and depth of examples. In the VM-level monitoring section, Windows instructions and screenshots are presented before Linux, with more detailed step-by-step guidance and multiple screenshots for Windows (Explorer, dir command), while Linux receives a single command-line example. In the CLI/PowerShell section, PowerShell is visually emphasized in screenshots, and while Azure CLI is mentioned, the visual examples are all PowerShell-based. There are no Linux-specific CLI examples or screenshots, and no mention of Linux shell environments in the context of automation or scripting.
Recommendations
- Present Linux and Windows examples in parallel or alternate the order to avoid always placing Windows first.
- Provide equivalent depth for Linux: include screenshots of Linux file managers (e.g., Nautilus, Dolphin) showing volume properties, not just command-line output.
- In CLI/PowerShell sections, include explicit Linux shell (bash) examples and screenshots, not just PowerShell.
- Clarify that Azure CLI commands can be run from both Windows and Linux environments, and provide sample commands in both bash and PowerShell syntax.
- Where automation is discussed, mention Linux scripting options (e.g., bash scripts, cron jobs) alongside PowerShell.
- Ensure that all tooling and operational guidance is equally accessible and illustrated for both Windows and Linux administrators.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/move-across-regions.md
...blob/main//articles/azure-relay/move-across-regions.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure Portal (web UI) for all steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While this avoids explicit Windows-only tools, it implicitly favors Windows users by referencing Windows-centric concepts (such as WCF relays) and omitting Linux-friendly automation or CLI workflows. There are no examples or instructions for performing the same tasks using cross-platform tools like Azure CLI or ARM templates via command line, which are commonly used on Linux and macOS.
Recommendations
- Add step-by-step instructions for exporting, editing, and deploying ARM templates using Azure CLI commands (az group export, az deployment group create, etc.), which work on all platforms.
- Include examples for deleting resources using Azure CLI or REST API, not just the portal.
- Mention that all steps can be performed from Linux, macOS, or Windows using the Azure CLI, and provide sample commands.
- If referencing WCF relays (a Windows-centric technology), clarify their relevance for cross-platform users or provide context for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md
...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes a Windows development environment by instructing users to create a console application using Visual Studio and referencing the .NET Framework, both of which are primarily associated with Windows. There are no instructions or examples for creating or running the application on Linux (e.g., using .NET Core/SDK CLI or Visual Studio Code), nor is there mention of cross-platform development tools or workflows.
Recommendations
- Provide alternative instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') for cross-platform compatibility.
- Mention that the Microsoft.Azure.Relay NuGet package can be added via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay') for non-Windows environments.
- Clarify whether the code is compatible with .NET Core/.NET 5+ and, if so, update references from '.NET Framework' to '.NET' or provide both options.
- Include guidance for Linux and macOS users, such as using Visual Studio Code or JetBrains Rider, and terminal commands for building and running the application.
- Explicitly state any platform limitations or requirements if the code is Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of Visual Studio and the .NET Framework, both of which are primarily associated with Windows development. All instructions reference Visual Studio-specific workflows (such as right-clicking the project and using the Visual Studio NuGet Package Manager), and there is no mention of cross-platform alternatives (e.g., using the .NET CLI or Visual Studio Code). There are no Linux-specific instructions or examples, nor is there guidance for users developing on macOS or Linux.
Recommendations
- Add instructions for creating the console application using the .NET CLI (e.g., 'dotnet new console') to support Linux and macOS users.
- Include steps for adding NuGet packages via the CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
- Mention that the code is compatible with .NET Core/.NET 5+ and can be developed using Visual Studio Code or other cross-platform editors.
- Provide explicit notes or sections for Linux/macOS users, including any environment-specific considerations.
- Avoid assuming Visual Studio as the only development environment; present it as one option among several.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md
...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of Visual Studio (a primarily Windows IDE) and does not provide instructions or examples for developing or running the .NET applications on Linux or macOS. There are no mentions of cross-platform .NET development tools (such as VS Code or the dotnet CLI), nor are there any Linux-specific instructions for running or building the applications.
Recommendations
- Include instructions for setting up the development environment on Linux and macOS, such as using VS Code or JetBrains Rider, and installing the .NET SDK via package managers.
- Provide examples for building and running the applications using the dotnet CLI, which is cross-platform.
- Explicitly state that the tutorial works on Windows, Linux, and macOS, and mention any platform-specific considerations.
- If any steps are different on Linux (e.g., terminal commands, file paths), provide those instructions alongside the Windows ones.
- Add screenshots or terminal output examples from Linux/macOS environments to demonstrate parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-relay/relay-port-settings.md
...blob/main//articles/azure-relay/relay-port-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows Communication Foundation (WCF) Relays and their associated .NET bindings, which are Windows-centric technologies. There are no examples, guidance, or references for Linux environments or cross-platform alternatives. The documentation assumes the use of Windows tools and frameworks, omitting Linux-compatible approaches or examples.
Recommendations
- Include information about using Azure Relay from Linux environments, such as with cross-platform .NET (Core/5/6+), Java, Node.js, or Python SDKs.
- Provide examples or references for configuring required ports on Linux systems (e.g., using iptables, ufw, or firewalld).
- Mention any cross-platform alternatives to WCF or clarify the platform limitations of the described bindings.
- Add explicit notes or links for Linux users to relevant Azure Relay documentation or SDKs.
- Ensure that port configuration instructions are not limited to Windows-specific tools or frameworks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/bicep-functions-deployment.md
...e-resource-manager/bicep/bicep-functions-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing the PowerShell command (Get-AzEnvironment) before the cross-platform Azure CLI equivalent (az cloud list) when describing how to list registered environments. No Linux-specific examples or tools are mentioned, and the PowerShell cmdlet is given equal prominence to the CLI, which is more commonly used on Linux/macOS. No explicit Windows-only tools or patterns are present, but the ordering and inclusion of PowerShell may subtly prioritize Windows users.
Recommendations
- List the Azure CLI (az cloud list) command before the PowerShell cmdlet, as the CLI is cross-platform and more widely used outside Windows.
- Clarify that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to avoid implying PowerShell is Windows-only.
- Consider including explicit Linux/macOS terminal usage notes or examples where relevant, to reinforce cross-platform parity.
- If referencing PowerShell, note that PowerShell Core is available cross-platform, or provide a link to installation instructions for non-Windows systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-to-management-group.md
...e-resource-manager/bicep/deploy-to-management-group.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files at the management group scope. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after the CLI example. There are no explicit Linux-specific instructions or examples, and no mention of Bash scripting or Linux shell patterns. The documentation does not mention any platform-specific prerequisites or differences, but the inclusion of PowerShell as a primary example may signal a bias toward Windows users.
Recommendations
- Clearly indicate that Azure CLI is fully cross-platform and works on Windows, Linux, and macOS.
- Consider presenting Azure CLI examples first, as it is the most platform-agnostic tool.
- Add explicit Bash shell examples or notes for Linux users where relevant (e.g., environment variables, file paths).
- Clarify that PowerShell Core is available cross-platform, but note any differences if applicable.
- Include a brief section or note on running these commands in Linux/macOS environments, such as using Azure CLI in Bash or Zsh.
- Avoid implying that PowerShell is the default or preferred method unless there is a technical reason.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-cloud-shell.md
...les/azure-resource-manager/bicep/deploy-cloud-shell.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Bash (Linux) and PowerShell (Windows) options for Cloud Shell, but PowerShell is mentioned alongside Bash in the UI steps and is given its own example section. The 'Next steps' section lists the PowerShell documentation link after the CLI (which is cross-platform), but there is no explicit Linux-specific guidance or troubleshooting. The overall structure is relatively balanced, but there is a slight tendency to highlight PowerShell and Windows-centric patterns.
Recommendations
- Explicitly state that both Bash and PowerShell are available in Cloud Shell, and clarify that Bash is typically used for Linux/macOS users.
- Provide a brief note on the equivalence of Azure CLI commands in Bash and PowerShell, and clarify that Azure CLI is cross-platform.
- Include troubleshooting tips or notes for Linux users (e.g., file path differences, case sensitivity).
- Ensure that examples and further reading links are balanced between PowerShell and Bash/Azure CLI, and consider adding a 'Linux tips' or 'Bash tips' section if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-to-tenant.md
...icles/azure-resource-manager/bicep/deploy-to-tenant.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands and role assignment, but PowerShell is often presented first or equally, which can be interpreted as a slight Windows bias. There are no Linux-specific instructions or examples, and no mention of running these commands in a Linux environment or using Bash. However, Azure CLI is cross-platform and is included, which helps mitigate the bias. There are no exclusive references to Windows-only tools, but the presence and order of PowerShell examples may suggest a preference for Windows users.
Recommendations
- Ensure that Azure CLI examples are always presented before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and can be run from Bash or other shells.
- Where PowerShell examples are given, consider also providing Bash or shell script equivalents for common tasks (e.g., role assignment), or clarify that Azure CLI is the recommended approach for Linux.
- Add a note or section about running these commands in Cloud Shell, which is platform-agnostic.
- Review all examples and instructions to ensure there are no implicit assumptions about the user's operating system.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-to-resource-group.md
...ure-resource-manager/bicep/deploy-to-resource-group.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but consistently lists Azure CLI (which is cross-platform) first, followed by Azure PowerShell (which is traditionally Windows-centric, though now available cross-platform). There are no explicit Linux-only or Windows-only commands, but the presence of PowerShell examples and references may be perceived as Windows-leaning, especially since no Bash or Linux-native shell examples are provided. There is no mention of Windows-specific tools, but the documentation could better highlight Linux parity by including Bash or shell script examples and clarifying cross-platform compatibility.
Recommendations
- Explicitly state that Azure CLI commands work identically on Windows, Linux, and macOS.
- Add Bash or shell script examples for common deployment scenarios to demonstrate Linux parity.
- Clarify that Azure PowerShell is available cross-platform, and provide installation links for Linux/macOS.
- Consider including a table or section comparing deployment options across platforms (Windows, Linux, macOS).
- Avoid implying PowerShell is the default or preferred method unless justified by technical reasons.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/bicep-functions-resource.md
...ure-resource-manager/bicep/bicep-functions-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias in the section describing how to enumerate available 'list' operations for resources. The PowerShell (Windows-centric) example is presented before the Azure CLI example, and the PowerShell cmdlet is specifically highlighted. No Linux-specific or cross-platform shell examples (such as Bash or scripting with jq) are provided. However, the majority of the documentation is platform-agnostic, focusing on Bicep syntax and Azure concepts.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more widely used on Linux and macOS.
- Explicitly mention that both Azure CLI and PowerShell are supported on all major platforms, but Azure CLI is the default for Linux/macOS users.
- Where possible, provide Bash or shell scripting examples (e.g., using jq to parse JSON output from Azure CLI) to further support Linux users.
- Add a note or section clarifying that all command-line examples are cross-platform unless otherwise stated, and provide links to installation instructions for both Azure CLI and PowerShell.
- Consider including a table or callout that summarizes equivalent commands in Azure CLI, PowerShell, and Bash for common operations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-to-subscription.md
...azure-resource-manager/bicep/deploy-to-subscription.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files at the subscription scope. However, the PowerShell example is given equal prominence as the Azure CLI example, and there is no explicit mention of Linux or Bash scripting. The CLI example is cross-platform, but the PowerShell example (and references to Azure PowerShell) may be perceived as Windows-centric, especially since PowerShell is traditionally associated with Windows environments. There are no Linux-specific examples or explicit notes about using Bash or other shells.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and that the CLI example is cross-platform.
- Consider providing a Bash shell example or clarifying that the Azure CLI example is intended for Bash (Linux/macOS) and CMD/PowerShell (Windows) environments.
- Add a note that Azure PowerShell is available cross-platform, but is most commonly used in Windows environments, and provide guidance for Linux users if needed.
- Ensure that references to deployment commands and further reading include links to Linux/Bash-specific guidance where available.
- If possible, include a table or section summarizing command usage across different operating systems to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deploy-cli.md
...n//articles/azure-resource-manager/bicep/deploy-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific shells (PowerShell and cmd) before or alongside Linux/Bash, and by providing explicit guidance for Windows users in several places. While the main examples use Bash (which is cross-platform), there are multiple notes and code snippets specifically for PowerShell/cmd users, sometimes with more detail than for Linux users. There are no Linux tools or patterns missing, but the documentation tends to mention Windows environments and their requirements prominently.
Recommendations
- Ensure that all examples and notes are equally detailed for both Bash (Linux/macOS) and PowerShell/cmd (Windows).
- Where platform-specific syntax is required, present Bash (Linux/macOS) and PowerShell/cmd (Windows) examples side-by-side, rather than referencing Windows shells as an afterthought.
- Avoid phrasing that centers Windows as the default, such as 'If you're using PowerShell or cmd...'—instead, use neutral language like 'In Bash (Linux/macOS): ... In PowerShell (Windows): ...'.
- Explicitly state that Bash is available on Windows (via WSL or Git Bash) to encourage cross-platform parity.
- Consider adding a table or section summarizing syntax differences across platforms for common commands and parameter passing.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/data-types.md
...n//articles/azure-resource-manager/bicep/data-types.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, but there is a notable Windows bias in the 'Integers' section, where PowerShell is mentioned as the example deployment tool that limits integer ranges. No equivalent mention is made of Linux or cross-platform tools (such as Azure CLI). This may give the impression that Windows/PowerShell is the primary or default environment for Bicep deployments.
Recommendations
- When discussing deployment tools and their limitations (such as integer range), mention both PowerShell and Azure CLI, and clarify which platforms they run on.
- Provide examples or notes for both Windows and Linux/macOS users where tool-specific behavior is relevant.
- Avoid referencing only Windows tools or patterns unless they are truly unique to Windows; otherwise, present cross-platform or Linux alternatives alongside.
- Consider adding a brief section or note about cross-platform support for Bicep and its tooling, including links to installation or usage instructions for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/export-bicep-portal.md
...es/azure-resource-manager/bicep/export-bicep-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references both Azure CLI and Azure PowerShell for exporting ARM JSON templates, but consistently lists Azure PowerShell (a Windows-centric tool) alongside or before Azure CLI. There are no explicit Linux-specific instructions or examples, and the workflow assumes the Azure portal (web UI), which is cross-platform, but the command-line alternatives do not highlight Linux parity or provide bash-specific examples.
Recommendations
- When listing command-line tools, mention Azure CLI before Azure PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly state that Azure CLI commands work on Linux/macOS/Windows, and provide example commands in bash syntax.
- Include a note or section for Linux/macOS users, clarifying that all export and decompilation steps are supported on those platforms.
- If referencing PowerShell, clarify that PowerShell Core is cross-platform, or provide both Windows PowerShell and bash/Azure CLI examples where appropriate.
- Consider adding a table or quick-reference showing parity of export options across Windows, Linux, and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md
...ep/linter-rule-admin-username-should-not-be-literal.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses examples and terminology relevant to Windows environments (e.g., 'administrator', 'adminUsername'), and references Azure VM resource types that default to Windows conventions. There are no examples or mentions of Linux admin usernames (such as 'azureuser' or 'root'), nor any Linux-specific guidance, which may lead users to assume the rule or guidance is only relevant for Windows VMs.
Recommendations
- Include examples that use Linux-typical admin usernames (e.g., 'azureuser', 'root') to demonstrate the rule's applicability to Linux VMs.
- Explicitly mention that the linter rule applies to both Windows and Linux virtual machines.
- Add a section or note clarifying any differences in admin username conventions between Windows and Linux VM deployments.
- Provide at least one example resource definition for a Linux VM, showing the adminUsername parameterization.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operator-safe-dereference.md
...re-resource-manager/bicep/operator-safe-dereference.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references Azure PowerShell and Visual Studio Code (a cross-platform tool, but often associated with Windows) before mentioning Azure CLI, and does not provide any Linux-specific instructions or examples. The deployment instructions mention Azure PowerShell before Azure CLI, which may suggest a Windows-first approach. There are no explicit Linux or bash shell examples, and no mention of Linux-native tooling.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that all examples work on Linux, macOS, and Windows, and provide bash shell equivalents where relevant.
- Include instructions or links for deploying Bicep files using bash or zsh shells on Linux.
- If referencing Visual Studio Code, clarify its cross-platform nature and consider mentioning other editors or command-line workflows common on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/quickstart-loops.md
...icles/azure-resource-manager/bicep/quickstart-loops.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and cleanup, but consistently lists PowerShell as a primary or parallel method. Visual Studio Code is recommended as the editor, but no mention is made of Linux-specific editors or shell environments. There is no explicit Windows-only tooling, but the documentation implicitly assumes familiarity with PowerShell and Windows-centric workflows, and does not address Linux shell nuances or alternative editors.
Recommendations
- Explicitly state that all CLI examples work on Linux, macOS, and Windows, and clarify any OS-specific differences if present.
- Add Linux/macOS-specific shell examples (e.g., bash/zsh) where variable assignment syntax differs from PowerShell.
- Mention alternative editors commonly used on Linux (e.g., Vim, Emacs, nano) in the prerequisites, or clarify that Visual Studio Code is cross-platform.
- If PowerShell is mentioned, also mention bash or sh as alternatives for Linux/macOS users.
- Include notes or callouts for any commands or steps that may behave differently on Linux versus Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/visual-studio-code.md
...les/azure-resource-manager/bicep/visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform neutrality by focusing on Visual Studio Code and Azure CLI, but there are several instances where Windows-specific tools (Azure PowerShell) are mentioned alongside or before cross-platform alternatives. In command examples, Azure CLI and Azure PowerShell are both provided, but PowerShell is sometimes listed first or equally, which may subtly prioritize Windows users. There are no explicit Linux-only examples or guidance, and no mention of Linux-specific workflows or shell environments.
Recommendations
- When listing command-line options, consistently present Azure CLI (which is cross-platform) before Azure PowerShell, as CLI is more commonly used on Linux and macOS.
- Explicitly mention that all instructions and examples work on Linux, macOS, and Windows unless otherwise noted.
- Where keyboard shortcuts are referenced (e.g., Ctrl+Shift+P), include macOS/Linux equivalents (e.g., Cmd+Shift+P for macOS).
- Add a brief section or note confirming that the Bicep extension and all described features are fully supported on Linux and macOS.
- If referencing the Azure PowerShell module, clarify that it is available cross-platform, but that Azure CLI is often the default on Linux.
- Consider including at least one screenshot or workflow example from a Linux desktop environment to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/custom-providers/tutorial-custom-providers-function-setup.md
...-providers/tutorial-custom-providers-function-setup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes use of the Azure Portal and .NET/C# tooling, with no mention of Linux-specific workflows, CLI alternatives, or cross-platform development environments. There are no examples or instructions for Linux users, such as using Azure CLI, VS Code, or command-line package management, and the default project setup is oriented toward Windows-centric .NET development.
Recommendations
- Include instructions for setting up Azure Functions using the Azure CLI and/or PowerShell Core, which are cross-platform.
- Provide examples for creating and configuring the function app using command-line tools available on Linux (e.g., Azure CLI, dotnet CLI).
- Mention and demonstrate how to edit and manage function apps using VS Code or other cross-platform editors, not just the Azure Portal.
- Clarify that the .NET Core SDK and Azure Functions Core Tools are available on Linux and provide installation steps for Linux users.
- Add explicit notes or sections for Linux/macOS users, including any differences in workflow or requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/managed-applications/create-storage-customer-managed-key.md
...ed-applications/create-storage-customer-managed-key.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI commands for building the Bicep template, but PowerShell is listed first and is visually emphasized. There are no explicit Linux-only examples, and the use of Visual Studio Code as the recommended editor is platform-neutral but may be more familiar to Windows users. The documentation does not provide any Linux-specific instructions, troubleshooting, or shell (bash) examples, and does not mention platform differences that may affect Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax where relevant.
- Include Linux-specific notes or troubleshooting tips if there are any platform-specific considerations.
- Consider adding a section or callout for Linux users, confirming that all steps are cross-platform unless otherwise noted.
- Where possible, provide examples using bash scripting for automation, not just PowerShell.