The emulator supports connection via HTTP only. You should not use the development account with production data. You cannot use your production storage account and key with the emulator. The authentication key supported by the emulator is intended only for testing the functionality of your client authentication code. They are: Account name: devstoreaccount1Īccount key: Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw= This account and key are the only Shared Key credentials permitted for use with the emulator. The emulator supports a single fixed account and a well-known authentication key for Shared Key authentication. Configure a connection string for Azurite You can use the Microsoft Azure Configuration Manager to access your connection string at runtime regardless of where your application is running. You only need to edit the connection string to point to your target environment.
Storing your connection string in a configuration file makes it easy to update the connection string to switch between the Azurite storage emulator and an Azure storage account in the cloud. Add the connection string to the ConfigurationSettings section of the service configuration file.
Add the connection string to the AppSettings section in these files. An application running on the desktop or on a device can store the connection string in an app.config or web.config file.You can store your connection string in an environment variable.
You have several options for storing your connection string: Your application needs to access the connection string at runtime to authorize requests made to Azure Storage. Azure AD provides superior security and ease of use over Shared Key. Microsoft recommends using Azure Active Directory (Azure AD) to authorize requests against blob and queue data if possible, instead of Shared Key.