Closed ngelotte closed 2 years ago
@ngelotte
Please use the latest Az.Storage module. The module you use is too old, and it depends on a old .net SDK which not work with some new storage account kind like FileStorage.
Please update to latest Az.Storage module and try again. See the migration guild here.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.
Author: | ngelotte |
---|---|
Assignees: | blueww |
Labels: | `Storage`, `Service Attention`, `question`, `customer-reported`, `AzureRM 6.x`, `needs-author-feedback` |
Milestone: | - |
I got the problem resolved by moving to Az.Storage.
The real problem was that we are using a custom build agent for Azure dev ops and the AZCopy step in Devops checks to see if the new modules are installed and then falls back to the RM modules if they are not. So we just needed to install the new modules and AZ copy uses them.
@ngelotte Thanks for the update! I will close this issue. Feel free to contact us again if need any further assistance on Powershell.
Description
After added a new Storage account with the type of FileStorage in our azure subscription the command Get-AzureRmStorageAccount is now failing. It is used by the AzureFileCopyV4 in Azure Devops so I cannot switch to a different command. I found a the same issue a few years back but it was supposed to be resolved but this is with the latest version of the AzureRM module and it is still happening.
Issue script & Debug output
Environment data
Module versions
Error output