Microsoft Azure PowerShell 0.8.8 is available
Just a few hours ago, Azure team released Microsoft Azure PowerShell 0.8.8. The new release has a lot of improvements and added a support for today’s Azure update–Role-Based Access Control in Azure Preview Portal.
Here is the official change log for version 0.8.8:
Role-based access control support
Query role definition
Get-AzureRoleDefinition
Manage role assignment
New-AzureRoleAssignment
Get-AzureRoleAssignment
Remove-AzureRoleAssignment
Query Active Directory object
Get-AzureADUser
Get-AzureADGroup
Get-AzureADGroupMember
Get-AzureADServicePrincipal
Show user’s permissions on
Get-AzureResourceGroup
Get-AzureResource
Active Directory service principal login support in Azure Resource Manager mode
Add-AzureAccount -Credential -ServicePrincipal -Tenant
SQL Database auditing support in Azure Resource Manager mode
Use-AzureSqlServerAuditingSetting
Set-AzureSqlServerAuditingSetting
Set-AzureSqlDatabaseAuditingSetting
Get-AzureSqlServerAuditingSetting
Get-AzureSqlDatabaseAuditingSetting
Disable-AzureSqlServerAuditing
Disable-AzureSqlDatabaseAuditing
Other improvements
Virtual Machine DSC extension supports PSCredential as configuration argument
Virtual Machine Antimalware extension supports native JSON configuration
Storage supports creating storage account with different geo-redundant options
Traffic Manager supports nesting of profiles
Website supports configuring x32/x64 worker process
-Detail parameter on Get-AzureResourceGroup to improve performance
Major refactoring around account and subscription management
The error “Add-AzureAccount: multiple_matching_tokens_detected: The cache contains multiple tokens satisfying the requirements. Call AcquireToken again providing more requirements (e.g. UserId)” that some users have experienced with the Add-AzureAccount cmdlet, and were blocked to work with the Resource Manager in PowerShell, is fixed now.
The “Virtual Machine DSC extension supports PSCredential as configuration argument” improvement is covered in detail in today’s post on PowerShell team blog.
Share on: