Document Details

Communicate Between Microservices
Home / Scan #41 / Communicate Between Microservices
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
Summary
The documentation provides both Bash and PowerShell examples for most commands, but in several key sections, the PowerShell workflow is more detailed and prominent. For example, the deployment of the frontend application is described in a much more elaborate way for PowerShell users, including the use of template objects and multiple steps, whereas the Bash workflow is a single command. Additionally, in some sections, PowerShell appears before Bash, and the PowerShell workflow uses Azure PowerShell cmdlets (e.g., New-AzContainerApp) rather than Azure CLI, which is more cross-platform. There are no missing Linux examples, but the PowerShell workflow is more verbose and detailed, potentially giving the impression of Windows preference.
Recommendations
  • Ensure that both Bash and PowerShell workflows are equally detailed. For example, provide a step-by-step Bash alternative for the multi-step PowerShell deployment process, possibly using Azure CLI and environment variables.
  • Where possible, use Azure CLI for both Bash and PowerShell examples to maintain cross-platform parity, as Azure CLI works identically on Windows, Linux, and macOS.
  • Present Bash examples first, as Bash is the default shell on Linux and macOS, and is also available on Windows via WSL or Git Bash.
  • If using PowerShell-specific cmdlets (e.g., New-AzContainerApp), provide equivalent Azure CLI commands for Bash users.
  • Review the order and depth of examples to ensure Linux users are not disadvantaged or required to 'figure out' missing steps.
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

$RegistryCredentials = Get-AzContainerRegistryCredential -Name $ACRName -ResourceGroupName $ResourceGroup

$APIBaseURL = (Get-AzContainerApp -Name $APIName -ResourceGroupName $ResourceGroup).IngressFqdn

$EnvVars = New-AzContainerAppEnvironmentVarObject -Name API_BASE_URL -Value https://$APIBaseURL

$ContainerArgs = @{
  Name = $FrontendName
  Image = $ACRName + '.azurecr.io/albumapp-ui'
  Env = $EnvVars
}
$ContainerObj = New-AzContainerAppTemplateObject @ContainerArgs

$RegistryArgs = @{
    Server = $ACRName + '.azurecr.io'
    PasswordSecretRef = 'registrysecret'
    Username = $RegistryCredentials.Username
}
$RegistryObj = New-AzContainerAppRegistryCredentialObject @RegistryArgs

$SecretObj = New-AzContainerAppSecretObject -Name 'registrysecret' -Value $RegistryCredentials.Password

$EnvId = (Get-AzContainerAppManagedEnv -EnvName $Environment -ResourceGroup $ResourceGroup).Id

$AppArgs = @{
    Name = $FrontendName
    Location = $Location
    ResourceGroupName = $ResourceGroup
    ManagedEnvironmentId = $EnvId
    TemplateContainer = $ContainerObj
    ConfigurationRegistry = $RegistryObj
    ConfigurationSecret = $SecretObj
    IngressTargetPort = 3000
    IngressExternal = $true
}
$FrontEndApp = New-AzContainerApp @AppArgs

# show the app's FQDN

$FrontEndApp.IngressFqdn