Share via

Connecting to Azure Storage Account from SSMS

mij2020 366 Reputation points
2022-03-16T16:42:58.187+00:00

Hi,
According to MS Docs I should be able to connect to my Azure SA using the primary or secondary access key from SSMS.
However the only option I have is to connect to the SA by using my AAD credentials by signing in. The option to use access keys is not there.
To clarify - within SSMS I click: Connect -> Azure Storage and at this point I was expecting to be able to use access key, or to have the ability to switch between access key and Sign-In option.
Can someone confirm that the access key authentication to Azure SA has been deprecated with SSMS v18.11.1 or am I looking in the wrong place?

Azure SQL Database
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,944 questions
0 comments
Accepted answer
  1. Alberto Morillo 33,426 Reputation points MVP
    2022-03-16T20:44:28.497+00:00

    Here you will find a tutorial on how to use SSMS to connect to an Azure Storage Account. I am able to connect successfully to an Storage Account using SSMS, and I just needed to sign in to my Microsoft Account. No need to provide account key. You cannot provide storage account key any longer.

    183828-image.png

    183829-image.png

    183850-image.png

    However, to connect to an Azure Storage account with a key I will recommend you to use Azure Storage Explorer. Download the tool from here. Here is a tutorial on how to get started with Azure Data Explorer.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. mij2020 366 Reputation points
    2022-03-17T08:27:32.26+00:00

    Thank you for your answer. The link provided also describes how to use access keys to authenticate to the SA from SSMS.
    The sign in to Azure does work for me - I just couldnt find any documentation to say that access keys were no longer allowed. and any MS docs article I found haven't been updated to reflect this.