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 1-25 of 492 flagged pages
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and Visual Studio, with all instructions and screenshots based on the Windows version of Visual Studio. Deployment steps rely exclusively on PowerShell scripts (AzureRM and Az modules), with no mention of Linux/macOS alternatives or cross-platform tooling. There are no examples or guidance for performing these tasks on Linux or macOS, nor is there any reference to CLI, VS Code, or other cross-platform approaches.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as using VS Code with Azure extensions, or Azure CLI/ARM templates.
  • Provide cross-platform deployment examples using Azure CLI or Bicep, not just PowerShell.
  • Explicitly mention platform requirements and alternatives for non-Windows users.
  • Include screenshots or steps for VS Code or other IDEs that run on Linux/macOS.
  • Clarify whether the PowerShell scripts can be run in PowerShell Core on Linux/macOS, and provide troubleshooting steps if not.
GitHub Create Pull Request
Azure Resource Manager Use template deployment scripts | Microsoft Docs ...nager/templates/template-tutorial-deployment-script.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of PowerShell for deployment scripts, detailed PowerShell-specific instructions and escape character notes, and a lack of Bash or Linux shell script examples for the core deployment script. While Azure CLI is mentioned for some steps, the main deployment script resource only supports PowerShell, and all script content and troubleshooting guidance is PowerShell-centric. Linux/macOS users are left without equivalent examples or guidance for authoring or debugging deployment scripts in their native environments.
Recommendations
  • Add equivalent Bash (Azure CLI) deployment script examples and templates where possible.
  • Clearly state platform limitations (e.g., if only PowerShell is supported for deployment scripts) and provide workarounds or alternatives for Linux/macOS users.
  • Include troubleshooting steps and file locations for Bash/CLI scripts, not just PowerShell.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • If PowerShell is required, provide guidance for installing and using PowerShell Core on Linux/macOS.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows. All examples, scripts, and template resources focus exclusively on deploying and configuring a Windows VM using PowerShell and Windows-specific tools (e.g., Install-WindowsFeature, powershell.exe). There are no Linux VM examples, nor any mention of Linux equivalents such as Bash scripts or Linux extensions. The tutorial title and steps do not clarify that it is Windows-only, and Linux users are left without guidance for completing similar tasks.
Recommendations
  • Add parallel examples for deploying and configuring Linux VMs, including use of Custom Script Extension with Bash scripts.
  • Include links to Linux VM extension documentation and quickstart templates (e.g., 'Deploy a simple Linux VM').
  • Show both PowerShell and Bash script examples for password generation, script execution, and resource cleanup.
  • Clarify in the introduction that the tutorial focuses on Windows, and provide a link or section for Linux users.
  • Demonstrate how to install a web server (e.g., Apache or Nginx) on Linux VMs using ARM templates and extensions.
GitHub Create Pull Request
Azure Resource Manager Enable debug logging ...source-manager/troubleshooting/enable-debug-logging.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias by exclusively using Azure PowerShell for enabling debug logging, which is not available via Azure CLI (the cross-platform tool). All setup and enabling instructions rely on PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There are no Linux/macOS-specific instructions or alternatives for enabling debug logging, and no mention of Bash or shell scripting. While Azure CLI is referenced for retrieving and deleting logs, it cannot be used to enable debug logging, creating a significant gap for non-Windows users.
Recommendations
  • Provide parity for enabling debug logging via Azure CLI, or document a workaround for Linux/macOS users.
  • If PowerShell is required, clarify how to use Azure PowerShell on Linux/macOS (e.g., via PowerShell Core), including installation and usage instructions.
  • Add explicit notes or examples for Linux/macOS users, including any platform-specific caveats.
  • Consider advocating for CLI feature parity in Azure tooling if not currently possible.
GitHub Create Pull Request
Azure Resource Manager Create & deploy Visual Studio resource group projects ...r/templates/create-visual-studio-deployment-project.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows users, specifically those using Visual Studio and PowerShell. All examples and instructions assume the use of Visual Studio (a Windows-only IDE) and PowerShell scripts for deployment, with no mention of Linux/macOS alternatives or cross-platform tools. There are no CLI or VS Code instructions, and no Linux/macOS-specific guidance is provided.
Recommendations
  • Add instructions for deploying Azure Resource Manager templates using cross-platform tools such as Azure CLI or VS Code.
  • Provide Linux/macOS equivalents for project creation, template editing, and deployment steps.
  • Include examples using Bash or Azure CLI for deployment, not just PowerShell.
  • Mention and link to cross-platform alternatives for Visual Studio, such as VS Code with Azure extensions.
  • Clearly state platform requirements and offer guidance for non-Windows users at the start of the article.
GitHub Create Pull Request
Azure Resource Manager Use Azure Key Vault in templates ...e-manager/templates/template-tutorial-use-key-vault.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell environments. All code examples for resource creation, deployment, and cleanup use Azure PowerShell cmdlets, with no Azure CLI or Bash equivalents provided. The tutorial centers on deploying a Windows VM, and the validation step requires connecting via RDP, a Windows-specific protocol. Linux alternatives (such as deploying a Linux VM, using SSH, or using Azure CLI commands) are not mentioned or demonstrated.
Recommendations
  • Provide Azure CLI (az) and Bash script equivalents for all PowerShell examples, especially for key vault creation, secret retrieval, template deployment, and resource cleanup.
  • Include a parallel example for deploying a Linux VM, with instructions for connecting via SSH instead of RDP.
  • Explicitly mention and demonstrate how to use Cloud Shell in Bash mode, not just PowerShell.
  • Reference Linux password requirements and link to relevant documentation, not just Windows VM password requirements.
  • Reorder examples or provide both Windows and Linux options side-by-side to avoid Windows-first presentation.
GitHub Create Pull Request
Azure Resource Manager Deploy VM extensions with template ...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on deploying VM extensions to Windows VMs using PowerShell scripts and Windows-specific tooling (e.g., Install-WindowsFeature, powershell.exe). All examples, templates, and walkthroughs are for Windows VMs, with no mention of Linux VMs, Bash scripts, or Linux equivalents of the demonstrated tasks. This creates friction for Linux users and does not provide guidance for deploying extensions to Linux VMs.
Recommendations
  • Add parallel examples and walkthroughs for deploying extensions to Linux VMs, including Bash script usage.
  • Include ARM template snippets for Linux VM extensions (e.g., using CustomScriptExtension with Bash).
  • Show how to install a web server (e.g., Apache or Nginx) on a Linux VM via extension.
  • Provide deployment and verification steps for Linux VMs (e.g., retrieving public IP, checking Apache/Nginx welcome page).
  • Ensure that both Windows and Linux scenarios are covered equally, or clarify the scope if the tutorial is intentionally Windows-only.
GitHub Create Pull Request
Azure Resource Manager Quickstart: Create Bicep files with Visual Studio Code ...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Bicep extension, Azure PowerShell) are mentioned prominently, and PowerShell examples are provided alongside Azure CLI. The deployment workflow is described primarily through Visual Studio Code's GUI, which is most commonly used on Windows. There are no Linux-specific instructions, nor are Linux terminal patterns (e.g., Bash, shell scripting) referenced. The order of examples and tool mentions generally favors Windows-first patterns.
Recommendations
  • Explicitly mention Linux and macOS compatibility for Visual Studio Code and the Bicep extension.
  • Provide Linux-specific instructions for installing prerequisites (e.g., using apt, yum, or Homebrew for Bicep and Azure CLI).
  • Include Bash or shell script examples for deployment and cleanup, especially for users who prefer terminal workflows.
  • Clarify that Azure CLI commands work cross-platform and highlight any differences in usage between Windows and Linux/macOS.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, path configuration).
  • Consider adding screenshots from Linux/macOS environments to balance the visual representation.
GitHub Create Pull Request
Azure Resource Manager Create and deploy a template spec with Bicep ...urce-manager/bicep/quickstart-create-template-specs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, without providing Linux/macOS equivalents. All command examples assume a Windows environment, and there is no mention of Linux-specific patterns, such as using forward slashes in file paths or handling environment variables in Bash. The documentation also references Windows tools (PowerShell) and links to PowerShell-based tutorials for access control, without offering Bash or Linux alternatives.
Recommendations
  • Provide Linux/macOS file path examples (e.g., ~/templates/main.bicep or /home/user/templates/main.bicep) alongside Windows paths in all CLI and PowerShell command samples.
  • Explicitly mention cross-platform compatibility of Azure CLI and PowerShell, and note any platform-specific caveats.
  • Where PowerShell is referenced for role assignments or other tasks, include equivalent Bash/Azure CLI instructions.
  • Add notes or tabs for Linux/macOS users, especially for steps involving file paths, environment variables, or shell scripting.
  • Ensure all command snippets and explanations are clear about platform differences, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager resource group and resource deletion ...e-resource-manager/management/delete-resource-group.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by consistently presenting PowerShell examples first, referencing PowerShell-specific commands, and using terminology and tooling (PowerShell) that is native to Windows. While Azure CLI and Python examples are included, the ordering and prominence of PowerShell, as well as the lack of explicit Linux shell examples (e.g., Bash), reinforce a Windows-centric approach. There are no direct Linux shell or scripting examples, and no mention of Linux-specific considerations or tools.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) or Bash examples appear before PowerShell.
  • Include explicit Bash shell examples for resource deletion, demonstrating usage in a Linux environment.
  • Clarify that Azure CLI works on both Windows and Linux, and provide installation/usage notes for Linux users.
  • Add notes or sections highlighting Linux-specific considerations, such as differences in authentication or environment setup.
  • Reduce reliance on PowerShell-specific syntax and terminology, or provide equivalent Linux-native commands where appropriate.
GitHub Create Pull Request
Azure Resource Manager Move guidance for classic deployment model resources ...ent/move-limitations/classic-model-move-limitations.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation refers to Azure PowerShell before Azure CLI when listing move operations, and does not provide any explicit Linux-specific examples or guidance. The mention of PowerShell (a Windows-centric tool) before CLI may suggest a Windows-first bias. There are no examples of using Linux-native tools or shell environments, nor is there parity in showing how to perform these operations on Linux systems.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning cross-platform tools, or mention them together to avoid implying preference.
  • Provide explicit examples of move operations using Azure CLI in Bash or other Linux shells.
  • Clarify that all operations can be performed equally on Linux, macOS, and Windows, and link to platform-specific instructions if available.
  • Avoid referencing PowerShell exclusively; ensure that CLI commands are shown alongside or before PowerShell commands.
  • Add a section or note on how Linux users can perform these operations, including installation and usage of Azure CLI.
GitHub Create Pull Request
Azure Resource Manager 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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Bicep files at the subscription scope. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are no explicit Bash or Linux shell examples. The CLI example is platform-neutral, but the PowerShell section may signal a Windows bias, especially as there is no mention of Linux-specific tools or workflows. There are also no explicit instructions or notes for Linux/macOS users, and the 'Cloud Shell' reference is only in the links, not in the main example flow.
Recommendations
  • Add explicit Bash/Linux shell examples where appropriate, or clarify that Azure CLI commands work cross-platform.
  • Consider mentioning that Azure CLI is available on all major platforms and is recommended for Linux/macOS users.
  • If PowerShell is included, clarify that PowerShell Core is cross-platform, or provide Bash equivalents.
  • Add a short section or note for Linux/macOS users to ensure parity and inclusivity.
  • Consider reordering to present Azure CLI (platform-neutral) before PowerShell, or clarify that both are supported equally.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md ...e-resource-manager/bicep/bicep-kubernetes-extension.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Visual Studio Code (a tool often associated with Windows) as the primary editor for importing Kubernetes manifests, and by mentioning the 'Import Kubernetes manifest' command in Visual Studio Code without providing equivalent instructions for Linux-native editors or command-line alternatives. There are no examples or guidance for using Linux tools or workflows, and no mention of Linux-specific considerations.
Recommendations
  • Provide examples or instructions for importing Kubernetes manifests using popular Linux editors (e.g., Vim, Emacs) or command-line tools.
  • Mention and link to cross-platform alternatives for Visual Studio Code, or clarify that VS Code is available on Linux and macOS.
  • Add explicit Linux command-line examples for managing kubeconfig files, such as using kubectl or base64 utilities.
  • Ensure that any tooling or workflow described is either cross-platform or that Linux/macOS alternatives are documented alongside Windows/VS Code instructions.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-config.md .../articles/azure-resource-manager/bicep/bicep-config.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Visual Studio Code (a cross-platform editor but with a Windows-centric workflow) and referencing Azure PowerShell and AzureCLI in credential precedence, with PowerShell listed before CLI in examples. There are no explicit Linux or macOS-specific instructions, nor are there examples using Linux-native editors or shell commands for creating or managing the configuration file.
Recommendations
  • Add explicit examples for creating and editing the bicepconfig.json file using Linux-native tools (e.g., nano, vim, or command-line touch/cat).
  • When discussing credential precedence, clarify the cross-platform availability of AzureCLI and Azure PowerShell, and consider listing AzureCLI first as it is more commonly used on Linux.
  • Include screenshots or instructions for creating the configuration file in editors popular on Linux/macOS (e.g., VS Code on Linux, Vim, or even gedit).
  • Mention that all instructions apply equally to Linux/macOS unless otherwise noted, and provide any OS-specific caveats if they exist.
  • Ensure that references to tools or commands (such as Visual Studio Code or PowerShell) are balanced with Linux/macOS equivalents or alternatives.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-files.md .../azure-resource-manager/bicep/bicep-functions-files.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples that are heavily oriented toward PowerShell scripts (e.g., .ps1 files, AzurePowerShell deployment scripts) and does not include equivalent examples for Linux shell scripts (e.g., .sh files, Bash). There are no references to Linux tools or patterns, and all script-related examples assume a Windows/PowerShell context. No Linux or cross-platform examples are provided.
Recommendations
  • Add examples that use Bash or shell scripts (e.g., .sh files) alongside PowerShell examples, especially in sections demonstrating script loading.
  • When referencing deployment scripts, include both 'AzurePowerShell' and 'AzureCLI' (with Bash) resource kinds to show parity.
  • Explicitly mention that file paths and encodings are cross-platform, and provide notes or examples for Linux/macOS users.
  • Where possible, alternate the order of examples or provide parallel examples for both Windows and Linux environments.
  • Clarify that Bicep functions work with files created or edited on any OS, and note any OS-specific considerations (such as line endings or file permissions).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-cli.md ...ain/articles/azure-resource-manager/bicep/bicep-cli.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style paths (e.g., c:\jsontemplates) in all file path examples, mentioning Windows paths before Linux equivalents, and referencing Windows tools (Azure PowerShell, Visual Studio Code) before or instead of Linux alternatives. There are no explicit Linux shell examples (e.g., bash), and Linux-style paths are only mentioned in a few places, often after the Windows version. Installation and usage guidance references Windows-centric tools and patterns, and Linux users may find it less approachable.
Recommendations
  • Provide Linux/macOS path examples (e.g., /home/user/jsontemplates) alongside or before Windows paths in all relevant code blocks.
  • Include bash/zsh shell command examples where appropriate, not just Azure CLI and PowerShell.
  • When referencing installation instructions, ensure parity between Windows and Linux, and link to both Azure CLI and native package manager (apt, yum, brew) installation guides.
  • When describing file system locations (e.g., cache paths), list Linux/macOS paths before or alongside Windows paths, not after.
  • Avoid using only Windows-specific shortcuts (e.g., SHIFT+ALT+F in VS Code) and mention the Linux/macOS equivalents.
  • Add explicit notes or tabs for Linux/macOS users where behavior or commands differ.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/bicep-functions-parameters-file.md ...ource-manager/bicep/bicep-functions-parameters-file.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias, especially in the 'readEnvironmentVariable' section. All examples for setting environment variables use PowerShell syntax and reference .NET/Windows APIs. There are no examples for Linux or macOS shells (e.g., Bash), and Windows methods are mentioned exclusively and first. This may confuse or exclude users working on non-Windows platforms.
Recommendations
  • Add equivalent examples for setting environment variables in Bash (Linux/macOS), e.g., export testEnvironmentVariable="Hello World!".
  • Mention both Windows (PowerShell/CMD) and Linux/macOS (Bash/Zsh) methods for setting environment variables, and present them together or in parallel sections.
  • Reference cross-platform documentation for environment variables, not just Windows/.NET APIs.
  • Clarify that Bicep and its parameter files are cross-platform and that environment variable handling depends on the user's OS/shell.
  • Where possible, avoid assuming PowerShell as the default shell; provide parity for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/create-resource-group.md .../azure-resource-manager/bicep/create-resource-group.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment commands. However, PowerShell (a Windows-centric tool) is always presented after the Azure CLI, and there is no mention of Bash, Linux shell scripting, or cross-platform command-line environments. The PowerShell examples use the Az module, which is primarily used on Windows, and there are no explicit Linux-specific instructions or troubleshooting notes. The documentation assumes parity between Azure CLI and PowerShell but does not address Linux users directly or provide guidance for common Linux workflows.
Recommendations
  • Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
  • Add Bash shell scripting examples or usage notes for Linux users, especially for multi-line commands.
  • Include troubleshooting notes or prerequisites for running Azure CLI on Linux (e.g., installation links, authentication differences).
  • Mention that PowerShell Core is available cross-platform, but clarify that the Az module examples are most familiar to Windows users.
  • Consider providing a Linux-first example in at least one section to balance the order of presentation.
  • Add a short section or note about using Bicep and deployment commands in WSL (Windows Subsystem for Linux) for users on Windows who prefer a Linux environment.
GitHub Create Pull Request
Azure Resource Manager 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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment command examples for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux-specific usage or shell environments (e.g., Bash). The CLI example is cross-platform, but the PowerShell example is Windows-centric. There are no Linux shell-specific instructions, nor is there guidance for using Bicep with Bash or other Linux tools. References to Cloud Shell are present but not elaborated upon, and the documentation does not clarify that Azure CLI works natively on Linux and macOS.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI commands, clarifying cross-platform compatibility.
  • Note that Azure CLI is available on Windows, Linux, and macOS, and provide installation or usage links for Linux users.
  • Include a section or note on using Bicep with Linux-native tools and environments.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users (e.g., Azure CLI).
  • Expand the Cloud Shell section to explain its cross-platform nature and how both CLI and PowerShell can be accessed from any OS.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/data-types.md ...in/articles/azure-resource-manager/bicep/data-types.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is generally cross-platform, but it contains a notable Windows bias in the 'Integers' section, where only PowerShell is mentioned as an example of a deployment tool with integer range limitations. No mention is made of Linux or cross-platform equivalents (such as Azure CLI or Bash), and no Linux-specific examples or caveats are provided. This may lead Linux users to believe the limitation is exclusive to PowerShell or Windows environments.
Recommendations
  • When referencing deployment tools (such as in the integer range limitation), mention both Windows (PowerShell) and Linux/cross-platform tools (such as Azure CLI, Bash, or Cloud Shell).
  • If a limitation is specific to PowerShell, clarify that and provide information about behavior on Linux tools (e.g., Azure CLI).
  • Wherever possible, provide examples or notes relevant to both Windows and Linux users, or explicitly state when behavior is platform-agnostic.
  • Consider adding a table or section comparing behaviors across common deployment environments (PowerShell, Azure CLI, Bash) for clarity.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/decompile.md ...ain/articles/azure-resource-manager/bicep/decompile.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Azure CLI and Azure PowerShell examples, with PowerShell (a Windows-centric tool) given its own section. There are no explicit Linux/macOS shell examples (e.g., Bash), and the use of Visual Studio Code (a cross-platform tool but often associated with Windows) is emphasized. The documentation does not mention or show Linux-specific shell commands or workflows, nor does it address platform-specific differences or considerations. The ordering of examples (CLI, then PowerShell, then Portal) also puts Windows tools before Linux-native equivalents.
Recommendations
  • Add explicit Bash/Linux shell examples for exporting and decompiling templates, e.g., using Bash redirection and file paths.
  • Clarify that Azure CLI commands work on all platforms and provide sample commands using Bash syntax (e.g., with single quotes, Linux file paths).
  • Mention and show how to use the Bicep CLI directly in Linux/macOS terminal environments.
  • Balance the order of examples so that Linux/Bash and Windows/PowerShell are presented equally or alternate their order.
  • Explicitly state cross-platform compatibility and call out any platform-specific differences or requirements.
  • Consider adding a table or section summarizing commands for Windows (PowerShell), Linux (Bash), and macOS.
GitHub Create Pull Request
Azure Resource Manager 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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples and commands before or alongside Azure CLI, referencing Windows-centric tools (PowerShell), and using PowerShell syntax in permission assignment steps. There is no explicit mention of Linux environments, nor are Linux-specific instructions or examples provided. The use of Azure CLI does help with cross-platform parity, but the prominence and order of PowerShell examples and references to Windows tools suggest a Windows-first approach.
Recommendations
  • Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links or instructions for those platforms.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available on Linux/macOS, or provide Bash script equivalents where possible.
  • Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or differences.
  • Review all command-line examples to ensure they are not Windows-centric (e.g., avoid using backticks for line continuation in PowerShell, which is not standard in Bash).
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deploy-what-if.md ...rticles/azure-resource-manager/bicep/deploy-what-if.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples alongside Azure CLI, often listing PowerShell before CLI or with equal prominence. All command-line examples are either Azure CLI or PowerShell, with no mention of Bash, Linux shell scripting, or native Linux tools. Installation and usage instructions focus on PowerShell and Azure CLI, which, while cross-platform, are more familiar to Windows users. There is no explicit Linux shell (bash/zsh) or macOS-specific guidance, and PowerShell is treated as a first-class citizen, reinforcing a Windows-centric workflow.
Recommendations
  • Add explicit Bash/Linux shell examples for all command-line operations, especially for scripting and programmatic evaluation.
  • Clarify that Azure CLI is cross-platform and provide Linux/macOS installation instructions or links.
  • When listing tools or examples, lead with Azure CLI (as it is more common on Linux/macOS) before PowerShell.
  • Include notes or sections for using these commands in native Linux/macOS environments, addressing any differences (e.g., file paths, environment variables).
  • Mention and link to relevant Linux-native editors (e.g., Vim, nano) or scripting approaches where appropriate.
  • Review and adjust language to avoid implying PowerShell is the default or preferred shell, especially in cross-platform contexts.
GitHub Create Pull Request
Azure Resource Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md ...manager/bicep/deployment-script-bicep-configure-dev.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and PowerShell by providing all deployment and upload examples using Azure PowerShell scripts, referencing Windows-style file paths, and omitting equivalent Bash or Azure CLI examples for common tasks such as uploading files. The Docker section also uses Windows drive letters and folder mapping syntax, with no explicit Linux or macOS instructions. While Azure CLI and Bash are mentioned for container images and script content, the operational instructions and tooling focus primarily on PowerShell and Windows-centric workflows.
Recommendations
  • Provide Bash/Azure CLI equivalents for all PowerShell deployment and upload scripts, especially for tasks like deploying Bicep files and uploading scripts to Azure Storage.
  • Include Linux/macOS-specific Docker volume mount examples (e.g., using /home/user/docker:/data) alongside Windows examples.
  • When referencing file paths or drive letters, clarify platform differences and provide cross-platform examples.
  • Balance the order of presentation so that Azure CLI/Bash and PowerShell/Windows instructions are given equal prominence, or group them clearly by platform.
  • Explicitly mention platform compatibility and any differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Azure Resource Manager 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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and Azure CLI as alternatives to the Azure portal for exporting ARM templates, but does not provide explicit Linux-specific examples or mention Bash/shell usage. Azure PowerShell is mentioned alongside Azure CLI, but there is no parity in showing Linux command-line workflows or emphasizing cross-platform tools. The absence of Linux-specific instructions or screenshots, and the order of mentioning PowerShell (a Windows-centric tool) before CLI or REST API, suggests a mild Windows bias.
Recommendations
  • Add explicit examples using Azure CLI in Bash or shell environments to demonstrate Linux parity.
  • When listing alternatives, mention Azure CLI and REST API before Azure PowerShell to avoid Windows-first ordering.
  • Include screenshots or instructions that show the process on Linux systems, if applicable.
  • Clarify that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • Where PowerShell is referenced, note that PowerShell Core is also available cross-platform, or provide equivalent Bash commands.
GitHub Create Pull Request
← Previous Page 1 of 20 Next →