Mounting Azure Storage Account on the Azure Perform

Azure Perform

Azure Features is a serverless computing answer that allows you to write much less code, handle fewer infrastructures, and cut back prices. Relatively than coping with the deployment and upkeep of servers, the cloud infrastructure offers all vital up-to-date sources to maintain purposes operational. It helps a number of languages, together with C#, Python, Java, JavaScript, and PowerShell.

When creating an Azure Perform, it should be related to storage accounts, which permits it to make the most of storage recordsdata throughout the code. For safety functions, it’s advisable to rotate the entry key of the Azure storage accounts each six months. The perform app is linked to the storage account utilizing the entry key by way of backend CLI instructions.

To get an inventory of storage accounts

az webapp config storage-account checklist --name [MyWebApp] --resource-group [MyResourceGroup]

State. It should inform you whether or not the connection is profitable and if the credentials are right.

To replace the access key from the Backend.

az webapp config storage-account replace --custom-id
                                        [--access-key]
                                        [--account-name]
                                        [--ids]
                                        [--mount-path]
                                        [--name]
                                        [--resource-group]
                                        [--share-name]
                                        [--slot]
                                        [--slot-setting]
                                        [--storage-type {AzureBlob, AzureFiles}]
                                        [--subscription]

Examples

Replace the entry key for a connection to the Azure blob.

Azure CLI

az webapp config storage-account replace -g [ResourceGroup Name] -n [FunctionApp name] --custom-id [Name shown in storage account list] --access-key [AccessKey]

Required Parameters

–custom-id -i: Identify of the share configured throughout the net ap

Elective Parameters

• –access-key -k: Storage account entry key.
• –account-name -a: Storage account identify.
• –ids: A number of useful resource IDs (space-delimited). It needs to be a whole useful resource ID containing all data of ‘Useful resource Id’ arguments. You must present both –ids or different ‘Useful resource Id’ arguments.
• –mount-path -m: The trail which the net app makes use of to read-write knowledge ex: /share1 or /share2.
• –name -n: Identify of the net app. If left unspecified, a reputation shall be randomly generated. You may configure the default utilizing az configure –defaults net=<identify>.
• –resource-group -g: Identify of useful resource group. You may configure the default group utilizing az configure –defaults group=<identify>.
• –share-name –sn: Identify of the file share as given within the storage account.
• –slot -s: The identify of the slot. Default to the manufacturing slot if not specified.
• –slot-setting: With slot setting you possibly can resolve to make BYOS configuration sticky to a slot, that means that when that slot is swapped, the storage account stays with that slot. Default worth: False
• –storage-type -t: Storage kind.
  • Accepted values: AzureBlob, AzureFiles (It is advisable to mount Azure Perform on Azure File Share)
• –subscription: Identify or ID of subscription. You may configure the default subscription utilizing az account set -s NAME_OR_ID.