![]() To make changes, select Back, and then enter the settings you want.Īfter the storage account has successfully been attached, the storage account is displayed with (SAS) appended to its name. In the Connection Summary dialog box, verify the information. Paste your connection string into the Connection string: field. In Storage Explorer, open the Connect Dialog.Ĭhoose Use a connection string. Īttach to a storage account by using a SAS Connection String Next to the Connection String text box, select Copy to copy it to your clipboard, and then click Close. In the Generate Shared Access Signature dialog box, specify the time frame and permissions that you want for the account, and then click the Create button. In Storage Explorer, right-click the storage account you want share, and then select Get Shared Access Signature…. Generate a SAS query string for the account you want to share UserB uses Storage Explorer to attach to the account that belongs to UserA by using the supplied SAS.UserA shares the SAS with the person (UserB, in this example) who wants access to the storage account.UserA generates a SAS connection string for a specific time period and with the desired permissions.To illustrate this scenario, let’s say that UserA is an admin of an Azure subscription, and UserA wants to allow UserB to access a storage account for a limited time with certain permissions: ![]() You can then find the storage account node for your emulator under Local & Attached > Storage Accounts.A Shared Access Signature, or SAS, lets the admin of an Azure subscription grant temporary access to a storage account without having to provide Azure subscription credentials. Then select the Connection string option, proceed to the next page, and use your connection string to complete the connection process. Once you have a connection string, open the Connect dialog (plug icon in the left side) and choose Storage account or service. The connection string will likely need to explicitly define the endpoint for each service type. If you need to manually connect to an emulator running on a different machine, then you will need to construct a connection string that details how to connect to your emulator. For best results, configure your emulator to use the default development account name and key, and then use a name and key connection string to connect. Certain remote emulator configurations may make it difficult for Storage Explorer to understand that an emulator is being connected to, which may affect some features. Remote emulatorĪlthough Storage Explorer supports connnecting to a remote emulator, it is not reccomended. After you finish connecting, you can find the storage account node for your emulator under Local & Attached > Storage Accounts. If your emulator is configured to use HTTPS, also make sure to check the checkbox for HTTPS. Make sure to set the ports for each service type to their appropriate values. If you need to manually connect to an emulator that is running locally, open the Connect dialog (plug icon in the left side) and choose Local storage emulator. Manually connect to an emulator Local emulator If any of the above aren't true, then you'll need to manually add a connection to your emulator. Then you can quickly access your emulator resources by navigating in the resource tree view to Local & Attached > Storage Accounts > Emulator (Default Ports). Configured to listen on the typical default ports of:.If you attempt to access an emulator container, queue, or table, before starting your emulator you'll receive an error message.Īssuming you have started your emulator and it is: If you attempt to access an emulator storage account before starting your emulator, you'll receive a message reminding you to start your emulator. Storage Explorer doesn't start your emulator for you. How to connect to an emulatorīefore you can connect Storage Explorer to an emulator, you must first start the emulator. You'll need to download an emulator on your own. Also note that Storage Explorer doesn't ship with an emulator. However, any emulator that functions similarly to Azurite will also likely work with Storage Explorer. Azurite is a cross platform, open-source emulator made by Microsoft. Storage Explorer officially supports and recommends using Azurite. And once you're satisfied with how your application is working locally, you can switch to using a real Azure Storage account in the cloud. Emulators provide a free local environment for testing your code and applications. ![]() Storage Explorer can be connected to an Azure Storage emulator to aid in development.
0 Comments
Leave a Reply. |