Azure Resource Manager

504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1281 issues found
Showing 226-250 of 1281 flagged pages
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 00:00
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 Windows bias. All code examples for creating and deploying resources use Azure PowerShell, with no equivalent Azure CLI or Bash examples provided. The tutorial centers on deploying a Windows VM, referencing Windows-specific password requirements and using RDP for validation. Linux VM scenarios, tools, and deployment patterns are absent, and the use of PowerShell is prioritized throughout, even when Cloud Shell supports Bash/CLI. Windows tools and workflows are mentioned exclusively or before any Linux alternatives.
Recommendations
  • Provide Azure CLI (az) and Bash examples alongside PowerShell scripts for all resource creation and deployment steps.
  • Include a parallel tutorial or examples for deploying a Linux VM, referencing Linux-specific password/SSH requirements.
  • Mention and demonstrate Linux connection methods (e.g., SSH) in the validation section, not just RDP.
  • Reference Linux documentation and password requirements where appropriate.
  • Ensure that instructions for Cloud Shell do not default to PowerShell, but present Bash/CLI as an equal option.
  • Balance the use of Windows and Linux terminology, tools, and workflows throughout the tutorial.
GitHub Create Pull Request
Azure Resource Manager Use template reference .../templates/template-tutorial-use-template-reference.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias: Visual Studio Code is required as the editor, which is cross-platform but often associated with Windows workflows. The instructions for opening and saving files use GUI steps typical of Windows environments. In deployment, both PowerShell and Azure CLI examples are provided, but PowerShell is presented first, and the CLI example is labeled as 'Bash (for CLI)', which may imply secondary importance. There are no explicit Linux-specific editor or workflow recommendations, and the file upload instructions reference GUI actions that may not be typical for Linux users.
Recommendations
  • Explicitly mention that Visual Studio Code is available on Linux and macOS, and suggest alternative editors (e.g., Vim, nano) for Linux users.
  • Provide command-line instructions for downloading the template file (e.g., using curl or wget) in addition to GUI steps.
  • Present Azure CLI (Bash) examples before or alongside PowerShell examples to avoid Windows-first impression.
  • Include Linux-specific instructions for uploading files to Azure Cloud Shell (e.g., using azcopy or scp).
  • Clarify that all steps can be performed on Linux, macOS, or Windows, and highlight any platform-specific differences.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot common Azure deployment errors ...ce-manager/troubleshooting/common-deployment-errors.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates some Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell (a Windows-centric tool) is referenced directly alongside CLI, without explicit parity for Linux shell usage. In the 'SubnetsNotInSameVnet' error, the Windows VM multiple NICs documentation is listed before the Linux equivalent, suggesting a Windows-first approach. There are also several references to PowerShell modules and commands, which are primarily used on Windows, with no mention of Bash or Linux-specific alternatives. No explicit Linux shell commands or troubleshooting patterns are provided.
Recommendations
  • Ensure that examples and tool references include both Windows (PowerShell) and Linux (Bash/CLI) usage, with equal prominence.
  • When linking to platform-specific documentation (e.g., multiple NICs), alternate the order or provide a neutral grouping to avoid Windows-first presentation.
  • Where PowerShell is referenced, also provide equivalent Bash or Azure CLI commands for Linux users.
  • Audit linked troubleshooting guides to ensure Linux scenarios are covered as thoroughly as Windows ones.
  • Explicitly mention cross-platform compatibility for tools and commands where applicable.
GitHub Create Pull Request
Azure Resource Manager Deployment quota exceeded ...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (with Bash scripting) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, and there is no explicit mention that PowerShell commands are Windows-centric or that Bash examples are Linux/macOS-centric. The Bash scripting in the Azure CLI section assumes a Unix-like environment but does not clarify this, nor does it provide Windows Command Prompt equivalents. There is a slight Windows bias in that PowerShell is presented as the alternative to Azure CLI, which is more cross-platform, and there is no mention of using CLI in Windows Command Prompt or PowerShell Core on Linux/macOS.
Recommendations
  • Explicitly state which environments (Windows, Linux, macOS) each example is intended for.
  • Provide Windows Command Prompt batch script equivalents for the Azure CLI examples, or clarify that Bash is required for those scripts.
  • Clarify that PowerShell examples are for Windows PowerShell, and mention PowerShell Core compatibility on Linux/macOS if applicable.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell to reduce implicit Windows-first bias.
  • Add notes or links for users on Linux/macOS who may want to use PowerShell Core, or provide guidance for adapting the scripts.
GitHub Create Pull Request
Azure Resource Manager SKU not available errors ...rce-manager/troubleshooting/error-sku-not-available.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by consistently presenting PowerShell examples and references before Linux-friendly alternatives, such as Azure CLI. PowerShell and Windows-centric tools (e.g., New-AzVM, Get-AzComputeResourceSku) are featured prominently, with more detailed scripting examples provided for PowerShell than for CLI. The REST example uses a Windows-style path ('.\sku-list.json') for output, and there is no mention of Linux-specific shell usage or file paths. No Bash or Linux shell scripting examples are provided, and the documentation does not address Linux-specific usage patterns or troubleshooting steps.
Recommendations
  • Alternate the order of examples so that Azure CLI (cross-platform) is presented before PowerShell.
  • Provide equivalent Bash shell scripting examples for filtering and processing output, especially for complex queries currently shown only in PowerShell.
  • Use platform-neutral file paths in examples (e.g., './sku-list.json' instead of '.\sku-list.json').
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide troubleshooting notes for Linux users if relevant.
  • Where PowerShell scripts are shown, offer a comparable Bash or shell script for Linux users.
  • Reference Linux tools (e.g., jq for JSON parsing) alongside PowerShell tools (e.g., Where-Object) when discussing output filtering.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot ARM template JSON deployments ...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by consistently presenting PowerShell examples alongside Azure CLI, referencing PowerShell as a primary tool, and mentioning Windows-centric tools like Visual Studio Code before alternatives. There is no explicit Linux example (e.g., bash scripting), and PowerShell is given equal prominence to Azure CLI, which is cross-platform but often associated with Linux workflows. The prerequisites and instructions do not mention Linux-specific editors or shell environments.
Recommendations
  • Add explicit Linux shell (bash) examples for ARM template deployment commands, especially for Azure CLI usage.
  • Mention Linux-native editors (e.g., Vim, nano, gedit) as alternatives to Visual Studio Code in the prerequisites.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Consider including screenshots or instructions from a Linux desktop environment (e.g., Ubuntu) to balance the visual representation.
  • If PowerShell is mentioned, note that it is available cross-platform, and provide guidance for installing and using it on Linux.
  • Avoid listing PowerShell before Azure CLI, or alternate the order to avoid implicit prioritization.
GitHub Create Pull Request
Azure Resource Manager Resource not found errors ...re-resource-manager/troubleshooting/error-not-found.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Azure CLI together, but listing PowerShell first and providing a direct link to the PowerShell cmdlet before the Azure CLI equivalent. There are no examples or instructions for Linux-specific tools, shells, or workflows. The guidance assumes use of the Azure portal (web-based, cross-platform) but omits any mention of Linux shell usage or alternative Linux-native tools. No bash, zsh, or Linux command-line examples are provided, and troubleshooting steps do not address Linux-specific scenarios.
Recommendations
  • Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first to avoid Windows-first perception.
  • Provide explicit bash/zsh/Linux shell examples for relevant commands, especially for subscription/context switching and resource management.
  • Mention Linux-native tools (e.g., az CLI in bash, scripting with jq, etc.) where appropriate.
  • Clarify that Azure CLI is cross-platform and provide instructions for both Windows and Linux environments.
  • Add troubleshooting steps or notes relevant to Linux users, such as environment variables, shell differences, or file system considerations.
GitHub Create Pull Request
Azure Resource Manager Troubleshoot Bicep file deployments ...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
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 deployment and cleanup tasks. However, PowerShell is a Windows-centric tool, and its examples are given equal prominence to Azure CLI, which is cross-platform. There is no mention of Linux-specific shell environments (e.g., Bash), nor are there examples tailored for Linux users (such as using Bash scripts or Linux file paths). The prerequisites mention Visual Studio Code, which is cross-platform, but do not discuss alternative editors or shell environments commonly used on Linux. The documentation does not address platform-specific nuances, such as line continuation differences or file system paths, which may affect Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and clarify that PowerShell is primarily for Windows (though available on Linux, it's less common).
  • Add Bash-specific examples or notes for Linux users, especially for multi-line commands (e.g., using \ for line continuation in Bash).
  • Include Linux-specific troubleshooting tips, such as checking file permissions or using common Linux editors (e.g., Vim, Nano) in addition to Visual Studio Code.
  • Clarify any platform-specific differences in command syntax, output, or error handling.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric), or provide tabs labeled by OS (Windows, Linux, macOS) for greater clarity.
GitHub Create Pull Request
Azure Resource Manager Templates overview .../articles/azure-resource-manager/templates/overview.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 Tools Windows First
Summary
The documentation page demonstrates mild Windows bias. PowerShell is mentioned as a primary scripting option for deployment scripts and for the ARM template toolkit (arm-ttk), which is only available as a PowerShell script. Authoring tools listed are Visual Studio Code and Visual Studio, both Windows-centric (though VS Code is cross-platform). There is a tendency to mention PowerShell before Bash, and Windows tools (Visual Studio) are referenced without Linux alternatives. No explicit Linux-only tools or workflows are highlighted.
Recommendations
  • Provide equal emphasis on Bash scripting alongside PowerShell for deployment scripts, including example usage.
  • Mention and link to cross-platform or Linux-native template authoring tools (such as Vim, Emacs, or JetBrains IDEs) if applicable.
  • Highlight ARM template toolkit alternatives or wrappers for Linux users, or clarify how to run arm-ttk on Linux (e.g., via PowerShell Core).
  • Include explicit Linux CLI examples and workflows, especially for template deployment and validation.
  • When listing deployment options, alternate the order or group CLI and Bash before PowerShell to avoid 'windows_first' impression.
GitHub Create Pull Request
Azure Resource Manager Create parameter file ...es/azure-resource-manager/templates/parameter-files.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 provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool (despite cross-platform support, it's still most commonly associated with Windows). The PowerShell example is given after the CLI example, which is cross-platform, but references to Visual Studio (Windows-only) and PowerShell parameter name conflicts further reinforce a Windows bias. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific patterns or tools.
Recommendations
  • Include Linux/Bash shell examples for deploying templates, such as using az CLI from Bash with Linux-style file paths (e.g., /home/user/storage.parameters.json).
  • Clarify that PowerShell is available cross-platform, and provide examples with Linux/Mac file paths.
  • Add notes or examples for using VS Code (cross-platform) instead of Visual Studio for ARM template projects.
  • Ensure that references to file paths use both Windows and Linux/Mac conventions.
  • Mention that Azure CLI is fully supported on Linux and Mac, and highlight any differences in usage if relevant.
GitHub Create Pull Request
Azure Resource Manager Create Azure Managed Application that deploys storage account encrypted with customer-managed key ...ed-applications/create-storage-customer-managed-key.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 demonstrates a Windows bias in several areas. PowerShell is presented as the first and primary example for building the Bicep template, with Azure CLI only shown as an alternative. There are no explicit Linux or macOS-specific instructions or examples, and the use of Visual Studio Code is described without mention of platform-specific setup steps. The documentation does not provide parity for Linux users in terms of command-line usage, troubleshooting, or tool installation.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Include explicit instructions for Linux and macOS users, such as installation commands for Azure CLI and Bicep on those platforms.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., file permissions, path differences).
  • Clarify that Visual Studio Code and its extensions are available on all major platforms, and provide installation links for Linux/macOS.
  • Avoid using Windows-centric terminology (such as referencing PowerShell as the default) unless necessary, and ensure all steps are platform-neutral or provide alternatives.
GitHub Create Pull Request
Azure Resource Manager Deploy a service catalog managed application ...aged-applications/deploy-service-catalog-quickstart.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 displays a moderate Windows bias. Azure PowerShell examples are consistently presented before Azure CLI examples, and instructions reference opening a PowerShell terminal in Visual Studio Code (a Windows-centric workflow) before mentioning Bash. The use of PowerShell-specific syntax (backtick for line continuation and escaping) is explained in detail, while Bash/Linux equivalents are covered but with less emphasis. Visual Studio Code is recommended as the editor, which is cross-platform, but the terminal instructions default to PowerShell first. There is no explicit mention of Linux-specific tools or workflows, and the CLI instructions assume Bash, but do not address other common Linux shells or environments. No Linux-only features or troubleshooting are discussed.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI examples so that CLI (Linux-friendly) is sometimes presented first.
  • Explicitly mention that Bash instructions apply to Linux, macOS, and Windows (with WSL or Git Bash), and clarify any differences for Linux users.
  • Provide more detailed explanations of Bash/Linux shell syntax, especially for users unfamiliar with escape characters and line continuation.
  • Include troubleshooting tips or notes for Linux users, such as file permissions, environment variables, or common issues with Azure CLI on Linux.
  • Reference Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code.
  • Where possible, add links to Azure CLI installation instructions for Linux distributions and clarify cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Create and deploy template spec ...-manager/templates/quickstart-create-template-specs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits Windows bias in several ways: file paths are exclusively given in Windows format (e.g., C:\Templates\...), there are no Linux/macOS path or shell examples, and PowerShell is featured prominently alongside Azure CLI. Windows tools and conventions (such as PowerShell and Windows file paths) are mentioned and used throughout, while Linux equivalents (e.g., bash, Linux file paths) are missing. The portal instructions also reference Windows-style file locations. There is no guidance for Linux users on saving files, running commands, or handling file paths, and no mention of cross-platform considerations.
Recommendations
  • Provide Linux/macOS shell examples (e.g., bash) alongside PowerShell and Azure CLI.
  • Use cross-platform or dual file path examples (e.g., C:\Templates\... and ~/Templates/...).
  • Explicitly mention that Azure CLI works on Linux/macOS and provide instructions for those platforms.
  • Add notes or tabs for Linux/macOS users, especially for file saving and command execution.
  • Avoid recommending PowerShell as the primary tool; present CLI and PowerShell equally, or default to CLI for cross-platform parity.
  • Update portal instructions to clarify that file selection works with both Windows and Linux/macOS file systems.
GitHub Create Pull Request
Azure Resource Manager Roll back on error to successful deployment .../azure-resource-manager/templates/rollback-on-error.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 Windows bias by presenting PowerShell examples before Azure CLI examples, using Windows-style file paths in PowerShell commands, and referencing Windows-specific tools (PowerShell) without equal emphasis on Linux-native equivalents. The PowerShell section appears first, and the file path syntax (e.g., c:\MyTemplates\azuredeploy.json) is Windows-specific, which may confuse Linux users. There are no Bash or Linux shell examples, nor are there notes about cross-platform usage for PowerShell or CLI.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Include Linux/Bash shell examples, especially for Azure CLI usage, with Linux-style file paths (e.g., /home/user/MyTemplates/azuredeploy.json).
  • Add notes clarifying that PowerShell is available cross-platform, and provide instructions or examples for using PowerShell on Linux/macOS.
  • Where file paths are shown, provide both Windows and Linux path formats.
  • Explicitly mention cross-platform compatibility for all tools and commands, and link to installation guides for Linux users.
GitHub Create Pull Request
Azure Resource Manager Deploy ARM template with SAS token - Azure Resource Manager | Microsoft Docs ...ce-manager/templates/secure-template-with-sas-token.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. PowerShell examples are consistently presented before Azure CLI examples, and file paths in examples use Windows-style (e.g., c:\Templates\azuredeploy.json). The PowerShell tab is listed first in each code section, and references to environments (such as Bash) are only made in passing for CLI, with no explicit Linux file path examples. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux-specific usage or considerations.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side to avoid implicit prioritization.
  • Include Linux-style file paths (e.g., /home/user/Templates/azuredeploy.json) in CLI examples to demonstrate cross-platform usage.
  • Explicitly mention and provide examples for running Azure CLI commands in both Windows (CMD/PowerShell) and Linux (Bash) environments.
  • Add notes or tips about differences in environment variables, path syntax, and shell behavior between Windows and Linux.
  • Ensure that references to tools and environments do not assume Windows as the default; clarify cross-platform applicability throughout.
GitHub Create Pull Request
Azure Resource Manager Create and publish Azure Managed Application in service catalog ...er/managed-applications/publish-service-catalog-app.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 demonstrates a moderate Windows bias. Azure PowerShell examples and terminology are presented before Azure CLI (which is more cross-platform and Linux-friendly), and PowerShell-specific concepts like 'splatting' are explained in detail. The instructions for opening a terminal default to PowerShell first, with Bash mentioned as an alternative only in the CLI section. There are no explicit Linux-specific instructions or examples (e.g., using Linux-native tools for zipping files, or referencing Linux shell conventions), and the guidance for Visual Studio Code does not address Linux-specific setup or alternatives.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better support Linux users.
  • Include explicit Linux instructions for tasks like creating zip files (e.g., using 'zip' command), and clarify that Bash terminals are available on Linux and macOS.
  • Add notes about using Visual Studio Code on Linux, including installation links and any relevant differences.
  • Reference Linux-native shell conventions (e.g., use $HOME instead of %USERPROFILE%) where appropriate.
  • Avoid PowerShell-specific terminology (like 'splatting') without providing equivalent Bash/Linux shell explanations.
  • Ensure all examples and screenshots are platform-neutral or provide Linux-specific variants where UI or workflow differs.
GitHub Create Pull Request
Azure Resource Manager Tutorial - custom actions & resources ...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 bias towards Windows environments by providing a detailed PowerShell script for packaging and uploading the application artifacts to Azure Storage, while omitting equivalent Linux/macOS shell (bash/azcopy) examples. Windows tools and patterns (PowerShell cmdlets, $RANDOM variable, etc.) are presented first and exclusively in the artifact upload section. There is no mention of Linux-native approaches or cross-platform alternatives for these steps, despite the Azure CLI examples being cross-platform in later sections.
Recommendations
  • Provide equivalent bash or shell script examples for packaging and uploading artifacts to Azure Storage, using azcopy or Azure CLI commands.
  • Explicitly mention that the PowerShell example is for Windows and offer a Linux/macOS alternative.
  • Avoid using Windows-specific environment variables (e.g., $RANDOM) without cross-platform notes.
  • Add a note or section highlighting cross-platform compatibility and how Linux/macOS users can perform the same steps.
  • Ensure that all tooling references (e.g., PowerShell, Azure CLI) are presented with parity, or at least link to Linux/macOS instructions where appropriate.
GitHub Create Pull Request
Azure Resource Manager Bring your own storage to create and publish an Azure Managed Application definition ...ions/publish-service-catalog-bring-your-own-storage.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. Azure PowerShell examples are consistently presented before Azure CLI (Bash) examples, and PowerShell-specific features like splatting are explained in detail. Visual Studio Code is recommended as the editor, which is cross-platform, but the overall flow and explanations (such as variable usage and command output) are tailored to PowerShell/Windows users. There is a brief mention of Git Bash for Windows, but no equivalent troubleshooting or tips for Linux shells. No explicit Linux-only examples, tools, or workflows are provided.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples, or present CLI first to balance platform focus.
  • Include troubleshooting notes for common Linux shell issues (e.g., quoting, environment variables) similar to the Git Bash note for Windows.
  • Add explicit statements that all CLI commands work on Linux/macOS, and provide links to shell-specific documentation.
  • Mention Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code for users who prefer them.
  • Where PowerShell features (like splatting) are explained, provide equivalent Bash scripting tips for Linux users.
  • Ensure that all instructions and explanations are equally clear for both Windows and Linux users, avoiding assumptions about the user's platform.
GitHub Create Pull Request
Azure Resource Manager What are the resource providers for Azure services ...anager/management/azure-services-resource-providers.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 mild Windows bias. In the 'Find resource provider' section, PowerShell is given as the second example after Azure CLI, and the output shown is from Windows PowerShell. There is a reference to the 'Windows Azure Service Management API' in the registration section, and some resource providers and services are Windows-specific (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP, Microsoft.SerialConsole for Windows). There are no explicit Linux shell examples (such as bash or zsh), nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Add Linux shell (bash/zsh) examples for listing resources and resource providers using Azure CLI, showing typical Linux output formatting.
  • Include references to Linux-specific Azure services or resource providers where relevant, or clarify cross-platform applicability.
  • When mentioning PowerShell, clarify that Azure PowerShell is available cross-platform, and consider showing examples run on Linux.
  • Avoid using 'Windows' in API names or explanations unless necessary; clarify when APIs or services are platform-neutral.
  • Balance the order of examples so that Linux and Windows approaches are presented equally, or explicitly state cross-platform compatibility.
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 a mild Windows bias. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. In both 'Delete resource group' and 'Delete resource' sections, PowerShell examples are listed first, which may implicitly prioritize Windows users. There are no explicit Linux shell (bash) examples, nor are Linux-specific tools or patterns mentioned. The Python examples are cross-platform, but no attention is given to Linux-specific command-line usage or considerations.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash-specific usage notes if relevant.
  • Add bash script examples for common deletion tasks to improve Linux parity.
  • Clarify that PowerShell is available on Linux, but Azure CLI is the default/preferred tool for Linux users.
  • Review screenshots and instructions in the Portal section to ensure they are not Windows-specific (e.g., file paths, UI elements).
GitHub Create Pull Request
Azure Resource Manager Configure data boundary ...re-resource-manager/management/manage-data-boundary.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 Tools Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, REST API, and mentions the Azure portal. However, PowerShell is featured prominently and referenced in links and examples, which may indicate a Windows bias. The documentation links to PowerShell-specific resources before CLI or REST equivalents, and troubleshooting/role assignment guidance references PowerShell first. There are no explicit Linux-specific examples, nor is there mention of Linux-native scripting or shell environments (e.g., Bash), and PowerShell is a Windows-centric tool (though now cross-platform, its usage is still more common on Windows).
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate Linux-native usage.
  • Ensure links to Azure CLI documentation are given equal prominence to PowerShell links.
  • Where PowerShell is referenced, clarify that Azure CLI is fully supported on Linux and macOS, and provide guidance for those platforms.
  • Avoid using PowerShell-specific terminology (e.g., 'cmdlet') without also referencing CLI equivalents.
  • Consider adding troubleshooting steps using Azure CLI in addition to PowerShell.
  • Review ordering of examples and documentation links to avoid listing Windows/PowerShell first unless justified by usage statistics.
GitHub Create Pull Request
Azure Resource Manager Use APIs to create a private link for managing Azure resources ...ager/management/create-private-link-access-commands.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 provides both Azure CLI and PowerShell examples, but PowerShell (a Windows-centric tool) is given equal prominence and detailed usage instructions. There is no mention of Linux-specific tools or shell patterns (e.g., Bash), nor is there any explicit guidance for Linux users. The PowerShell examples and references to Connect-AzAccount suggest a Windows bias, as PowerShell is primarily used on Windows, and its usage is highlighted alongside CLI. REST API examples are platform-neutral, but the lack of Linux/Bash-specific instructions or examples is notable.
Recommendations
  • Add explicit Bash examples for Linux users, especially for authentication and scripting.
  • Clarify that Azure CLI works cross-platform and provide shell-specific instructions (e.g., Bash, zsh).
  • Mention that PowerShell Core is available on Linux, or provide links to install/use it on Linux if PowerShell examples are retained.
  • Include notes or tabs for Linux/macOS users, highlighting any differences or prerequisites.
  • Ensure that CLI examples use syntax and patterns common to Linux shells (e.g., environment variables, piping, jq for JSON parsing).
GitHub Create Pull Request
Azure Resource Manager Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources ...azure-resource-manager/management/deployment-models.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used exclusively in command examples, with no Azure CLI or Bash equivalents provided alongside. Windows tools and patterns (such as remote desktop and remote PowerShell traffic) are mentioned before Linux equivalents (SSH), and the 'Next steps' section links only to PowerShell deployment instructions. There is a lack of Linux-focused examples or references, and Azure CLI is only mentioned as an afterthought in migration guidance, not in main command examples.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands throughout the documentation.
  • Mention Linux tools and patterns (such as SSH) equally or before Windows-specific ones when discussing connectivity and management.
  • Include links to both PowerShell and Azure CLI deployment guides in the 'Next steps' section.
  • Add explicit examples and instructions for Linux-based virtual machines, including template deployment and management.
  • Ensure diagrams and architecture references are not Windows-centric (e.g., avoid only referencing 'Run a Windows VM on Azure').
GitHub Create Pull Request
Azure Resource Manager Manage Azure resources by using the REST API ...e-resource-manager/management/manage-resources-rest.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 provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell is given equal prominence and is referenced in links and examples. There are several references to PowerShell-specific workflows and tools (such as Visual Studio Code and PowerShell deployment guides), and PowerShell is presented as a primary method for interacting with Azure REST APIs. There is a lack of explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI, and Windows-centric tools and patterns (PowerShell, Visual Studio Code) are mentioned before or instead of Linux alternatives.
Recommendations
  • Add explicit bash shell examples for authentication and REST calls, especially for Linux users.
  • Include references to Linux-native tools (e.g., wget, curl in bash scripts) and editors (e.g., Vim, VS Code on Linux) where applicable.
  • Ensure that Azure CLI examples are presented first or with equal prominence to PowerShell, as CLI is cross-platform.
  • Provide links to Linux-specific deployment guides and documentation, not just PowerShell-based workflows.
  • Avoid assuming Visual Studio Code or PowerShell as the default tooling; mention alternatives or clarify cross-platform support.
GitHub Create Pull Request
Azure Resource Manager Move Microsoft.Resources resources to new region ...manager/management/microsoft-resources-move-regions.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 page demonstrates Windows bias by exclusively using Windows-style file paths (e.g., c:\export), omitting Linux/macOS equivalents. All examples for Azure CLI and PowerShell use Windows paths and do not mention or show Linux alternatives (such as /home/user/export). The export and deployment instructions reference Windows tools and patterns, and there is no guidance for Linux users regarding file system conventions or shell usage.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples, especially for file paths (e.g., use /home/user/export in CLI examples).
  • Explicitly mention that Azure CLI and PowerShell are cross-platform and provide platform-specific instructions where relevant.
  • Add notes or sections clarifying differences in command syntax or file system conventions between Windows and Linux/macOS.
  • Ensure links to deployment instructions include both PowerShell and Bash/CLI options.
  • Avoid using only Windows-centric terminology and patterns; strive for parity in documentation for all supported platforms.
GitHub Create Pull Request
← Previous Page 10 of 52 Next →