Document Details
Credentials
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
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, primarily focusing on PowerShell cmdlets and workflows. All command-line examples are given in PowerShell, with no mention of Linux shell equivalents or cross-platform CLI tools. Windows-specific tools and patterns (e.g., PSCredential, PowerShell modules) are referenced exclusively and before Python alternatives. There are no bash, Azure CLI, or Linux-native examples for credential management, and the documentation does not address Linux automation scenarios.
Recommendations
- Add equivalent examples using Azure CLI (az) for credential management, which is cross-platform and works on Linux.
- Include bash or shell script examples for common credential operations, such as retrieving secrets from Azure Key Vault.
- Clarify which features and cmdlets are available or not available on Linux-based hybrid workers, and provide guidance for Linux users.
- Mention Python and other cross-platform SDKs earlier in the documentation, not only after extensive PowerShell coverage.
- Provide a comparison table of credential management approaches for Windows (PowerShell), Linux (bash/Azure CLI), and Python.
- Explicitly state any platform limitations or differences in credential asset usage between Windows and Linux environments.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-02-12 00:00 | #237 | in_progress |
 Clean
|
| 2026-02-11 00:00 | #233 | in_progress |
Clean
|
| 2026-02-10 00:00 | #229 | completed |
Biased
|
| 2026-01-25 00:00 | #165 | completed |
Biased
|
| 2026-01-24 00:00 | #161 | completed |
Biased
|
| 2026-01-23 00:00 | #157 | completed |
Biased
|
| 2026-01-13 06:17 | #107 | completed |
Biased
|
| 2026-01-12 00:00 | #99 | completed |
Biased
|
| 2026-01-11 06:20 | #98 | completed |
Biased
|
| 2026-01-11 00:00 | #95 | cancelled |
Clean
|
| 2026-01-10 00:00 | #92 | completed |
Clean
|
| 2026-01-09 00:00 | #87 | cancelled |
Clean
|
| 2026-01-06 22:28 | #78 | completed |
Clean
|
| 2025-12-29 18:00 | #48 | cancelled |
Biased
|
| 2025-12-15 00:00 | #7 | completed |
Clean
|
| 2025-12-14 05:05 | #6 | completed |
Clean
|
Flagged Code Snippets
Import-Module Orchestrator.AssetManagement.Cmdlets -ErrorAction SilentlyContinue
$user = "MyDomain\MyUser" $pw = ConvertTo-SecureString "PassWord!" -AsPlainText -Force $cred = New-Object –TypeName System.Management.Automation.PSCredential –ArgumentList $user, $pw New-AzureAutomationCredential -AutomationAccountName "MyAutomationAccount" -Name "MyCredential" -Value $cred
$myCredential = Get-AutomationPSCredential -Name 'MyCredential' $userName = $myCredential.UserName $securePassword = $myCredential.Password $password = $myCredential.GetNetworkCredential().Password
# Ensures you do not inherit an AzContext in your runbook
Disable-AzContextAutosave -Scope Process
# Connect to Azure with system-assigned managed identity
$AzureContext = (Connect-AzAccount -Identity).context
# set and store context
$AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext
# Get credential
$myCred = Get-AutomationPSCredential -Name "MyCredential"
$userName = $myCred.UserName
$securePassword = $myCred.Password
$password = $myCred.GetNetworkCredential().Password
$myPsCred = New-Object System.Management.Automation.PSCredential ($userName,$securePassword)
# Connect to Azure with credential
$AzureContext = (Connect-AzAccount -Credential $myPsCred -TenantId $AzureContext.Subscription.TenantId).context
# set and store context
$AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription `
-TenantId $AzureContext.Subscription.TenantId `
-DefaultProfile $AzureContext