A shared access signature (SAS) provides you with a way to grant limited access to objects in your storage account to other clients, without exposing your account key. Read more.
This application demonstrate following functionalities:
- usage of Azure functions,
- dependency injection with Autofac (inspired by Holger Leichsenring Blog Post),
- logging with Serilog sink to Azure Table storage,
- Visual Studio 2017 15.5.5 or greater
- Azure Storage Emulator (the Storage Emulator is available as part of the Microsoft Azure SDK)
To create and deploy functions, you also need:
- An active Azure subscription. If you don't have an Azure subscription, [free accounts]https://azure.microsoft.com/en-us/free) are available.
- An Azure Storage account. To create a storage account, see Create a storage account.
First, you have to enter your Azure storage account connection string into local.settings.json:
{
"IsEncrypted": false,
"Values": {
"Logging.Storage.TableName": "LogAzureFunctions",
"StorageAccount.ConnectionString": "UseDevelopmentStorage=true"
}
}P.S. More about how to test Azure functions locally you can read here.
Second, if you use development storage you have to setup Azure Storage Emulator. See Use the Azure storage emulator for development and testing and Configuring and Using the Storage Emulator with Visual Studio.
Third, build solution and run it with local Azure Functions runtime:
Finally test it with Postman:
Enjoy!