Skip to content

Conversation

@navba-MSFT
Copy link
Contributor

@navba-MSFT navba-MSFT commented May 6, 2022

The below information needs to be added to avoid the customer's using -UseConnectedAccount (AAD Credential) to create account SAS which would fail.

"An account SAS is secured using the storage account key. To create an account SAS, a client application must possess the account key."

Fixes #17008

Description

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

The below information needs to be added to avoid the customer's using -UseConnectedAccount (AAD Credential) to create account SAS which would fail.

"An account SAS is secured using the storage account key. To create an account SAS, a client application must possess the account key."
@wyunchi-ms
Copy link
Contributor

/azp run azure-powershell - security-tools

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New-AzStorageAccountSASToken doesn't work with -UseConnectedAccount

2 participants