Document Details
Linter Rule Admin Username Should Not Be Literal
❌
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.
Bias Analysis
Bias Types:
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation page exclusively uses examples and terminology relevant to Windows environments (e.g., 'administrator', 'adminUsername'), and references Azure VM resource types that default to Windows conventions. There are no examples or mentions of Linux admin usernames (such as 'azureuser' or 'root'), nor any Linux-specific guidance, which may lead users to assume the rule or guidance is only relevant for Windows VMs.
Recommendations:
- Include examples that use Linux-typical admin usernames (e.g., 'azureuser', 'root') to demonstrate the rule's applicability to Linux VMs.
- Explicitly mention that the linter rule applies to both Windows and Linux virtual machines.
- Add a section or note clarifying any differences in admin username conventions between Windows and Linux VM deployments.
- Provide at least one example resource definition for a Linux VM, showing the adminUsername parameterization.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
Flagged Code Snippets
param location string = resourceGroup().location
var defaultAdmin = 'administrator'
resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
name: 'name'
location: location
properties: {
osProfile: {
adminUsername: defaultAdmin
}
}
}