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 151-175 of 1281 flagged pages
Azure Resource Manager
Create a parameters file for bicep deployment
...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While the main deployment examples use Azure CLI (which is cross-platform), all PowerShell examples use Windows paths (C:\MyTemplates\...), and only Azure PowerShell is mentioned (no Bash or Linux shell equivalents). Visual Studio Code is referenced as the primary editor, but no mention is made of Linux-specific editors or shell environments. The PowerShell section is extensive and appears before any mention of Linux shell scripting or automation, and there are no Bash or Linux shell script examples for deploying Bicep files with parameters.
Recommendations
- Add Linux shell (bash) examples for deploying Bicep files with parameters, especially for common scenarios using Azure CLI.
- When showing file paths, provide both Windows (C:\...) and Linux/Mac (~/ or /home/user/...) equivalents.
- Mention Linux and MacOS environments explicitly when discussing tools like Azure CLI and Bicep CLI, including installation and usage notes.
- Include references to Linux-native editors (such as Vim, Nano, or VS Code on Linux) when discussing editing parameter files.
- Clarify that Azure CLI commands work identically on Linux, MacOS, and Windows, and show cross-platform usage where appropriate.
Create Pull Request
Azure Resource Manager
Create a private container registry in Azure for Bicep modules
...zure-resource-manager/bicep/private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and the documentation refers to Windows-specific tools and paths first. The local cache path for Windows is described in more detail, while the Linux and Mac paths are less specific. There are no Linux shell (bash) or scripting examples, and the documentation assumes the use of PowerShell or Azure CLI, which may be less familiar to Linux users. Additionally, credential acquisition defaults to Azure CLI or PowerShell, with no mention of Linux-native authentication methods.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (cross-platform) examples first to avoid Windows-first bias.
- Include bash or shell script examples where appropriate, especially for common tasks like retrieving registry information or publishing modules.
- Provide more detailed Linux and Mac path examples, matching the specificity given to Windows paths.
- Mention Linux-native authentication methods or tools (such as managed identities, environment variables, or service principals configured via bash) when discussing credentials.
- Clarify that Azure CLI is cross-platform and can be used on Linux, Mac, and Windows, to encourage parity.
- Where possible, add notes or links for Linux users regarding package installation, file permissions, and other OS-specific considerations.
Azure Resource Manager
Quickstart: Create Bicep files with Visual Studio Code
...icep/quickstart-create-bicep-use-visual-studio-code.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Azure PowerShell is mentioned alongside Azure CLI in prerequisites and deployment/cleanup instructions, but examples and instructions are given for both. However, PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (like Bash) can signal Windows-first thinking. The Visual Studio Code workflow is cross-platform, but there is no explicit mention of Linux or MacOS environments, nor are there any examples tailored for those platforms (e.g., terminal commands, OS-specific notes). No Linux-specific tools or patterns are discussed, and the documentation does not acknowledge platform-specific differences in experience or setup.
Recommendations
- Explicitly state that Visual Studio Code and the Bicep extension work on Windows, Linux, and MacOS.
- Add screenshots or notes showing the workflow on Linux and MacOS (e.g., using the terminal, file explorer differences).
- Include Bash examples for deploying and cleaning up resources, not just Azure CLI (which is cross-platform, but Bash syntax is familiar to Linux users).
- Clarify that Azure PowerShell is available on Linux and MacOS, or recommend Bash/Azure CLI as the default for Linux users.
- Add troubleshooting tips for Linux/MacOS users (e.g., permissions, path issues, installing prerequisites).
- Avoid listing PowerShell before CLI or Bash unless contextually appropriate for the majority of users.
Azure Resource Manager
Create and deploy a deployment stack with Bicep
...e-manager/bicep/quickstart-create-deployment-stacks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is featured prominently throughout, and is listed as a prerequisite alongside Azure CLI. Visual Studio Code is recommended as the editor, which is cross-platform, but the PowerShell examples and terminology may be more familiar to Windows users. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there any examples showing Linux-specific command patterns, environment setup, or troubleshooting. The documentation assumes parity between CLI and PowerShell, but the presence and order of PowerShell examples, and the lack of Linux shell context, indicate a mild Windows bias.
Recommendations
- Add explicit Bash shell examples for key CLI commands, showing usage in a typical Linux terminal.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and mention any OS-specific considerations.
- Include Linux-specific setup instructions (e.g., using apt-get/yum for Azure CLI installation, or referencing ~/.azure for configuration).
- Balance the order of examples so that CLI/Bash is presented first, or alternate the order to avoid implicit prioritization of Windows/PowerShell.
- Mention alternative editors (such as Vim, nano, or Sublime Text) for users who may not use Visual Studio Code.
- Add troubleshooting tips for common Linux issues (e.g., file permissions, environment variables) when running Azure CLI or Bicep.
Azure Resource Manager
Publish modules to private module registry
...ce-manager/bicep/quickstart-private-module-registry.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation consistently provides examples for Azure CLI and Azure PowerShell, but omits Linux-native equivalents (e.g., Bash scripts, shell patterns) and does not mention Linux-specific tooling or editors. Visual Studio and Visual Studio Code are referenced as primary editors, both of which are Windows-centric (VS is Windows-only, VS Code is cross-platform but presented without mention of Linux). PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell examples, and no mention of Linux package managers or shell environments.
Recommendations
- Add Bash shell examples alongside Azure CLI, demonstrating usage in a typical Linux terminal.
- Explicitly mention that Azure CLI commands work cross-platform, and provide Linux-specific instructions for installation and usage.
- Include references to Linux-native editors (e.g., Vim, Emacs) or at least acknowledge their use for Bicep development.
- Clarify that Visual Studio Code is available on Linux and macOS, and provide installation links for those platforms.
- Reduce emphasis on PowerShell, or clarify its cross-platform availability, and provide parity for Linux shell environments.
- Where file paths are referenced, use both Windows (\) and Linux (/) path conventions in examples.
Azure Resource Manager
Create and deploy template specs in Bicep
...rticles/azure-resource-manager/bicep/template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples before Azure CLI examples, and by using PowerShell-specific syntax and patterns. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any examples tailored for Linux environments (such as shell scripting or command-line nuances). The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not address cross-platform considerations or differences in command execution between Windows and Linux.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform) before PowerShell to avoid implicit prioritization of Windows tools.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific examples where relevant (e.g., using export, $(), or quoting conventions).
- Include notes or sections about running these commands in Linux environments, such as using Bash or Zsh, and highlight any differences in syntax or behavior (e.g., environment variable usage, file paths).
- Add troubleshooting tips or caveats for Linux users, such as file permission issues, case sensitivity, or shell quoting.
- Consider including screenshots or terminal output from Linux shells to reinforce cross-platform parity.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While both Azure PowerShell and Azure CLI are mentioned as prerequisites, the PowerShell example for building the Bicep file is presented first, followed by the Azure CLI example. There are no explicit Linux-specific instructions, nor are there examples showing command-line usage in a Linux shell (e.g., Bash). The instructions and screenshots are focused on the Azure Portal UI, which is cross-platform, but there is no mention of Linux-specific tools, patterns, or considerations. The documentation does not provide parity for Linux users in terms of command-line examples or environment-specific notes.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples to avoid implicit Windows-first bias.
- Include explicit Bash shell examples for Linux users where command-line operations are described.
- Add notes or sections highlighting any differences or considerations for Linux environments (e.g., file paths, shell commands, package installation).
- Clarify that Visual Studio Code and Azure CLI are cross-platform and provide installation links or instructions for Linux.
- Where PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide installation instructions for those platforms.
Azure Resource Manager
Deploy a service catalog managed application
...aged-applications/deploy-service-catalog-quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples (which are most commonly used on Windows) are consistently presented before Azure CLI examples. Instructions for opening terminals specify PowerShell first and reference Visual Studio Code, which is more popular on Windows. The documentation discusses PowerShell-specific syntax (backtick for escaping and line continuation) in detail, while Bash/Linux equivalents are explained more briefly. There is no mention of Linux-specific tools or environments (e.g., native Linux terminal, WSL, or alternative editors). The overall structure and example ordering favor Windows users and workflows.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples, or present CLI first in some sections to balance platform representation.
- Explicitly mention Linux environments (e.g., native Bash, GNOME Terminal, KDE Konsole) and editors (e.g., Vim, Nano) alongside Visual Studio Code.
- Provide guidance for running Azure CLI commands in native Linux terminals, not just Git Bash.
- Expand explanations of Bash/Linux syntax and escape characters to match the detail given for PowerShell.
- Include troubleshooting notes or tips for common Linux-specific issues (e.g., file permissions, environment variables).
- Reference WSL (Windows Subsystem for Linux) for Windows users who prefer Bash, and clarify cross-platform compatibility of commands.
Azure Resource Manager
Use Bicep to deploy an Azure Managed Application definition
...anager/managed-applications/deploy-bicep-definition.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio Code is recommended as the editor, and PowerShell is consistently presented as the first option in all code tabs and examples. The instructions for opening terminals default to PowerShell and Bash, with Bash only mentioned as an alternative if Git is installed. Windows-specific tools and patterns (such as PowerShell splatting) are explained, while Linux-specific equivalents are not discussed. There are no explicit Linux-only examples, and the CLI instructions are presented after PowerShell in every case.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI first in some sections to avoid Windows-first bias.
- Explicitly mention Linux environments and terminal options (e.g., GNOME Terminal, Konsole) alongside PowerShell/Bash.
- Provide guidance for using editors other than Visual Studio Code, such as Vim, Nano, or Emacs, which are popular on Linux.
- Explain CLI-specific patterns and features (such as parameter files, output parsing) with Linux shell examples (e.g., jq, grep) where appropriate.
- Ensure that all instructions and explanations are equally applicable to Linux and macOS users, not just Windows/PowerShell users.
Azure Resource Manager
Manage Azure resources by using the REST API
...e-resource-manager/management/manage-resources-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining access tokens and making REST API calls, but PowerShell is given equal or slightly more prominence than Linux-native tools. References to Visual Studio Code and PowerShell are present, with links to PowerShell-specific deployment guides. There are no explicit Linux shell script examples beyond Azure CLI/cURL, and Windows tools (PowerShell, Visual Studio Code) are mentioned before or instead of Linux alternatives.
Recommendations
- Add explicit Bash shell script examples for REST API calls, especially for authentication and resource management.
- Include references to Linux-native editors (e.g., Vim, nano) or cross-platform alternatives when discussing template editing, not just Visual Studio Code.
- Ensure that Azure CLI examples are presented before PowerShell, or at least equally, to avoid Windows-first impression.
- Provide links to Linux-specific deployment guides alongside PowerShell guides.
- Mention that Azure CLI and cURL commands work natively on Linux, macOS, and Windows, to reinforce cross-platform applicability.
Azure Resource Manager
Move guidance for Cloud Services (extended support) deployment model resources
...nt/move-limitations/cloud-services-extended-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell before Azure CLI when describing move operations, and by not providing explicit Linux-specific examples or guidance. The mention of Azure PowerShell (primarily used on Windows) and lack of Linux shell commands or parity examples suggests a preference for Windows tooling and patterns.
Recommendations
- Provide explicit Linux/Unix shell examples using Azure CLI, including sample commands for moving resources.
- List Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Include notes or sections addressing Linux users, such as prerequisites or environment setup for CLI usage.
- Ensure REST API examples are platform-neutral and provide sample curl commands for Linux users.
Azure Resource Manager
Define multiple instances of a property
...es/azure-resource-manager/templates/copy-properties.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing Windows-specific VM deployment templates, listing Azure PowerShell before Azure CLI in version requirements, and linking only to PowerShell deployment instructions. There are no Linux-specific examples, nor are Linux deployment tools (such as Bash or CLI tutorials) given equal prominence.
Recommendations
- Include example templates for Linux VM deployments alongside Windows examples.
- List Azure CLI before or alongside Azure PowerShell when mentioning supported deployment tools and versions.
- Add links to documentation for deploying ARM templates using Azure CLI and Bash, not just PowerShell.
- Ensure parity in example scenarios and quickstart links for both Windows and Linux environments.
Azure Resource Manager
Configure development environment for deployment scripts in templates | Microsoft Docs
.../templates/deployment-script-template-configure-dev.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is used as the primary scripting language for both Azure PowerShell and Azure CLI container deployment examples, with all deployment and upload steps shown only in PowerShell. The Docker section uses Windows-style drive letter paths (e.g., d:/docker) and does not provide Linux/macOS equivalents for mounting volumes. There are no bash or Linux-native CLI examples for uploading scripts or deploying templates, and the use of Windows-centric tools and patterns is prevalent throughout the page.
Recommendations
- Provide equivalent bash or Azure CLI examples for all PowerShell commands, especially for deployment and file upload steps.
- Include Linux/macOS Docker volume mount syntax (e.g., -v /home/user/docker:/data) alongside Windows examples.
- Mention and demonstrate use of Linux-native tools (e.g., az CLI, bash scripts) for common operations.
- Clarify that the instructions apply to both Windows and Linux environments, and explicitly call out any platform-specific differences.
- Add screenshots or terminal output examples from Linux/macOS environments where relevant.
Azure Resource Manager
Azure Resource Manager deployment modes
...s/azure-resource-manager/templates/deployment-modes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first in the deployment mode example section, with a Windows-style file path (c:\MyTemplates\storage.json) used in the PowerShell example. The CLI example follows, but there is no explicit mention of Linux shell usage, nor are Linux-specific considerations (such as file paths or shell environment) discussed. The 'Next steps' section links to a PowerShell-focused deployment guide before mentioning REST API operations, further reinforcing the Windows-first pattern.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid Windows-first bias.
- Use platform-neutral file paths in examples (e.g., ./MyTemplates/storage.json) or provide both Windows and Linux path formats.
- Explicitly mention that Azure CLI is cross-platform and provide example commands in both Bash and PowerShell where appropriate.
- Include links to Linux-specific deployment guides or documentation alongside PowerShell guides in the 'Next steps' section.
- Add a brief note clarifying that both PowerShell and CLI are available on multiple platforms, and highlight any platform-specific considerations.
Azure Resource Manager
Create parameter file
...es/azure-resource-manager/templates/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style paths (C:\MyTemplates\...) and references Windows-specific tooling (Visual Studio). The PowerShell example is given immediately after the CLI example, and additional notes about parameter name conflicts are specific to PowerShell. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific tools or editors mentioned. The Visual Studio tip is Windows-centric, and file path conventions are Windows-first.
Recommendations
- Add Linux/Bash shell examples for deploying templates with parameter files, using Linux-style paths (e.g., /home/user/storage.parameters.json).
- Mention cross-platform editors (e.g., VS Code) alongside Visual Studio, or clarify that Visual Studio is Windows-only.
- Include notes about file path conventions for both Windows and Linux/Mac environments.
- Provide parity in troubleshooting tips for both PowerShell and Bash/CLI users.
- Clarify that Azure CLI is cross-platform and highlight its usage on Linux/Mac as well as Windows.
Azure Resource Manager
Deploy to Azure button
...e-resource-manager/templates/deploy-to-azure-button.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides a PowerShell example for URL encoding but does not offer equivalent examples for Linux or macOS users (e.g., using bash, curl, or Python). This omission may hinder non-Windows users, as PowerShell is primarily a Windows tool. The example is presented as the only way to perform URL encoding locally, implicitly prioritizing Windows tooling and patterns.
Recommendations
- Add Linux/macOS command-line examples for URL encoding, such as using Python, bash, or curl.
- Explicitly mention that PowerShell is one option and provide alternatives for other platforms.
- Ensure that future documentation includes cross-platform examples side-by-side, especially for common tasks like encoding or file manipulation.
- Consider a table or section listing equivalent commands for Windows, Linux, and macOS.
Azure Resource Manager
Enable debug logging
...source-manager/troubleshooting/enable-debug-logging.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) for enabling debug logging, explicitly stating that debug logging cannot be enabled via Azure CLI (the cross-platform tool). All enabling examples use PowerShell syntax, with no Bash or Linux-native alternatives. PowerShell commands are presented first in each section, and the documentation refers to PowerShell cmdlets and patterns before CLI equivalents. There is no mention of Linux-specific troubleshooting or alternative approaches for enabling debug logging, leaving Linux users with reduced functionality and guidance.
Recommendations
- Provide parity for enabling debug logging in Azure CLI, or document a workaround for Linux users if the feature is unavailable.
- Include Bash/Linux shell examples where possible, especially for CLI commands.
- Clearly state platform limitations and offer alternative guidance for non-Windows users.
- Consider restructuring sections to present CLI (cross-platform) options before PowerShell, or present both side-by-side.
- Advocate for feature parity in Azure CLI to avoid functionality gaps for Linux/macOS users.
Azure Resource Manager
Use ARM template test toolkit
...icles/azure-resource-manager/templates/test-toolkit.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is heavily PowerShell-centric, requiring PowerShell on all platforms (Windows, Linux, macOS) to use the ARM template test toolkit. Windows installation instructions are presented before Linux and macOS. All usage examples, including those for pipelines, are written in PowerShell, with no alternatives for native Linux shells or other scripting environments. There is no mention of Linux-native tools or patterns, nor are there any Bash or shell script examples for running tests outside of PowerShell.
Recommendations
- Provide Bash or shell script examples for Linux users who do not use PowerShell.
- Clarify if the toolkit can be run via other scripting environments (e.g., Python, Bash) or provide wrappers if possible.
- Consider presenting Linux instructions before or alongside Windows instructions to avoid implicit prioritization.
- Mention any Linux-native alternatives or integration patterns, such as using the toolkit in a Docker container or with common Linux CI/CD tools.
- If PowerShell is a strict requirement, explicitly state this limitation and suggest ways to streamline PowerShell installation for Linux users.
Azure Resource Manager
Create a template spec with linked templates
...urce-manager/templates/template-specs-create-linked.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: file paths are given in Windows format (e.g., c:\Templates\...), PowerShell examples and notes are presented before Azure CLI equivalents, and troubleshooting notes specifically reference Windows PowerShell. There is an assumption of a Windows environment throughout, with no mention of Linux or macOS file systems, shell conventions, or potential platform-specific issues. No Linux/macOS-specific examples or considerations are provided.
Recommendations
- Provide file path examples in both Windows (c:\...) and Linux/macOS (~/Templates/...) formats.
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid implicit prioritization.
- Include troubleshooting notes for Linux/macOS environments, not just Windows PowerShell.
- Explicitly mention that the instructions apply to all major platforms, and call out any platform-specific differences.
- Add examples using Bash shell variable assignment and usage, especially for CLI commands.
- Reference Linux/macOS tools and conventions where relevant (e.g., directory creation commands, file navigation).
Azure Resource Manager
Request disallowed by policy error
...ubleshooting/error-policy-requestdisallowedbypolicy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides troubleshooting steps for the 'RequestDisallowedByPolicy' error in Azure deployments. It offers examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. However, there are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or patterns. The PowerShell section includes detailed usage and tips (e.g., ConvertTo-Json), which are not paralleled in the Azure CLI section. This may disadvantage Linux users who do not use PowerShell.
Recommendations
- Add bash-specific examples for querying policy definitions and assignments using Azure CLI, including output formatting (e.g., using jq for JSON parsing).
- Ensure that Azure CLI examples are as detailed as PowerShell ones, including tips for handling JSON output and filtering results.
- Consider mentioning that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell examples are primarily for Windows users unless PowerShell Core is specified.
- Where advanced output manipulation is shown in PowerShell (e.g., ConvertTo-Json with Depth), provide equivalent Linux command-line techniques (e.g., jq or grep) for parity.
Azure Resource Manager
Use template deployment scripts | Microsoft Docs
...nager/templates/template-tutorial-deployment-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The core deployment script example is written exclusively in PowerShell, which is primarily a Windows-centric scripting language (despite its cross-platform support, most users associate it with Windows). The template resource uses 'kind: AzurePowerShell', and the script content is PowerShell-only, with no Bash or cross-platform alternatives. PowerShell examples and escape rules are discussed in detail, while Linux-native scripting (e.g., Bash) is not mentioned. The CLI examples are present for some steps, but the main deployment script and troubleshooting steps are PowerShell-only. Windows tools and patterns (PowerShell, Visual Studio Code, Azure PowerShell modules) are mentioned before or instead of Linux equivalents. There is no example of using Bash for the deployment script, nor any discussion of Linux-specific troubleshooting or scripting.
Recommendations
- Provide equivalent Bash script examples for the deployment script resource (using 'kind: AzureCLI').
- Discuss Bash-specific quoting and escape rules alongside PowerShell.
- Include troubleshooting steps for Bash-based deployment scripts, not just PowerShell.
- Mention Linux-native tools and editors (e.g., Vim, nano) as alternatives to Visual Studio Code.
- Clarify cross-platform support for deployment scripts and explicitly state when only PowerShell is supported.
- Where possible, alternate the order of presenting CLI and PowerShell examples, or present them side-by-side.
- Add links to documentation about using Bash in deployment scripts and working with outputs from Bash scripts.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Azure PowerShell examples are consistently presented before Azure CLI examples, and PowerShell-specific concepts (such as splatting) are explained in detail. Visual Studio Code is recommended as the editor, but no mention is made of Linux-specific editors or workflows. There is a brief mention of Git Bash for Windows in troubleshooting, but no equivalent advice for Linux shells. The documentation does provide Azure CLI examples throughout, which are cross-platform, but the ordering and depth of PowerShell coverage suggest a Windows-centric approach.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples, or present CLI examples first to better reflect cross-platform usage.
- Add notes or troubleshooting tips for common Linux shells (e.g., bash, zsh) in addition to Git Bash for Windows.
- Mention Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code, or clarify that VS Code is available cross-platform.
- Reduce the emphasis on PowerShell-specific features (like splatting) unless a CLI equivalent is also explained.
- Explicitly state that all CLI examples work on Linux/macOS and Windows, and highlight any platform-specific caveats.
Azure Resource Manager
What are the resource providers for Azure services
...anager/management/azure-services-resource-providers.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. It references 'Windows Azure Service Management API' and includes a PowerShell example alongside Azure CLI and Python, but does not provide Bash or Linux shell examples. The Serial Console section links specifically to 'Azure Serial Console for Windows' without mentioning Linux. Windows-specific resource providers (e.g., Microsoft.WindowsIoT, Microsoft.WindowsDefenderATP, Microsoft.WindowsESU) are present, and Windows terminology appears before Linux equivalents in some cases.
Recommendations
- Add Linux/Bash shell examples alongside PowerShell, especially in sections demonstrating resource listing.
- Include links to both Windows and Linux versions of Azure Serial Console documentation.
- Where Windows-specific APIs or terminology are mentioned, provide Linux equivalents or clarify cross-platform applicability.
- Ensure resource provider tables include Linux-focused services where relevant, and avoid listing Windows services first unless contextually appropriate.
- Review references to Windows Azure Service Management API and clarify if it applies to all platforms or provide Linux alternatives.
Azure Resource Manager
Tutorial - custom actions & resources
...ns/tutorial-create-managed-app-with-custom-provider.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for packaging and uploading the managed application artifacts, with no equivalent Bash or Linux shell examples. Windows tools and patterns (e.g., PowerShell cmdlets like New-AzStorageAccount, Set-AzStorageBlobContent) are presented first and exclusively for key steps such as uploading the application package. While Azure CLI examples are included for deployment, the initial artifact packaging and upload steps lack Linux parity, and there are no explicit instructions or examples for Linux users. This may hinder accessibility and usability for users on non-Windows platforms.
Recommendations
- Add Bash or Azure CLI examples for packaging and uploading the application zip to Azure Storage, using cross-platform tools (e.g., az storage blob upload, curl, or azcopy).
- Present Linux/macOS instructions alongside Windows/PowerShell instructions, or use tabs to separate platform-specific guidance.
- Avoid assuming PowerShell is the default or only scripting environment; clarify when steps are platform-specific.
- Reference cross-platform tools (e.g., azcopy, Azure CLI) before or alongside Windows-specific tools.
- Explicitly mention prerequisites for both Windows and Linux users, including installation of required tools.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for key operations, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is referenced in the private endpoint creation section as a primary method. There is no mention of Linux-specific tools or shell scripting, and PowerShell is listed before REST in some sections. The documentation assumes familiarity with PowerShell and does not offer Bash or Linux shell script equivalents, which may disadvantage Linux users.
Recommendations
- Add explicit Bash/Linux shell script examples alongside Azure CLI commands, showing usage in a Linux environment.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Avoid listing PowerShell before REST or CLI unless there is a technical reason; consider listing CLI first as it is more cross-platform.
- Include notes or links for Linux users on installing and using Azure CLI and relevant authentication methods.
- If referencing PowerShell, also mention alternatives for Linux users (e.g., Bash, zsh, etc.).
- Review referenced links (such as for private endpoint creation) to ensure parity in Linux and Windows instructions.