Document Details

Deploy Service Catalog Quickstart
Home / Scan #41 / Deploy Service Catalog Quickstart
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

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...'.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean

Flagged Code Snippets

Connect-AzAccount

Get-AzManagedApplicationDefinition -ResourceGroupName appDefinitionGroup

New-AzResourceGroup -Name applicationGroup -Location westus

Get-AzManagedApplication -Name demoManagedApplication -ResourceGroupName applicationGroup

Get-AzDenyAssignment -ResourceGroupName $mrgname

$definitionid = (Get-AzManagedApplicationDefinition -ResourceGroupName appDefinitionGroup -Name sampleManagedApplication).ManagedApplicationDefinitionId

$mrgprefix = 'mrg-sampleManagedApplication-'
$mrgtimestamp = Get-Date -UFormat "%Y%m%d%H%M%S"
$mrgname = $mrgprefix + $mrgtimestamp
$mrgname

"{ `"parameterName`": {`"value`":`"parameterValue`"}, `"parameterName`": {`"value`":`"parameterValue`"} }"

$params="{ `"appServicePlanName`": {`"value`":`"demoAppServicePlan`"}, `
`"appServiceNamePrefix`": {`"value`":`"demoApp`"} }"

Get-AzRoleAssignment -ResourceGroupName $mrgname -RoleDefinitionName Owner

New-AzManagedApplication `
  -Name "demoManagedApplication" `
  -ResourceGroupName applicationGroup `
  -Location westus `
  -ManagedResourceGroupName $mrgname `
  -ManagedApplicationDefinitionId $definitionid `
  -Kind ServiceCatalog `
  -Parameter $params

Get-AzManagedApplication -Name demoManagedApplication -ResourceGroupName applicationGroup | Select-Object -ExpandProperty Properties

Get-AzResource -ResourceGroupName $mrgname

Get-AzRoleAssignment -ResourceGroupName $mrgname

Remove-AzResourceGroup -Name applicationGroup