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 476-492 of 492 flagged pages
Azure Resource Manager
Troubleshoot Bicep file deployments
...leshooting/quickstart-troubleshoot-bicep-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all deployment and cleanup commands, but PowerShell is featured equally and sometimes with more detail (e.g., parameter replacement instructions). The prerequisites mention Azure PowerShell before Azure CLI, and there are no explicit Linux/macOS-specific notes or examples. The use of Visual Studio Code is cross-platform, but command-line instructions do not acknowledge Linux/macOS shell differences or provide bash-specific tips.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide bash-specific notes where relevant (e.g., line continuation, quoting).
- List Azure CLI before PowerShell in prerequisites and examples to reflect its cross-platform nature.
- Add a note clarifying that PowerShell examples are primarily for Windows, and Linux/macOS users should use Azure CLI.
- Include screenshots or references for Linux/macOS terminal usage where appropriate.
- Ensure parameter replacement instructions are provided for both CLI and PowerShell, not just PowerShell.
Create Pull Request
Azure Resource Manager
Resource provider registration errors
...er/troubleshooting/error-register-resource-provider.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resolving resource provider registration errors, but the PowerShell section is given equal prominence and detail as the CLI section. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can create a subtle Windows bias, especially since PowerShell is often associated with Windows environments. However, the CLI examples are present and complete, and no steps are Windows-exclusive. The portal instructions are platform-neutral.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS/Windows, while PowerShell is most commonly used on Windows (though it is available cross-platform).
- Consider listing Azure CLI examples before PowerShell, as CLI is the default for cross-platform usage.
- Add a note or section for Linux/macOS users, confirming that all CLI steps are fully supported.
- If PowerShell is mentioned, clarify its cross-platform availability, but avoid implying it is the primary or preferred method for all users.
Azure Resource Manager
Resource declaration in Bicep
...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for querying supported resource locations, but PowerShell (a Windows-centric tool) is presented first, which may subtly prioritize Windows users. No Linux-specific tools or shell examples are given, but Azure CLI is cross-platform. There are no exclusive Windows-only examples, and the rest of the documentation is platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily used on Windows.
- Consider adding Bash shell examples or notes for Linux users where relevant.
- Ensure future documentation alternates or randomizes the order of platform-specific examples to avoid implicit prioritization.
Azure Resource Manager
Move Azure resources across resource groups, subscriptions, or regions
...resource-manager/management/move-resources-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing tools for moving resources, which may suggest a subtle Windows-first bias. However, no examples, commands, or instructions are given for either PowerShell or CLI, and no Windows-specific tools or patterns are described. There are no explicit PowerShell-heavy sections, nor are Linux examples missing, as none are provided for any platform.
Recommendations
- When listing tools, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Provide example commands for both Azure CLI and Azure PowerShell, ensuring parity and clarity for users on Linux, macOS, and Windows.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add links to platform-specific guidance (e.g., using Azure CLI on Linux) where appropriate.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/linter.md
...b/main/articles/azure-resource-manager/bicep/linter.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation page mentions Visual Studio Code and the Bicep CLI as the primary tools for using the Bicep linter. While these tools are cross-platform, the page references the linter rule 'use-recent-az-powershell-version', which is specific to Windows and PowerShell environments. No explicit Linux or bash examples, nor mentions of Linux-specific tools or workflows, are provided. The documentation does not show command-line usage examples that clarify compatibility or usage differences between Windows and Linux shells.
Recommendations
- Add explicit examples of using Bicep CLI and linter in Linux environments, such as bash or zsh.
- Clarify that Visual Studio Code and Bicep CLI are cross-platform and provide installation or usage notes for Linux users.
- Include references or examples for Azure CLI usage, which is more common in Linux environments, alongside or instead of PowerShell-specific rules.
- If mentioning PowerShell-specific rules, provide equivalent guidance for bash or other Linux shells where possible.
- Add screenshots or terminal output examples from Linux environments to demonstrate parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/operators-comparison.md
...s/azure-resource-manager/bicep/operators-comparison.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references 'Azure CLI or Azure PowerShell' for deploying Bicep files, with Azure PowerShell (a Windows-centric tool) mentioned alongside Azure CLI. No explicit Linux-specific tools or shell examples are provided, and the order of mention (CLI first, then PowerShell) is not strongly biased, but the inclusion of PowerShell without mentioning Bash or Linux-native workflows may suggest a mild Windows-first bias. All code examples are in Bicep, which is platform-agnostic.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- If referencing PowerShell, also mention Bash or shell equivalents for Linux users, or clarify that PowerShell Core is available cross-platform.
- Provide example commands for deploying Bicep files using Azure CLI in Bash (Linux/macOS) and PowerShell (Windows), or link to platform-specific deployment guides.
- Ensure that introductory or instructional text does not implicitly prioritize Windows tools or workflows over Linux equivalents.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/outputs.md
.../main/articles/azure-resource-manager/bicep/outputs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Azure PowerShell (commonly used on Windows) and Azure CLI examples for retrieving output values, but the PowerShell example is listed first. No other Windows-specific tools, patterns, or examples are present, and Linux parity is generally maintained elsewhere.
Recommendations
- List Azure CLI examples before Azure PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux and macOS.
- Explicitly mention that both Azure CLI and Azure PowerShell are available on all major platforms, but CLI is often preferred for Linux/macOS users.
- Consider providing Bash or shell scripting examples where relevant, especially for automation scenarios.
- Review other documentation pages for consistent ordering and parity between Windows and Linux tooling.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/bicep/resource-declaration.md
...s/azure-resource-manager/bicep/resource-declaration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for determining supported resource locations, but the PowerShell example is presented first. There are no Linux-specific tools or shell examples (e.g., Bash), but Azure CLI is cross-platform. No exclusive Windows tools or patterns are used, and no examples are missing for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though available cross-platform).
- Where possible, add Bash shell examples for common tasks, especially for scripting scenarios.
- Ensure that any references to tooling or workflows do not assume a Windows environment by default.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/custom-providers/tutorial-get-started-with-custom-providers.md
...roviders/tutorial-get-started-with-custom-providers.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or instructions, but it also does not mention or demonstrate Linux tools, shell commands, or patterns. There is a lack of explicit parity for Linux users, as no examples or references are given for Linux environments, even though Azure CLI and REST APIs are cross-platform.
Recommendations
- Add explicit examples using Bash or other Linux shells when demonstrating command-line interactions.
- Mention that Azure CLI and REST API instructions are cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).
- Where relevant, include notes or tips for Linux users, such as authentication methods, environment setup, or script execution differences.
- Ensure that any referenced scripts or automation steps are shown in both PowerShell and Bash formats.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/relocation/includes/app-service-certificates.md
...gement/relocation/includes/app-service-certificates.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or commands, but it also omits any mention of Linux or cross-platform tools for certificate export/import. There is no explicit Windows bias, but the lack of Linux-specific guidance or examples may leave Linux users without clear instructions.
Recommendations
- Add explicit examples for exporting and importing certificates using cross-platform tools such as OpenSSL.
- Include command-line instructions for both Windows (e.g., PowerShell) and Linux (e.g., Bash) environments where relevant.
- Mention common Linux certificate management patterns and tools to ensure parity.
- Clarify that the export/import process can be performed on any supported OS, and link to platform-agnostic guides where possible.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resource-groups-portal.md
...ce-manager/management/manage-resource-groups-portal.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively provides instructions and screenshots for managing Azure resource groups via the Azure portal, with no mention of command-line tools or scripts. There are no examples for Linux users (e.g., Azure CLI, Bash), nor for Windows users (e.g., PowerShell). However, the absence of Linux-oriented command-line examples (such as Azure CLI) is a notable gap, as these are commonly used on Linux and cross-platform environments.
Recommendations
- Add Azure CLI examples for each major operation (create, list, delete, lock, tag resource groups) alongside the portal instructions. Azure CLI is cross-platform and widely used on Linux.
- If including PowerShell examples, ensure Azure CLI examples are presented first or side-by-side to avoid Windows-first bias.
- Explicitly mention that the Azure portal is platform-agnostic, but provide links or sections for users who prefer command-line tools (especially Linux users).
- Include a section comparing different management methods (Portal, Azure CLI, PowerShell) and link to relevant documentation for each.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/manage-resource-groups-python.md
...ce-manager/management/manage-resource-groups-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but presents the Windows instructions first, followed by Linux and macOS. There is no exclusive use of Windows tools or missing Linux examples; parity is maintained in the examples and CLI usage. However, the ordering of instructions may subtly prioritize Windows users.
Recommendations
- Present environment setup instructions in a neutral or alphabetical order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
- Explicitly state that all platforms are equally supported at the beginning of the prerequisites section.
- Ensure that editor-specific notes (e.g., Visual Studio restart) are balanced with equivalent notes for popular Linux/macOS editors (e.g., VS Code, PyCharm).
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources-portal.md
...re-resource-manager/management/tag-resources-portal.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively covers tagging resources using the Azure portal UI, which is platform-agnostic. However, it does not mention or provide examples for command-line methods (such as Azure CLI, PowerShell, or Bash scripting), which are often important for Linux users. The absence of CLI examples or references may disadvantage Linux users who prefer or require non-GUI workflows.
Recommendations
- Add a 'Command-line alternatives' section with examples using Azure CLI (az tag commands), which are cross-platform and widely used on Linux.
- If mentioning PowerShell, ensure Azure CLI examples are given equal or greater prominence, and provide Bash scripting examples where relevant.
- Reference documentation for both Azure CLI and PowerShell for tagging resources, making it clear that both are supported and linking to their respective guides.
- Clarify that the Azure portal is accessible from any OS, but that automation and scripting can be achieved via CLI tools on Linux, macOS, and Windows.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/management/tag-resources-python.md
...re-resource-manager/management/tag-resources-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows, Linux, and macOS, but lists Windows instructions first and offers more detail for Windows (including both 'setx' and 'set', and a Visual Studio restart note). Linux and macOS instructions are present and correct, but are listed after Windows and are slightly less detailed regarding editor restart requirements.
Recommendations
- Present environment setup instructions in a neutral order (e.g., alphabetical: Linux, macOS, Windows) or group them together to avoid implying priority.
- Ensure parity in detail for all platforms (e.g., mention restarting editors for Linux/macOS as well, not just Windows/Visual Studio).
- If providing editor-specific notes (like Visual Studio), consider including equivalents for common Linux/macOS editors (e.g., VS Code, PyCharm).
- Consider a single cross-platform table or section for environment variable setup, with platform-specific commands clearly labeled but not prioritized.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/copy-resources.md
...les/azure-resource-manager/templates/copy-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Azure PowerShell and Azure CLI when discussing version requirements for supporting zero-count copy loops, but lists PowerShell before CLI. There are no explicit Linux or cross-platform shell examples (e.g., Bash), and no mention of Linux-specific tools or patterns. However, the bias is minimal, as both CLI and PowerShell are referenced, and the examples are all in ARM template JSON, which is platform-agnostic.
Recommendations
- List Azure CLI before Azure PowerShell when referencing cross-platform tools, or mention both together as 'Azure CLI or PowerShell' to avoid implying a Windows-first workflow.
- Explicitly state that Azure CLI is available on Linux, macOS, and Windows, reinforcing cross-platform support.
- Where possible, add example deployment commands for both Azure CLI (e.g., 'az deployment group create ...') and PowerShell ('New-AzResourceGroupDeployment ...'), showing parity.
- If referencing shell commands, provide both Bash and PowerShell variants, or clarify that the instructions apply equally to all supported platforms.
- Consider a note or section highlighting cross-platform compatibility for ARM/Bicep deployments.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/resource-location.md
.../azure-resource-manager/templates/resource-location.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for retrieving resource locations, but the PowerShell (Windows-centric) example is listed before the Azure CLI example. No explicit Linux or Bash-specific examples are provided, but the CLI example is cross-platform. There is a slight 'windows_first' bias in the ordering of examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across documentation pages, or explicitly state that Azure CLI commands work on all platforms including Linux and macOS.
- Consider providing Bash-specific examples or notes where relevant, especially for tasks that may differ between platforms.
- Add a brief note clarifying that Azure CLI is available and supported on Windows, Linux, and macOS, to reinforce cross-platform parity.
Azure Resource Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/templates/template-tutorial-add-variables.md
...e-manager/templates/template-tutorial-add-variables.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents deployment instructions for both Azure PowerShell and Azure CLI, but the PowerShell (Windows-centric) example is listed first. There are no Linux-specific shell examples (e.g., Bash), but the Azure CLI example is cross-platform. No exclusive Windows tools or patterns are used, and both tools are referenced in prerequisites. However, the ordering may subtly prioritize Windows users.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across tutorials, or present Azure CLI (which is cross-platform) first to avoid perceived Windows prioritization.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Where possible, provide Bash shell examples for common Linux workflows, especially for tasks like setting variables.
- Clarify in the prerequisites that both Azure PowerShell and Azure CLI are available cross-platform, and link to installation guides for all OSes.