Azure-docs: Step 5 isnt working - A parameter cannot be found that matches parameter name 'UseConnectedAccount'

[mganeshphani]

New-AzureStorageContext : A parameter cannot be found that matches parameter name 'UseConnectedAccount'.
At line:1 char:73

• ... Context -StorageAccountName jbhcreatekeyvaultase -UseConnectedAccount
• ~~~~
  
  
  
  • CategoryInfo : InvalidArgument: (:) [New-AzureStorageContext], ParameterBindingException
  
  
  • FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.WindowsAzure.Commands.Storage.Common.Cmdlet.NewAzureSto
    
    rageContext
  
  

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 18dcb813-6d62-ea30-4a33-1e350c9380cd
• Version Independent ID: 9a7e40de-b31d-96e7-c272-99d51b822af8
• Content: Run Azure CLI or PowerShell commands under an Azure AD identity to access Azure Storage (Preview)
• Content Source: articles/storage/common/storage-auth-aad-script.md
• Service: storage
• GitHub Login: @tamram
• Microsoft Alias: tamram

[mganeshphani]

Followed exact same steps as mentioned in the document.. this wasted my 30 min of time..

[AdamS-MSFT]

@mganeshphani I apologize for the experience, I've already reported this issue to the product team, The Oauth support is in Powershell “Azure.Storage” preview module with version “4.4.0-preview” or “4.4.1-preview".
But since the latest official release “Azure.Storage” has version 4.5.0 (doesn’t have Oauth support), the support for it will be pushed by the end of September. I'll keep this case open and will communicate when the product team rolls out the fix.

[mganeshphani]

@Adam-Smith-MSFT

Thankyou for taking a look.

I wish product teams will be very careful and test the scenarios well before releasing the documentation to public.. I guess Agile doesn't mean release(I do know this is preview, but I do at least expect the behavior as mentioned in the official doc) broken stuff to end users and waste time, (please pass on the feedback to relevant teams if you can) :)

[tamram]

@mganeshphani - Thanks for your feedback. I've fixed this, and the change should go live early next week.

please-close

[SaurabhSharma-MSFT]

@mganeshphani We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[asvyat]

How to get fixed PS version? I am still getting similar issue on both of my machines :-(