Deployment Environments

73
Total Pages
67
Linux-Friendly Pages
6
Pages with Bias
8.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

12 issues found
Showing 1-12 of 12 flagged pages
Deployment Environments Grant access to Azure Deployment Environments ...nments/how-to-manage-deployment-environments-access.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions and screenshots for using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or guidance for performing role assignments using cross-platform tools such as Azure CLI, Azure PowerShell, or REST APIs, which would be relevant for Linux and macOS users. The lack of command-line or automation-friendly instructions creates friction for non-Windows users and those working in headless or automated environments.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI (az role assignment), which works on Linux, macOS, and Windows.
  • Include Azure PowerShell examples, noting that PowerShell Core is cross-platform.
  • Provide REST API examples for role assignment for automation and platform neutrality.
  • Explicitly state that the Azure portal is web-based and can be accessed from any OS, but highlight CLI and API alternatives for users who prefer or require non-GUI workflows.
GitHub Create Pull Request
Deployment Environments Create an environment with Azure Developer CLI ...-configure-azure-developer-cli-deployment-environments.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the installation instructions for the Azure Developer CLI, where only a PowerShell-based installation command is provided and no Linux/macOS equivalent is mentioned. The installation section does not offer parity for Bash or other Unix shells, and the Windows/PowerShell example is presented first and exclusively. While the rest of the CLI usage is cross-platform, the initial setup creates friction for non-Windows users.
Recommendations
  • Add explicit installation instructions for Linux and macOS, including Bash/cURL commands and package manager options (e.g., apt, brew).
  • Present installation instructions for all platforms side-by-side or in tabs, rather than only showing PowerShell.
  • Clarify that azd is cross-platform and provide links to official installation docs for each OS.
  • Ensure screenshots and examples are not exclusively Windows/PowerShell unless necessary.
GitHub Create Pull Request
Deployment Environments Configure a managed identity for Azure Deployment Environments ...ment-environments/how-to-configure-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (a web-based GUI) for all configuration steps and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). While the portal is cross-platform, the lack of CLI instructions can disadvantage Linux/macOS users, who often prefer or require automation and non-GUI workflows. There is also no mention of Linux-specific tools or patterns, and no parity for users who may not use the portal.
Recommendations
  • Add equivalent Azure CLI commands for all major configuration steps (e.g., creating and assigning managed identities, role assignments, key vault permissions).
  • Explicitly mention that all steps can be performed via CLI or automation, and link to relevant CLI documentation.
  • Provide example scripts for Linux/macOS environments alongside portal instructions.
  • Clarify that the Azure portal is accessible from any OS, but highlight CLI alternatives for users who prefer non-GUI workflows.
GitHub Create Pull Request
Deployment Environments ADE extensibility model for custom container images ...s/how-to-configure-extensibility-model-custom-image.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its scripting and example sections, especially for Bicep and Terraform workflows. All quickstart and automation scripts are provided as PowerShell (.ps1) files, with example invocations shown only in PowerShell syntax. There are no equivalent Bash or shell script examples for Linux/macOS users, nor are alternative instructions or scripts provided for those platforms. The prerequisites and instructions repeatedly mention Docker Desktop (primarily a Windows/macOS tool) and Azure CLI, but fail to clarify cross-platform usage or offer parity for Linux-native tools and workflows. This bias creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/shell scripting.
Recommendations
  • Provide equivalent Bash/shell scripts for all PowerShell (.ps1) quickstart scripts, or clarify cross-platform compatibility.
  • Include example commands for Linux/macOS users, using Bash syntax and native tools.
  • Explicitly mention that Docker Desktop is not required on Linux, where Docker Engine is typically used.
  • Reorder examples so that Linux/macOS instructions are presented alongside or before Windows/PowerShell instructions.
  • Add notes or tabs for platform-specific instructions, ensuring Linux/macOS users can follow all steps without needing PowerShell.
GitHub Create Pull Request
Deployment Environments Grant access to Azure Deployment Environments ...nments/how-to-manage-deployment-environments-access.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and management using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, Azure PowerShell, or REST API, which would be accessible from Linux or macOS. All screenshots and step-by-step instructions assume use of the portal, and there is no mention of command-line alternatives.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Provide Azure PowerShell examples, noting that PowerShell Core is available on Linux/macOS.
  • Include REST API examples for advanced users who may prefer automation or scripting.
  • Explicitly state that the Azure portal is web-based and can be accessed from any OS, but highlight CLI and API options for those who prefer or require non-GUI workflows.
GitHub Create Pull Request
Deployment Environments Create a Dev Center and Project for Deployment Environments by Using an ARM Template ...start-create-dev-center-project-azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for template deployment, instructing users to select the PowerShell shell in Cloud Shell, and omitting equivalent Azure CLI/bash examples. This prioritizes Windows-centric tooling and patterns, potentially creating friction for Linux/macOS users who typically use Azure CLI or bash.
Recommendations
  • Add Azure CLI/bash examples for deploying the ARM template, with clear instructions for use in Cloud Shell or local terminals.
  • Present both PowerShell and CLI examples side-by-side, or allow users to select their preferred shell before showing code.
  • Explicitly mention that Cloud Shell supports both PowerShell and Bash, and provide guidance for both environments.
  • Ensure that references to deployment methods (portal, CLI, PowerShell) are equally detailed and accessible.
GitHub Create Pull Request
Deployment Environments Create an environment with Azure Developer CLI ...-configure-azure-developer-cli-deployment-environments.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the installation instructions for the Azure Developer CLI. The only explicit command-line installation example uses PowerShell, with no Bash or Linux/macOS equivalent provided. The use of Visual Studio and Visual Studio Code is platform-neutral, but the CLI installation and setup instructions are Windows-centric. Linux/macOS users are left to infer their installation steps, which may create friction.
Recommendations
  • Add explicit Bash installation instructions for Linux/macOS users, such as using curl or wget to install azd.
  • Include a note or tab for macOS/Linux users in the installation section, mirroring the PowerShell example with a Bash equivalent.
  • Clarify that azd is cross-platform and provide links or steps for installing on all supported operating systems.
  • Ensure all CLI examples are shown in both PowerShell and Bash where relevant, or use generic commands where possible.
GitHub Create Pull Request
Deployment Environments Grant access to Azure Deployment Environments ...nments/how-to-manage-deployment-environments-access.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions and screenshots for role assignment using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or guidance for performing these tasks via command-line tools (such as Azure CLI or PowerShell), nor are Linux/macOS-specific workflows or tools mentioned. This creates friction for users who prefer or require non-GUI, cross-platform automation.
Recommendations
  • Add step-by-step instructions for assigning roles using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include examples for PowerShell and Bash where relevant, showing equivalent commands for role assignment and verification.
  • Mention that the Azure portal is accessible from any modern browser on Linux/macOS, but clarify that automation and scripting can be done via CLI tools.
  • Provide links to official docs for CLI and PowerShell role assignment methods.
GitHub Create Pull Request
Deployment Environments ADE extensibility model for custom container images ...s/how-to-configure-extensibility-model-custom-image.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas. Script-based image creation instructions for both Bicep and Terraform exclusively provide PowerShell (.ps1) examples and commands, with no Bash or Linux/macOS equivalents. The prerequisites and instructions repeatedly mention Docker Desktop (a Windows-centric tool) and Azure CLI, but do not clarify Linux alternatives or usage. There is no mention of how to run the provided scripts on Linux/macOS, nor are cross-platform script variants or guidance provided. This creates friction for Linux/macOS users attempting to follow the quickstart or automation steps.
Recommendations
  • Provide Bash (.sh) script equivalents for all PowerShell (.ps1) scripts, with usage instructions for Linux/macOS.
  • Include explicit Linux/macOS command-line examples alongside Windows/PowerShell examples.
  • Clarify Docker Desktop requirements and provide guidance for Docker Engine on Linux.
  • Reorder examples so that cross-platform or Linux-native instructions are presented first or equally.
  • Add notes or tabs indicating platform-specific steps, and link to platform-appropriate tooling documentation.
GitHub Create Pull Request
Deployment Environments Configure a managed identity for Azure Deployment Environments ...ment-environments/how-to-configure-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (web UI) instructions and screenshots, which are platform-agnostic, but it omits any command-line examples (such as Azure CLI, PowerShell, or Bash). This creates a subtle Windows bias because Azure documentation often defaults to PowerShell or Windows-centric tools when command-line instructions are provided, and the absence of CLI examples means Linux/macOS users who prefer or require automation are underserved. There are no explicit references to Windows-only tools, but the lack of CLI parity is a notable gap.
Recommendations
  • Add Azure CLI command examples for all major steps (creating managed identities, assigning roles, configuring key vault access) alongside portal instructions.
  • Explicitly mention that all steps can be performed via CLI or automation, and link to relevant Azure CLI documentation.
  • If PowerShell examples are added in future, ensure Bash/Azure CLI equivalents are provided and shown with equal prominence.
  • Include notes or sections for scripting/automation for cross-platform users.
GitHub Create Pull Request
Deployment Environments Create a Dev Center and Project for Deployment Environments by Using an ARM Template ...start-create-dev-center-project-azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for template deployment, instructing users to select the PowerShell shell in Cloud Shell, and omitting equivalent Azure CLI/bash examples. This prioritizes Windows tooling and workflow, creating friction for Linux/macOS users who typically use Azure CLI or bash.
Recommendations
  • Add Azure CLI/bash examples for deploying the ARM template, ideally side-by-side with PowerShell.
  • Update instructions to mention both PowerShell and Bash shells in Cloud Shell, allowing users to choose their preferred environment.
  • Ensure that references to deployment methods (portal, CLI, PowerShell) are presented with equal prominence and clear links to relevant documentation for each.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid implicit prioritization.
GitHub Create Pull Request
Deployment Environments Tutorial: Deploy environments in CI/CD by using GitHub ...onments/tutorial-deploy-environments-in-cicd-github.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples exclusively using Azure CLI and Bash-style environment variable syntax, which is cross-platform but shown in a way most familiar to Linux/macOS users. However, in the 'Test the CI/CD pipeline' section, the instructions for cloning and working with the repository reference 'Git Bash' and Visual Studio Code, which are available on Windows, macOS, and Linux, but the explicit mention of 'Git Bash' may imply a Windows-first approach. There are no PowerShell or Windows Command Prompt examples, nor are there explicit Linux/macOS instructions or troubleshooting notes. The documentation does not mention platform-specific differences, nor does it provide parity for users who may be using Windows-native shells (e.g., PowerShell, Command Prompt), which could create friction for those users. Conversely, Linux users are not disadvantaged, but Windows users may need to adapt Bash syntax to PowerShell or Command Prompt.
Recommendations
  • Add explicit notes or examples for running Azure CLI commands in PowerShell and Windows Command Prompt, including syntax differences for environment variables (e.g., $env:VAR in PowerShell, set VAR= in CMD).
  • Clarify that Bash syntax is shown and provide equivalent commands for Windows shells where appropriate.
  • Include troubleshooting tips for common cross-platform issues (e.g., path separators, quoting, environment variable usage).
  • Mention that Visual Studio Code and Git Bash are available on all major platforms, and suggest alternatives for Linux/macOS users (e.g., native terminal, other editors).
GitHub Create Pull Request