Azure Resource Manager
1002
Total Pages
808
Linux-Friendly Pages
194
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
492 issues found
Showing 26-50 of 492 flagged pages
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/install.md
.../main/articles/azure-resource-manager/bicep/install.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation shows moderate Windows bias. Visual Studio (Windows-only) is presented as a primary authoring tool alongside Visual Studio Code, and PowerShell/Windows installer/Windows package managers (Chocolatey, Winget) are described in greater detail and with more installation options than their Linux/macOS equivalents. Windows-specific tools and patterns (e.g., PowerShell scripts, registry edits, Windows environment variables) are used and described in depth, while Linux and macOS installation instructions are more concise and less varied. In several sections, Windows options are listed before Linux/macOS, and PowerShell is the only scripting language shown for manual installation on Windows.
Recommendations
- Present Linux and macOS installation options before or alongside Windows options in all lists and tables to avoid 'windows_first' ordering.
- Expand Linux and macOS installation sections to include more package manager options (e.g., apt, yum, snap for Linux), mirroring the variety offered for Windows (e.g., Chocolatey, Winget).
- Provide Bash or shell script equivalents for all PowerShell examples, especially for manual installation and PATH modification.
- Where possible, use cross-platform language and avoid Windows-specific terminology (e.g., use 'home directory' instead of '%UserProfile%').
- Highlight cross-platform editors and tools (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio).
- Ensure troubleshooting and advanced sections include Linux/macOS-specific guidance, not just Windows/PowerShell.
Create Pull Request
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/installation-troubleshoot.md
...re-resource-manager/bicep/installation-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools and patterns (e.g., 'where bicep', %USERPROFILE% paths, PATH variable instructions for Windows only), omitting Linux/macOS equivalents (such as 'which bicep', $HOME/.azure/bin), and not providing cross-platform guidance. There are no Linux or macOS-specific troubleshooting steps or examples.
Recommendations
- Include Linux/macOS equivalents for all command-line instructions (e.g., use 'which bicep' for Linux/macOS, and specify the typical Azure CLI Bicep path as $HOME/.azure/bin).
- Provide instructions for modifying the PATH environment variable on Linux/macOS (e.g., editing .bashrc, .zshrc, or .profile).
- Clearly label platform-specific steps and provide parallel instructions for each supported OS.
- Add screenshots or descriptions relevant to Linux/macOS environments where applicable.
- Review all sections to ensure Linux/macOS users are equally supported in troubleshooting scenarios.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/key-vault-parameter.md
...es/azure-resource-manager/bicep/key-vault-parameter.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all command-line operations, but PowerShell examples are consistently listed after Azure CLI. However, there is a notable reference to a Windows-specific scenario ('WinRM on a Windows VM') in the introduction, with no equivalent Linux example or mention. The documentation also references PowerShell and .NET in the 'More information' section before mentioning Node.js, and does not provide any Linux-specific guidance or examples, such as using Bash scripting or Linux-based deployment scenarios.
Recommendations
- Add Linux-focused examples or references, such as deploying to Linux VMs or using Linux-specific tools/scripts.
- Include a Linux VM quickstart template reference alongside the Windows VM example in the introduction.
- Ensure parity in the order of tool presentation (e.g., alternate between Azure CLI and PowerShell, or mention Bash scripting where relevant).
- Expand the 'More information' section to include examples using Bash, Python, or other common Linux tools.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where possible, provide screenshots or walkthroughs using a Linux shell environment.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides deployment guidance and troubleshooting specifically for Azure PowerShell commands (e.g., New-AzDeployment), which are most commonly used on Windows. There are no examples or mentions of cross-platform tools such as Azure CLI, nor are there Linux-specific deployment patterns or considerations. The only deployment tool discussed is PowerShell, and it is mentioned before any Linux-equivalent tools (which are not mentioned at all).
Recommendations
- Add equivalent Azure CLI (az deployment ...) examples and guidance, which is cross-platform and widely used on Linux and macOS.
- Mention that Azure CLI does not have the same parameter name conflict as PowerShell, or document any differences.
- Where PowerShell-specific advice is given, provide parallel instructions for Bash/Azure CLI users.
- Consider reordering or balancing the documentation so that cross-platform tools are mentioned alongside or before Windows-specific tools.
- Explicitly state that the guidance applies to all platforms, and clarify any platform-specific differences.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate-blueprint.md
...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell-based export instructions and linking to a PowerShell-specific guide for exporting blueprint definitions. There is no mention of Linux or cross-platform tools (such as Azure CLI) for the export step, and no Linux-specific or cross-platform command examples are provided.
Recommendations
- Provide Azure CLI examples for exporting blueprint definitions, as Azure CLI is cross-platform and widely used on Linux.
- Update links and references to include both PowerShell and Azure CLI documentation, or clarify that the instructions apply to all platforms.
- Explicitly mention that migration steps can be performed on Linux, macOS, and Windows, and provide equivalent commands or guidance for non-Windows environments.
- Ensure that all code samples and instructions are platform-agnostic or have clear alternatives for Linux users.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/migrate.md
.../main/articles/azure-resource-manager/bicep/migrate.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and workflows (such as Azure PowerShell and Visual Studio Code) are mentioned alongside or before cross-platform options, and there are no explicit Linux-specific examples or CLI instructions. Keyboard shortcuts are provided for Windows and macOS, but Linux is only mentioned as sharing the Windows shortcut. There is no mention of Linux-native editors or shell environments, and examples using Azure CLI are not prioritized over PowerShell.
Recommendations
- Provide explicit Linux examples and instructions, especially for command-line operations (e.g., show Azure CLI commands before PowerShell).
- Include Linux-native editor alternatives (such as Vim, Emacs, or JetBrains IDEs) or at least acknowledge their use.
- When referencing keyboard shortcuts, clarify Linux-specific variations if they exist, and avoid grouping Linux with Windows unless they are truly identical.
- Ensure that all tools and workflows mentioned (such as exporting resources or running deployments) include parity for Linux users, with clear instructions.
- Where possible, use Azure CLI as the primary example, as it is cross-platform, and mention PowerShell as an alternative.
- Add a section or callout highlighting any platform-specific limitations or differences, so Linux users are aware of potential issues.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/msbuild-bicep-file.md
...les/azure-resource-manager/bicep/msbuild-bicep-file.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias. Windows/PowerShell commands and paths are used exclusively or appear first in nearly all examples, including project setup, directory navigation, and build instructions. Linux and macOS equivalents are rarely mentioned, and when present (e.g., in package references), they are not shown in code or command-line examples. The use of Windows-style paths (C:\, backslashes) and exclusive reliance on PowerShell for shell commands further reinforces the bias. There are no bash or Linux shell equivalents for common tasks such as directory creation, file deletion, or running MSBuild/dotnet commands.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, using bash syntax and POSIX-style paths (e.g., /home/user/msBuildDemo).
- Show how to run MSBuild and dotnet commands on Linux/macOS, including any differences in command names (e.g., 'msbuild' vs 'MSBuild.exe').
- Include Linux/macOS versions of project file snippets, especially for the <PackageReference> to Azure.Bicep.CommandLine.linux-x64 and path examples.
- When referencing environment variables or file paths, use cross-platform conventions or show both Windows and Linux/macOS variants.
- Add a tabbed or side-by-side format for all code and shell examples, allowing users to select their OS.
- For cleanup instructions, provide the equivalent bash command (e.g., 'rm -rf ~/msBuildDemo') alongside the PowerShell example.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/modules.md
.../main/articles/azure-resource-manager/bicep/modules.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation shows evidence of Windows bias primarily in the discussion of deployment tools and patterns. Azure PowerShell is mentioned before Azure CLI and the Azure portal when discussing deployment options for template specs. Additionally, PowerShell scripts are referenced as an example of artifacts that can be embedded in Bicep modules, with no mention of Bash or shell scripts. There are no explicit Linux or cross-platform command-line examples, and the only scripting language referenced is PowerShell.
Recommendations
- When listing deployment tools, mention Azure CLI before or alongside Azure PowerShell, and provide parity in examples.
- When referencing script artifacts, include Bash or shell scripts as examples alongside PowerShell scripts.
- Add explicit Azure CLI examples where deployment commands are discussed, especially for Linux users.
- Review the order of tool mentions to avoid always listing Windows tools first.
- Consider including a section or note about cross-platform compatibility and best practices for Linux/macOS users.
Azure Resource Manager
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where Azure PowerShell and Visual Studio Code (a tool often associated with Windows) are mentioned before or instead of Linux-native alternatives. There are no explicit Linux CLI examples, and the guidance to use Azure CLI is coupled with Azure PowerShell, with no Linux-specific instructions or parity. The Bicep code example itself is platform-neutral, but the surrounding guidance assumes a Windows-centric workflow.
Recommendations
- Provide explicit Linux and macOS instructions for deploying Bicep files, including terminal commands using Azure CLI.
- Mention and link to Linux-native editors (such as Vim, Emacs, or VS Code on Linux) for creating Bicep files.
- Ensure that Azure CLI (which is cross-platform) is given equal or higher prominence than Azure PowerShell in deployment instructions.
- Add a section or note clarifying that all examples and tools are available and supported on Linux, with links to relevant installation guides.
- Where possible, include screenshots or terminal output from Linux environments to demonstrate parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operator-spread.md
...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page references Azure CLI and Azure PowerShell together for running examples, but lists Azure PowerShell (a Windows-centric tool) before Azure CLI, which is cross-platform. The guidance for creating Bicep files only mentions Visual Studio Code, which is available on Linux but is often associated with Windows development. There are no explicit Linux shell or deployment examples, and no mention of Linux-native tools or workflows. No Linux-specific instructions or parity examples are provided.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is more platform-neutral.
- Explicitly mention that all examples can be run on Linux, macOS, and Windows, and provide a Linux shell (bash) example for deploying Bicep files.
- Include instructions or links for using Bicep with Linux-native editors (e.g., Vim, Emacs) or command-line workflows.
- Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for non-Windows users.
- Ensure that all tool references and workflows are presented in a platform-neutral order and language.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/parameter-files.md
...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing deployment examples and file path conventions primarily for Windows environments. Azure PowerShell is featured prominently, and all PowerShell examples use Windows-style paths (e.g., C:\MyTemplates\...). There are no Linux/macOS-specific examples, nor any mention of Bash, shell scripting, or Linux file paths. Visual Studio Code is referenced as the editor, but no cross-platform CLI or scripting guidance is provided for Linux users.
Recommendations
- Add Linux/macOS examples for Azure CLI and PowerShell, using POSIX-style file paths (e.g., /home/user/templates/storage.bicep).
- Include Bash or shell scripting examples alongside PowerShell, especially for deployment commands.
- Explicitly mention that Azure CLI and Bicep CLI are cross-platform, and provide installation and usage notes for Linux/macOS.
- Clarify that Visual Studio Code and Bicep extension are available on Linux/macOS, and provide relevant links.
- Where file paths are shown, provide both Windows and Linux/macOS variants, or use environment-agnostic placeholders.
- Add a note or section on deploying from Linux environments, including any differences or considerations.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/private-module-registry.md
...zure-resource-manager/bicep/private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. In command examples, Azure PowerShell (a Windows-centric tool) is consistently presented before Azure CLI, and PowerShell syntax is given equal or greater prominence than the cross-platform Azure CLI. There are no Bash or Linux shell examples, and the local cache path is described for Windows first, with Linux and Mac following. The documentation assumes use of Azure CLI or PowerShell for credentials, with no mention of Bash scripting or Linux-native workflows.
Recommendations
- Present Azure CLI examples before Azure PowerShell, as Azure CLI is cross-platform and more common for Linux users.
- Add Bash shell script examples where appropriate, especially for common tasks like publishing or restoring modules.
- When listing file paths, consider listing Linux or Mac paths first or presenting all platforms in parallel tables or lists.
- Explicitly mention that Azure CLI commands work on Linux, Mac, and Windows, and provide guidance for Linux-native workflows.
- Where possible, avoid Windows-centric terminology (e.g., %USERPROFILE%) without also providing the equivalent for Linux/Mac.
- Consider including a section or callout for Linux users, highlighting any differences or tips for using Bicep and Azure Container Registry on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md
...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. While it is focused on Visual Studio Code (which is cross-platform), it consistently presents Azure CLI and Azure PowerShell as the only deployment options, with PowerShell examples given equal prominence to CLI. There are no explicit Linux/macOS-specific instructions or terminal examples, and the workflow assumes familiarity with right-click context menus and UI patterns more common on Windows. The mention of Visual Studio (distinct from VS Code) also reinforces a Windows-centric perspective.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as using the integrated terminal in VS Code or relevant keyboard shortcuts.
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users, listing CLI examples before PowerShell.
- Include screenshots or callouts showing the process on Linux/macOS (e.g., using the terminal instead of right-click context menus).
- Avoid mentioning Visual Studio (the Windows-only IDE) in the main flow; if referenced, clearly distinguish it from VS Code and link only as an alternative.
- Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path syntax) where relevant.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-loops.md
...icles/azure-resource-manager/bicep/quickstart-loops.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently presents Windows-centric tools and workflows first or exclusively. Azure PowerShell is given equal prominence to Azure CLI, and Visual Studio Code is the only editor mentioned. There are no explicit Linux shell (bash) examples, and no mention of Linux-native editors or workflows. This may make Linux users feel like second-class citizens or require them to adapt Windows-oriented instructions.
Recommendations
- Present Azure CLI (which is cross-platform and often preferred on Linux/macOS) examples before PowerShell, or clarify that CLI is cross-platform while PowerShell is more common on Windows.
- Include bash/zsh shell variable syntax in CLI examples (e.g., export resourceGroupName=...) and clarify that CLI commands work on Linux/macOS terminals.
- Mention alternative editors such as Vim, Emacs, or JetBrains IDEs, or at least clarify that Visual Studio Code is available on Linux/macOS.
- Add a note or section on running Bicep deployments from Linux/macOS, including any prerequisites or differences.
- Where PowerShell is shown, explicitly state that it is primarily for Windows users, and link to Linux/macOS equivalents.
- Ensure that all instructions and scripts are tested and presented in a way that is friendly to Linux/macOS users, not just Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md
...urce-manager/bicep/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, and by referencing Windows tools and patterns (such as PowerShell and backslash line continuations) before or instead of Linux equivalents. There are no explicit Linux/macOS shell examples, and the CLI examples use Windows paths and conventions, which may not work on Linux/macOS systems.
Recommendations
- Provide both Windows and Linux/macOS file path examples (e.g., C:\templates\main.bicep and ~/templates/main.bicep) in all CLI and PowerShell commands.
- When showing Azure CLI examples, use POSIX-style paths and line continuations (forward slashes and \ or \ for Windows, / for Linux/macOS).
- Explicitly mention that the examples work on both Windows and Linux/macOS, and highlight any differences (such as variable assignment syntax in Bash vs PowerShell).
- Add tabs or callouts for Bash (Linux/macOS) shell usage where appropriate, especially for Azure CLI commands.
- Avoid using only Windows-specific tools or patterns (such as PowerShell) as the primary or first example; alternate or present Bash/Linux examples first in some sections.
- Clarify in notes or prerequisites that Visual Studio Code and the Bicep extension are cross-platform, and provide installation links for Linux/macOS if available.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md
...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is featured prominently throughout, including in prerequisites and code tabs. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example may signal a bias toward Windows users. Visual Studio Code is listed as the recommended editor, which is cross-platform, but there is no mention of Linux-specific shell environments or editors. The documentation does not provide explicit Linux shell examples (e.g., bash), nor does it mention Linux-specific installation steps or considerations. The ordering of examples sometimes places PowerShell before CLI, and PowerShell is referenced in the prerequisites before CLI.
Recommendations
- Add explicit bash/Linux shell examples where appropriate, especially for CLI commands.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any Linux-specific notes if needed (e.g., file path formats, environment setup).
- In the prerequisites, mention that Azure CLI and Visual Studio Code are cross-platform, and provide installation links for Linux and macOS as well as Windows.
- Consider providing examples using native Linux tools (e.g., nano, vim) for editing Bicep files, or at least mention their use.
- Ensure that CLI examples are presented first, as CLI is platform-neutral, and PowerShell is Windows-centric.
- Add a note that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
Azure Resource Manager
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally presents Azure CLI and Azure PowerShell as the primary command-line tools for interacting with Bicep and Azure resources. In several places, PowerShell is mentioned alongside or before CLI, and examples are always given for both, but there is no mention of Bash, Linux-specific shells, or Linux-native tools. The use of Visual Studio Code (cross-platform) is appropriate, but the command-line examples and tool recommendations are Windows-centric, with no explicit Linux or macOS guidance or examples. The documentation does not provide parity for Linux users in terms of shell commands, package management, or troubleshooting.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Provide Bash or shell examples where command-line usage is shown, especially for common tasks (e.g., using az in Bash).
- When referencing PowerShell, clarify that PowerShell Core is available on Linux and macOS, or provide Bash equivalents.
- Include Linux/macOS-specific troubleshooting tips or installation notes, such as using apt, yum, or Homebrew for installing tools.
- Ensure that any references to file paths, keyboard shortcuts, or context menus clarify platform differences (e.g., Ctrl vs Cmd, path separators).
- Add a section or callout for Linux/macOS users to ensure parity in setup and usage.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md
...ce-manager/bicep/quickstart-private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently provides examples using Azure CLI and Azure PowerShell, with no mention of native Linux shells (e.g., bash) or scripting environments. Visual Studio Code and Visual Studio are recommended as editors, with no mention of Linux-preferred alternatives. PowerShell examples are given equal prominence to Azure CLI, and Windows tools (Visual Studio, PowerShell) are referenced throughout, while Linux-specific workflows, editors, or shell commands are absent.
Recommendations
- Add explicit bash/zsh shell examples for all CLI commands, showing usage in a typical Linux environment (e.g., export environment variables, use $HOME paths).
- Mention and provide examples for using editors commonly preferred on Linux, such as Vim, Emacs, or alternatives to Visual Studio/Visual Studio Code.
- Clarify that Azure CLI is cross-platform and show command-line examples in a Linux terminal context (e.g., using single quotes, Linux-style paths).
- De-emphasize PowerShell as a primary tool by listing Azure CLI (which is cross-platform) first and PowerShell second, or in a separate section.
- Include a note or section on using the Bicep CLI directly from bash or other Linux shells, especially for users who do not use PowerShell.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, UI elements).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/resource-dependencies.md
.../azure-resource-manager/bicep/resource-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates bias towards Windows by exclusively mentioning Visual Studio Code—a tool most commonly associated with Windows—when discussing visualization of dependencies. No Linux-native editors or tools (such as Vim, Emacs, or command-line alternatives) are referenced. There are no examples or instructions for Linux users, nor is there mention of how to visualize dependencies outside of Visual Studio Code. The documentation implicitly assumes the reader is using Windows or Windows-centric tooling.
Recommendations
- Include instructions or references for visualizing Bicep dependencies using Linux-native editors or command-line tools.
- Mention cross-platform alternatives to Visual Studio Code, such as Vim, Emacs, or JetBrains IDEs, and clarify their support for Bicep visualization.
- Add a note about the availability of Visual Studio Code on Linux and macOS, or provide parity by listing equivalent steps for those platforms.
- Consider referencing CLI-based visualization tools (if available) for users who prefer terminal workflows, common on Linux.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-spec-convert.md
...re-resource-manager/templates/template-spec-convert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell-based automation for converting portal templates to template specs, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The only script provided is a PowerShell script, and there are no Linux/macOS-specific instructions or examples. This creates a bias toward Windows users and environments.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for Linux/macOS users.
- Explicitly state platform compatibility for the PowerShell script (e.g., if it works in PowerShell Core on Linux/macOS).
- Mention and link to cross-platform tools or scripts if available.
- Add a note or section for Linux/macOS users, clarifying how they can perform the migration (e.g., using Azure CLI, Cloud Shell, or PowerShell Core).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/template-specs.md
...rticles/azure-resource-manager/bicep/template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and in some cases provides PowerShell-only guidance (e.g., deploying with .bicepparam files is not supported in PowerShell). There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. The focus on PowerShell and lack of explicit Linux/Bash examples or notes may make the documentation less accessible for Linux users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) examples first to avoid Windows-first bias.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash/zsh shell command examples where relevant.
- Add notes or sections for Linux users, including any OS-specific considerations (e.g., file paths, environment variables, shell syntax).
- Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide equivalent Bash scripting examples.
- Review and update any statements or features that are PowerShell-only to clarify cross-platform support and provide alternatives if available.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/create-custom-provider.md
...rce-manager/custom-providers/create-custom-provider.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but the PowerShell sections rely on ARMClient, a tool that is Windows-centric and not natively available on Linux. There are no examples using common Linux-native tools (such as curl or httpie) for REST operations, and no mention of how to perform the PowerShell steps on Linux or via cross-platform alternatives. This creates a bias towards Windows users in the PowerShell sections and omits Linux-native workflows for REST calls.
Recommendations
- Add Linux-native examples for REST operations, such as using curl or httpie, especially in sections where ARMClient is recommended.
- Clarify whether ARMClient can be used on Linux (e.g., via .NET Core or Mono), or suggest cross-platform alternatives.
- In the PowerShell sections, note that PowerShell 7 is cross-platform and provide instructions for installing and using it on Linux and macOS.
- Consider including Bash script examples for key operations, or at least mention how the Azure CLI commands can be run on Linux/macOS.
- Wherever a Windows-specific tool is recommended, provide a Linux equivalent or explicitly state the limitations.
Azure Resource Manager
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, referencing Visual Studio Code (a cross-platform but Windows-associated editor) as the primary tool, and omitting explicit Linux/macOS shell examples for key steps. The portal-based instructions are platform-neutral, but command-line guidance is Windows-centric, and there are no Bash or Linux-specific notes or troubleshooting tips.
Recommendations
- Present Azure CLI (which is cross-platform) instructions before or alongside PowerShell, especially for build and deployment steps.
- Explicitly mention that Visual Studio Code is available on Linux and macOS, or suggest alternative editors (e.g., Vim, nano) for Linux users.
- Add Bash/Linux shell command examples for all steps where PowerShell is shown, and clarify any OS-specific differences.
- Include troubleshooting notes or links relevant to Linux/macOS users (e.g., file permissions, path conventions).
- Ensure that all prerequisite tools (Azure CLI, Bicep, editors) have installation instructions or links for Linux/macOS as well as Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md
...aged-applications/deploy-service-catalog-quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In most sections, Azure PowerShell (which is Windows-centric) is presented before Azure CLI (which is cross-platform and more common on Linux). Instructions for opening terminals default to PowerShell and Visual Studio Code, and PowerShell-specific syntax (such as the backtick for line continuation and escaping) is explained in detail, while Bash/Linux equivalents are covered later. There is a strong focus on PowerShell commands and patterns, and no mention of native Linux shells or editors (e.g., Bash, nano, vim) outside of the Azure CLI context. The documentation does not provide Linux-specific troubleshooting or environment notes, and the overall structure and examples are slightly more tailored to Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (Bash) first, as it is more cross-platform and widely used on Linux and macOS.
- Explicitly mention and provide examples for opening Bash terminals on Linux and macOS, not just in the context of Visual Studio Code or Git Bash.
- Include notes or tips for Linux users, such as common editors (nano, vim) or shell differences, especially when discussing environment setup.
- Balance the depth of explanation for PowerShell and Bash syntax (e.g., line continuation, escaping) to ensure Linux users receive equal guidance.
- Reference Linux-native tools or workflows where appropriate, and avoid assuming Visual Studio Code or PowerShell as the default environment.
- Consider adding a short section or callout for Linux/macOS users, highlighting any platform-specific considerations or troubleshooting steps.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/managed-applications/publish-bicep-definition.md
...nager/managed-applications/publish-bicep-definition.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and terminology are presented before Azure CLI/Bash equivalents throughout the page, and PowerShell-specific features (such as splatting) are explained in detail. Instructions for opening terminals reference PowerShell and Visual Studio Code, which are more commonly used on Windows. There is little explicit mention of Linux environments, and no Linux-specific tooling or patterns (such as native shell scripting, package managers, or alternative editors) are discussed.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples so that neither is always presented first; consider leading with Azure CLI/Bash in some sections.
- Add explicit instructions for Linux users, such as using native terminals (e.g., GNOME Terminal, Konsole) and referencing common Linux shell environments.
- Include notes on installing required tools (Azure CLI, Bicep, VS Code) on Linux distributions, with links to Linux-specific installation guides.
- Mention alternative editors (e.g., Vim, nano) for users who may not use Visual Studio Code.
- Avoid PowerShell-specific terminology (like 'splatting') without providing equivalent Bash/Linux shell explanations.
- Clarify that all CLI commands are cross-platform and provide troubleshooting tips for Linux-specific issues (e.g., file permissions, case sensitivity).