Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 526-550 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md
...anager/bicep/linter-rule-no-loc-expr-outside-params.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page provides deployment guidance and conflict resolution advice exclusively in terms of Azure PowerShell commands (e.g., New-AzDeployment), which are primarily Windows-centric tools. There are no examples or mentions of equivalent Azure CLI commands, which are cross-platform and commonly used on Linux and macOS. This focus on PowerShell and omission of CLI alternatives demonstrates a Windows-first and PowerShell-heavy bias.
Recommendations
- Add equivalent Azure CLI examples (e.g., az deployment sub create, az deployment mg create, az deployment tenant create, az deployment group create) alongside the PowerShell commands.
- Mention that Azure CLI is cross-platform and provide guidance for both PowerShell and CLI users.
- When discussing parameter name conflicts, explain whether similar issues exist with Azure CLI commands and how to resolve them.
- Ensure that all deployment scenarios (resource group, subscription, management group, tenant) are covered with both PowerShell and CLI examples.
- Consider presenting CLI examples first or in parallel with PowerShell to avoid a Windows-first impression.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authorize-access-azure-active-directory.md
.../event-hubs/authorize-access-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing .NET (DotNet) samples and libraries, which are traditionally associated with Windows environments. There are no Linux-specific or cross-platform CLI examples (such as Azure CLI, Bash, or Python), nor are there any references to Linux tools or shell environments. The samples and migration guides are all focused on .NET, with no parity for other platforms or languages commonly used on Linux.
Recommendations
- Add Azure CLI and Bash examples for role assignment and authentication flows, demonstrating how to perform these tasks from Linux or cross-platform environments.
- Include code samples in additional languages such as Python, Java, or Node.js, which are popular on Linux.
- Reference and link to SDK samples and guides for non-.NET languages and platforms.
- Explicitly mention that the procedures and APIs are platform-agnostic where applicable, and provide guidance for both Windows and Linux users.
- If PowerShell or Windows tools are mentioned, ensure equivalent Linux commands (e.g., Bash, Azure CLI) are presented alongside or before them.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/install.md
...main//articles/azure-resource-manager/bicep/install.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows some Windows bias by listing Windows installation options and tools (such as Visual Studio, PowerShell, Chocolatey, Winget) before or more prominently than Linux equivalents. PowerShell and Windows-specific package managers are given dedicated sections and detailed examples, while Linux and macOS instructions are present but less emphasized. The Visual Studio (Windows-only) workflow is described in detail, and Windows command-line examples (PowerShell, CMD) are more numerous and detailed than Linux shell examples.
Recommendations
- Ensure Linux and macOS installation instructions are as detailed and prominent as Windows instructions, including troubleshooting tips and verification steps.
- Provide equivalent Linux/macOS command-line examples wherever PowerShell or Windows CMD examples are given.
- Avoid listing Windows tools (e.g., Visual Studio, Chocolatey, Winget) before cross-platform or Linux-native tools unless there is a technical reason.
- Add more examples and guidance for Linux-native editors and workflows (e.g., Vim, Emacs, JetBrains IDEs) if relevant.
- Balance the order of sections so that Linux and macOS instructions are not always listed after Windows instructions.
- Where possible, use cross-platform language (e.g., 'terminal' instead of 'command prompt') and avoid assuming the user is on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/deployment-stacks.md
...cles/azure-resource-manager/bicep/deployment-stacks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell (a Windows-centric tool) is consistently presented before Azure CLI in all code example tabs, and PowerShell-specific command syntax is used throughout. There are no explicit Linux shell (bash/zsh) or cross-platform CLI usage notes, and no mention of Linux-specific considerations (such as quoting, line continuation, or environment differences). The documentation assumes familiarity with PowerShell and Windows tools, which may disadvantage Linux or macOS users.
Recommendations
- Alternate the order of Azure CLI and Azure PowerShell examples, or present Azure CLI first, as it is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and provide shell-specific notes where relevant (e.g., line continuation differences: '\' for bash, '`' for PowerShell).
- Add a short section or callout for Linux/macOS users, clarifying any differences in command usage, installation, or environment setup.
- Where possible, provide bash/zsh shell script examples or usage patterns, especially for scripting scenarios.
- Avoid assuming PowerShell as the default scripting environment; clarify that both CLI and PowerShell are supported and cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/migrate-blueprint.md
...cles/azure-resource-manager/bicep/migrate-blueprint.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell-specific documentation for exporting blueprint definitions and mentioning Azure PowerShell before Azure CLI when discussing configuration. There are no explicit Linux/CLI examples or references, and the guidance for exporting blueprints is tied to a PowerShell-centric workflow.
Recommendations
- Provide equivalent Azure CLI commands and documentation links alongside PowerShell references for exporting blueprint definitions.
- When mentioning tools for configuring deployment stack settings (such as DenySettingsMode), list Azure CLI before or alongside Azure PowerShell.
- Include sample migration workflows or command snippets for Linux environments, ensuring parity for users who prefer or require non-Windows tooling.
- Audit linked documentation (such as the export guide) to ensure CLI and cross-platform instructions are present and clearly referenced.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operator-spread.md
...ticles/azure-resource-manager/bicep/operator-spread.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias in the 'Next steps' section, where Azure PowerShell and Visual Studio Code (a Microsoft product) are mentioned as the primary tools for deploying and authoring Bicep files. Azure CLI is mentioned, but PowerShell is listed first, and there is no mention of Linux-native editors or deployment workflows. All examples are platform-neutral Bicep code, but the guidance for running and editing is Windows-centric.
Recommendations
- Present Azure CLI before Azure PowerShell, as Azure CLI is fully cross-platform and more commonly used on Linux.
- Explicitly mention that Bicep files can be deployed from Linux, macOS, and Windows using Azure CLI.
- Include instructions or links for using other editors (such as Vim, Emacs, or JetBrains IDEs) for authoring Bicep files, or clarify that any text editor can be used.
- Provide example deployment commands for both Azure CLI and Azure PowerShell, and ensure parity in documentation.
- Consider adding a note that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/parameter-files.md
...ticles/azure-resource-manager/bicep/parameter-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all PowerShell deployment examples using Windows-style paths (e.g., C:\MyTemplates\...), referencing Visual Studio Code (a tool more commonly used on Windows), and omitting any explicit Linux/bash shell or cross-platform examples for PowerShell commands. There are no bash or Linux shell examples for deploying Bicep files, and all file path conventions are Windows-centric. The documentation also references Azure PowerShell and Visual Studio Code before mentioning the Bicep CLI, and does not show how to use Linux-native tools or file paths.
Recommendations
- Add Linux/bash shell examples for deploying Bicep files using Azure CLI, showing Linux-style paths (e.g., /home/user/templates/storage.bicep).
- Include PowerShell Core examples that use Linux/macOS file paths, or clarify that PowerShell commands work cross-platform.
- When referencing Visual Studio Code, mention that it is available on Linux and macOS, or suggest alternative editors where appropriate.
- Balance the order of tool mentions (e.g., Azure CLI before Azure PowerShell) and ensure that Linux-native workflows are described alongside Windows ones.
- For every example using Windows paths, provide a corresponding example using Linux paths.
- Explicitly state that the Bicep CLI and Azure CLI are cross-platform, and provide installation links or notes for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/operators-access.md
...icles/azure-resource-manager/bicep/operators-access.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily references Windows-centric tools and workflows, such as Azure PowerShell and Visual Studio Code, and does not provide Linux-specific examples or mention Linux-native tools. The 'Next steps' section lists Azure PowerShell before Azure CLI and only references Visual Studio Code, which may suggest a Windows-first approach. There are no explicit Linux or cross-platform command-line examples or editor recommendations.
Recommendations
- In the 'Next steps' section, list Azure CLI before Azure PowerShell or mention both equally to avoid implying a Windows-first workflow.
- Include explicit instructions or links for deploying Bicep files from Linux/macOS terminals using Azure CLI.
- Mention alternative editors that are popular on Linux, such as Visual Studio Code (which is cross-platform), Vim, or other code editors.
- Where possible, provide cross-platform command-line examples and clarify that Bicep and Azure CLI are fully supported on Linux and macOS.
- Add a note or section highlighting that all examples work identically on Linux, macOS, and Windows, and provide troubleshooting links for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/private-module-registry.md
...zure-resource-manager/bicep/private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI examples, and provides detailed PowerShell command usage. There is an emphasis on PowerShell and Windows-specific tools and paths, with Linux and Mac paths only briefly mentioned. No Linux shell-specific examples (e.g., Bash) are provided, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples, or present Azure CLI (cross-platform) examples first to avoid privileging Windows users.
- Include Linux/Bash shell command examples where relevant, especially for scripting or file path manipulation.
- Provide equal detail for Linux and Mac file paths, not just a single path, and explain any differences in behavior or setup.
- Clarify that both Azure CLI and PowerShell are cross-platform, but highlight CLI as the default for Linux/macOS users.
- Add troubleshooting or setup notes specific to Linux/macOS environments, such as permissions or environment variables.
- Where possible, avoid Windows-specific terminology or explain it for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/image-factory-create.md
...ob/main//articles/devtest-labs/image-factory-create.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong bias toward Windows environments by exclusively referencing Azure PowerShell scripts and tools, without mentioning or providing examples for Linux shell scripts or cross-platform alternatives. The orchestration and automation examples are centered around PowerShell and Azure DevOps, with no discussion of Bash, CLI, or Linux-native workflows. This may hinder Linux users from adopting or understanding the solution.
Recommendations
- Include equivalent Bash or Azure CLI script examples alongside PowerShell scripts to ensure Linux users can follow the process.
- Mention and provide links to cross-platform tools and documentation, such as Azure CLI, where possible.
- Explicitly state whether the provided scripts and extensions are compatible with Linux/macOS environments, and provide guidance for those platforms.
- Balance the order of presentation by introducing both Windows and Linux approaches, or clarify if the solution is intentionally Windows-centric.
- If certain features are only available via PowerShell, note this limitation and suggest workarounds or alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/custom-providers/create-custom-provider.md
...rce-manager/custom-providers/create-custom-provider.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples throughout, but for PowerShell users it exclusively recommends and demonstrates the use of ARMClient (armclient.exe), a Windows-centric tool, for making REST API calls. There is no mention of Linux-native alternatives (such as curl or httpie), nor are there Bash or shell script examples for REST calls outside of Azure CLI. This creates a Windows bias by assuming PowerShell/ARMClient as the default non-CLI workflow and omitting Linux-friendly REST tooling.
Recommendations
- For REST API examples, provide Linux-native alternatives using curl or httpie alongside or instead of ARMClient in the PowerShell sections.
- Explicitly mention that ARMClient is primarily a Windows tool, and suggest cross-platform alternatives for Linux/macOS users.
- Where PowerShell is used for scripting, consider providing equivalent Bash/shell script examples for Linux users.
- In the prerequisites, mention Linux-compatible tools for REST operations, not just ARMClient.
- Ensure that all command-line examples are tested and presented in a cross-platform way, clarifying any OS-specific requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/quickstart-private-module-registry.md
...ce-manager/bicep/quickstart-private-module-registry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for all commands, but it exhibits a Windows bias by consistently including PowerShell (a Windows-centric tool) as a primary example, mentioning Visual Studio (a Windows-first IDE) before cross-platform alternatives, and omitting explicit Linux/macOS shell (bash/zsh) examples. There are no bash or shell script equivalents, and the guidance assumes the use of Visual Studio Code or Visual Studio, both of which are more common on Windows. The lack of Linux-specific instructions or troubleshooting further reinforces the Windows-centric approach.
Recommendations
- Add bash/zsh shell script examples alongside PowerShell, especially for variable assignment and command invocation.
- Explicitly mention that Azure CLI commands work cross-platform and provide Linux/macOS-specific notes where file paths or environment setup may differ.
- Include setup and usage instructions for common Linux editors (e.g., Vim, nano) or cross-platform editors (e.g., VS Code) before or alongside Visual Studio.
- Ensure that all prerequisite and installation steps include Linux/macOS guidance (e.g., package manager commands for Bicep CLI and Azure CLI).
- Where PowerShell is referenced, clarify that it is available cross-platform, but provide native shell alternatives for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md
...aged-applications/deploy-service-catalog-quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents both Azure PowerShell and Azure CLI examples in parallel, but consistently lists Azure PowerShell (a Windows-centric tool) first in every code example section. Instructions for opening a terminal default to PowerShell in Visual Studio Code, and PowerShell-specific syntax (such as backtick for line continuation and escaping) is explained in detail, while Bash/Linux equivalents are explained but always second. There is a strong assumption that users are familiar with PowerShell and Windows conventions, and Visual Studio Code is recommended as the editor, which, while cross-platform, is often associated with Windows workflows. No Linux-specific tools or patterns are highlighted, and the overall flow subtly prioritizes Windows/PowerShell users.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples, or present CLI examples first in some sections to avoid always privileging PowerShell/Windows workflows.
- Explicitly mention that Azure CLI commands work natively on Linux and macOS, and provide brief notes for Linux users (e.g., using native terminals, not just Git Bash).
- Where PowerShell-specific syntax (like backtick escaping) is explained, provide equally detailed explanations for Bash/Linux syntax and conventions.
- Include a short section or callout for Linux/macOS users, clarifying that all CLI instructions are fully supported and tested on those platforms.
- Consider referencing other popular Linux editors (e.g., Vim, Nano) or at least note that Visual Studio Code is cross-platform.
- Avoid language that assumes PowerShell is the default or preferred shell, and use neutral phrasing such as 'In your preferred shell...'.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/image-factory-save-distribute-custom-images.md
...st-labs/image-factory-save-distribute-custom-images.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows environments, with exclusive use of Azure PowerShell tasks and PowerShell scripting. There are no examples or instructions for Linux users, such as using Azure CLI, Bash scripts, or cross-platform automation tools. The sample configuration and image paths also reference only Windows images, and all screenshots and workflow steps assume a Windows-centric toolchain.
Recommendations
- Provide parallel examples using Azure CLI and Bash scripts for Linux/macOS users alongside PowerShell examples.
- Include instructions for adding Azure CLI tasks in Azure DevOps build definitions.
- Show sample labs.json entries and image paths for popular Linux distributions (e.g., Ubuntu, CentOS) in addition to Windows images.
- Add screenshots and workflow steps that demonstrate the process on non-Windows platforms or using cross-platform tools.
- Explicitly mention that the process can be performed from Linux/macOS environments and provide any necessary prerequisites or differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/quickstart-create-template-specs.md
...urce-manager/bicep/quickstart-create-template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all examples, regardless of the shell (PowerShell or Azure CLI). There are no Linux/macOS path examples, and no mention of Linux-specific considerations. The documentation also refers to PowerShell and Azure CLI, but PowerShell is always presented first, and the only editor mentioned is Visual Studio Code. Additionally, the 'Grant access' section links only to a PowerShell-based tutorial.
Recommendations
- Provide both Windows and Linux/macOS path examples in all command snippets (e.g., use C:\templates\main.bicep and ~/templates/main.bicep).
- Explicitly mention that file paths should be adapted for the user's operating system.
- Alternate the order of PowerShell and CLI examples, or present CLI first, as it is cross-platform.
- Include links to equivalent Linux/macOS tutorials for tasks such as granting access.
- Clarify that both PowerShell and CLI are available on multiple platforms, but that file path syntax may differ.
- Consider mentioning other editors (such as Vim, nano, or Sublime Text) in addition to Visual Studio Code.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/bicep/template-specs.md
...rticles/azure-resource-manager/bicep/template-specs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and in some sections, PowerShell is mentioned as a primary integration point (e.g., 'integrate the template spec into an existing deployment process such as a PowerShell script'). There is a general assumption of PowerShell usage, and no explicit mention of Linux shell or scripting environments. While Azure CLI is cross-platform, the documentation does not provide any Linux- or Bash-specific context or examples, nor does it mention Linux-native tools or scripting patterns. There are no examples or guidance tailored to Linux users, and PowerShell is sometimes referenced as the default automation tool.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples or present Azure CLI first, as it is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work in Bash, zsh, and other Linux shells, and provide example shell commands (e.g., export variables, use of $() for command substitution).
- Where scripting or automation is discussed, include references to Bash scripts or Linux automation pipelines alongside PowerShell.
- Avoid language that assumes PowerShell as the default scripting tool; instead, refer to 'automation scripts' or 'shell scripts' generically.
- Add a short section or note highlighting Linux compatibility and any Linux-specific considerations for template specs.
- If possible, provide at least one end-to-end example using Bash scripting to create, deploy, and manage template specs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/image-factory-set-up-devops-lab.md
...ticles/devtest-labs/image-factory-set-up-devops-lab.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented towards Windows environments, with exclusive use of Azure PowerShell scripts, references to Windows Task Scheduler, and no mention of Linux-compatible alternatives or examples. There are no instructions or examples for running the image factory using Bash, Azure CLI, or Linux-based automation tools. The documentation assumes familiarity with Windows-centric tools and workflows, and does not address how a Linux user would perform equivalent steps.
Recommendations
- Provide parallel examples using Azure CLI and Bash scripts for all steps currently shown with PowerShell.
- Mention and demonstrate how to run the image factory from Linux-based CI/CD systems (e.g., GitHub Actions, Jenkins on Linux, Azure DevOps Linux agents).
- Include instructions for scheduling and running scripts using Linux-native tools (e.g., cron) alongside Windows Task Scheduler.
- Clarify which scripts or templates are cross-platform and which are PowerShell-specific; if possible, provide cross-platform script versions.
- Explicitly state Linux support status and provide troubleshooting tips for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/resource-group-control.md
.../main//articles/devtest-labs/resource-group-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides a PowerShell script as the only CLI-based example for scripting the configuration of resource groups for DevTest Labs VMs. There are no equivalent examples using Bash, Azure CLI in Bash, or other Linux-native tools. The script invocation and syntax are Windows/PowerShell-specific, and there is no mention of Linux or cross-platform alternatives. The documentation implicitly assumes a Windows environment for scripting, which may exclude or inconvenience Linux/macOS users.
Recommendations
- Add an example using Azure CLI in Bash (sh) syntax to demonstrate how to perform the same operation on Linux/macOS or cross-platform environments.
- Explicitly mention that the Azure CLI commands can be run in any shell, and provide both PowerShell and Bash variants where applicable.
- Avoid using only PowerShell-specific script invocation (e.g., .\ResourceGroup.ps1) and include equivalent Bash script invocation (e.g., ./resource-group.sh) if scripts are provided.
- Where possible, use Azure CLI commands directly in documentation, as they are cross-platform, and supplement with PowerShell only if necessary.
- Add a note clarifying that the instructions apply to both Windows and Linux users, and provide links to Azure CLI installation and usage guides for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/managed-applications/tutorial-create-managed-app-with-custom-provider.md
...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 a detailed PowerShell script for packaging and uploading the application artifacts to Azure Storage, without offering a Linux/bash equivalent. The PowerShell script uses Az PowerShell cmdlets and Windows-specific patterns, and it is presented before the Azure CLI and Portal instructions. There are no bash or cross-platform shell examples for the packaging/upload step, and the documentation assumes familiarity with Windows tooling.
Recommendations
- Provide a bash (Linux/macOS) script example for packaging and uploading the application artifacts to Azure Storage, using Azure CLI commands (e.g., az storage account create, az storage container create, az storage blob upload).
- Clearly indicate which steps are platform-specific and offer alternatives for both Windows and Linux/macOS users.
- Consider presenting cross-platform Azure CLI examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
- Where possible, use Azure CLI as the default for scripting, as it is cross-platform, and relegate PowerShell to a separate tab or section.
- Explicitly mention that the PowerShell script is for Windows users and provide guidance for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/report-usage-across-multiple-labs-subscriptions.md
...abs/report-usage-across-multiple-labs-subscriptions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by primarily referencing PowerShell and Windows-centric tools (such as PowerShell Az.Resource module and SQL Server), providing no explicit Linux/bash/CLI examples, and mentioning Windows tools and patterns before any cross-platform or Linux alternatives. There is a lack of parity in scripting and tooling guidance for Linux users.
Recommendations
- Add equivalent Azure CLI (az) examples for exporting DevTest Labs usage, alongside or before PowerShell examples.
- Include bash script samples for automation scenarios, especially for exporting and processing usage data.
- Mention cross-platform storage and visualization tools (e.g., PostgreSQL, Grafana, or open-source alternatives) alongside SQL Server and Power BI.
- Explicitly state that Azure Functions and Azure Automation support multiple languages (including Python and bash), and provide sample code in at least one non-Windows language.
- Balance the order of tool and example presentation so that Linux-friendly and cross-platform options are not always listed after Windows-centric ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/syntax.md
...n//articles/azure-resource-manager/templates/syntax.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools and workflows before or instead of their Linux equivalents. Visual Studio Code and Visual Studio are mentioned as editors, with no explicit mention of Linux alternatives. The only extension referenced is the Azure Resource Manager Tools for VS Code, which is cross-platform but is presented in a way that assumes familiarity with Windows/VS Code workflows. In the 'identity' property, the only example link is for configuring managed identities on a Windows VM. There are no CLI or shell examples, and no explicit Linux or cross-platform editor guidance. In the multi-line strings section, Azure PowerShell is mentioned before Azure CLI, and there is no mention of Bash or Linux-specific considerations.
Recommendations
- Include explicit references to Linux and macOS environments when discussing editors and tools (e.g., mention that VS Code is available on Linux and macOS, or suggest other editors like Vim, Emacs, or JetBrains IDEs).
- When referencing deployment guides or quickstarts, provide both Windows and Linux examples or links (e.g., for configuring managed identities, link to both Windows and Linux VM guides).
- In sections discussing deployment via CLI or PowerShell, present Azure CLI (which is cross-platform) examples first, or at least in parallel with PowerShell, and clarify that CLI commands work on Linux/macOS/Windows.
- Add notes or examples for common Linux shell environments (e.g., Bash) where relevant, especially when discussing file formats, comments, or multi-line strings.
- Review all tool and workflow mentions to ensure Linux parity, and avoid assuming a Windows-first development environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/network-isolation.md
.../blob/main//articles/devtest-labs/network-isolation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing a PowerShell script (Convert-DtlLabToIsolatedNetwork.ps1) as the only provided automation method for converting an existing lab to isolated network mode. There are no equivalent Bash, Azure CLI, or Linux-oriented automation examples. The mention of automation later in the document lists PowerShell before Azure CLI, and does not provide any concrete Linux/Bash/CLI examples. No Linux-specific tools or workflows are discussed.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for converting an existing lab to isolated network mode, and link to them alongside the PowerShell script.
- When mentioning automation, present Azure CLI and PowerShell options together, or list Azure CLI first to avoid Windows-first ordering.
- Include explicit Linux/Bash command examples for relevant tasks, such as configuring service endpoints or automating network isolation.
- Clarify that all steps can be performed from any OS via the Azure Portal or Azure CLI, not just from Windows/PowerShell environments.
- If possible, provide sample code snippets or links for Linux users to achieve the same outcomes as the PowerShell script.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/import-virtual-machines-from-another-lab.md
...vtest-labs/import-virtual-machines-from-another-lab.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for PowerShell, with no equivalent examples or guidance for Linux users (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting method, and there is no mention of Linux-native tools or cross-platform alternatives. The REST API section is platform-neutral, but the scripting guidance is Windows-centric.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for Linux/macOS users.
- Provide Bash shell script examples for importing VMs, or at least mention how Linux users can interact with the REST API using curl or similar tools.
- Explicitly state that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, and provide installation guidance.
- Reorder or parallelize the scripting sections so that Windows and Linux approaches are presented side-by-side or with equal prominence.
- Include a note acknowledging cross-platform usage and direct users to relevant resources for their operating system.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/deployment-models.md
...azure-resource-manager/management/deployment-models.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 in several ways: PowerShell is the only command-line example shown, with no Azure CLI or Bash equivalents. The narrative and examples focus on Windows-centric tools and patterns (e.g., remote desktop, remote PowerShell), and Windows-based VM scenarios are mentioned before Linux-based ones. References to Linux (such as SSH for Linux VMs) are minimal and secondary. Migration and deployment guidance links prioritize PowerShell over CLI, and the 'Next steps' section points to PowerShell-specific instructions.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell commands for all resource management tasks.
- Mention Linux-based VM scenarios and SSH access patterns equally and before or alongside Windows/PowerShell examples.
- Ensure migration and deployment guidance includes both PowerShell and CLI/Bash options, with parallel documentation links.
- Balance references to Windows and Linux tools (e.g., remote desktop vs. SSH) when discussing VM connectivity.
- In tables and diagrams, use neutral or mixed examples (not just 'Run a Windows VM on Azure') and highlight both Windows and Linux VM architectures.
- Update 'Next steps' to include links for both PowerShell and CLI/Bash deployment guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/management/manage-private-link-access-commands.md
...ager/management/manage-private-link-access-commands.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, with PowerShell being a Windows-centric tool. PowerShell examples are given equal prominence to Azure CLI, and there is no mention of Linux-specific shell usage or considerations. The introductory comments for both CLI and PowerShell reference login commands (az login and Connect-AzAccount), but there is no explicit guidance for Linux users or mention of shell environments (e.g., Bash). The REST API examples are platform-neutral, but the overall pattern leans toward Windows tooling.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
- Add example shell commands using Bash (e.g., with environment variables, jq for JSON parsing) to demonstrate Linux-native usage.
- Explicitly mention that PowerShell Core is available on Linux and macOS, or clarify if the examples are intended for Windows PowerShell.
- Consider listing Azure CLI examples before PowerShell, as CLI is more commonly used in Linux environments.
- Add a note or section about using these commands in Linux environments, including any prerequisites or differences.
- Where relevant, provide troubleshooting or environment setup tips for Linux users.