You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-encrypt-at-rest-using-cmk.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ ms.date: 03/06/2020
7
7
8
8
# Encryption at rest using customer-managed keys
9
9
10
-
Encrypting your web app's application data at rest requires an Azure Storage Account and an Azure Key Vault. These services are used when you run your app from a deployment package.
10
+
Encrypting your function app's application data at rest requires an Azure Storage Account and an Azure Key Vault. These services are used when you run your app from a deployment package.
11
11
12
-
-[Azure Storage provides encryption at rest](../storage/common/storage-service-encryption.md). You can use system-provided keys or your own, customer-managed keys. This is where your application data is stored when it's not running in a web app in Azure.
12
+
-[Azure Storage provides encryption at rest](../storage/common/storage-service-encryption.md). You can use system-provided keys or your own, customer-managed keys. This is where your application data is stored when it's not running in a function app in Azure.
13
13
-[Running from a deployment package](deploy-run-package.md) is a deployment feature of App Service. It allows you to deploy your site content from an Azure Storage Account using a Shared Access Signature (SAS) URL.
14
14
-[Key Vault references](app-service-key-vault-reference.md) are a security feature of App Service. It allows you to import secrets at runtime as application settings. Use this to encrypt the SAS URL of your Azure Storage Account.
15
15
@@ -32,7 +32,7 @@ Once you upload your file to Blob storage and have an SAS URL for the file, set
32
32
az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings WEBSITE_RUN_FROM_PACKAGE="<your-SAS-URL>"
33
33
```
34
34
35
-
Adding this application setting causes your web app to restart. After the app has restarted, browse to it and make sure that the app has started correctly using the deployment package. If the application didn't start correctly, see the [Run from package troubleshooting guide](deploy-run-package.md#troubleshooting).
35
+
Adding this application setting causes your function app to restart. After the app has restarted, browse to it and make sure that the app has started correctly using the deployment package. If the application didn't start correctly, see the [Run from package troubleshooting guide](deploy-run-package.md#troubleshooting).
36
36
37
37
### Encrypt the application setting using Key Vault references
38
38
@@ -60,11 +60,11 @@ Now you can replace the value of the `WEBSITE_RUN_FROM_PACKAGE` application sett
60
60
61
61
The `<secret-version>` will be in the output of the previous `az keyvault secret set` command.
62
62
63
-
Updating this application setting causes your web app to restart. After the app has restarted, browse to it make sure it has started correctly using the Key Vault reference.
63
+
Updating this application setting causes your function app to restart. After the app has restarted, browse to it make sure it has started correctly using the Key Vault reference.
64
64
65
65
## How to rotate the access token
66
66
67
-
It is best practice to periodically rotate the SAS key of your storage account. To ensure the web app does not inadvertently loose access, you must also update the SAS URL in Key Vault.
67
+
It is best practice to periodically rotate the SAS key of your storage account. To ensure the function app does not inadvertently loose access, you must also update the SAS URL in Key Vault.
68
68
69
69
1. Rotate the SAS key by navigating to your storage account in the Azure Portal. Under **Settings** > **Access keys**, click the icon to rotate the SAS key.
70
70
@@ -82,31 +82,31 @@ It is best practice to periodically rotate the SAS key of your storage account.
82
82
83
83
The `<secret-version>` will be in the output of the previous `az keyvault secret set` command.
84
84
85
-
## How to revoke the web app's data access
85
+
## How to revoke the function app's data access
86
86
87
-
There are two methods to revoke the web app's access to the storage account.
87
+
There are two methods to revoke the function app's access to the storage account.
88
88
89
89
### Rotate the SAS key for the Azure Storage account
90
90
91
-
If the SAS key for the storage account is rotated, the web app will no longer have access to the storage account, but it will continue to run with the last downloaded version of the package file. Restart the web app to clear the last downloaded version.
91
+
If the SAS key for the storage account is rotated, the function app will no longer have access to the storage account, but it will continue to run with the last downloaded version of the package file. Restart the function app to clear the last downloaded version.
92
92
93
-
### Remove the web app's access to Key Vault
93
+
### Remove the function app's access to Key Vault
94
94
95
-
You can revoke the web app's access to the site data by disabling the web app's access to Key Vault. To do this, remove the access policy for the web app's identity. This is the same identity you created earlier while configuring key vault references.
95
+
You can revoke the function app's access to the site data by disabling the function app's access to Key Vault. To do this, remove the access policy for the function app's identity. This is the same identity you created earlier while configuring key vault references.
96
96
97
97
## Summary
98
98
99
-
Your application files are now encrypted at rest in your storage account. When your web app starts, it retrieves the SAS URL from your key vault. Finally, the web app loads the application files from the storage account.
99
+
Your application files are now encrypted at rest in your storage account. When your function app starts, it retrieves the SAS URL from your key vault. Finally, the function app loads the application files from the storage account.
100
100
101
-
If you need to revoke the web app's access to your storage account, you can either revoke access to the key vault or rotate the storage account keys, which invalidates the SAS URL.
101
+
If you need to revoke the function app's access to your storage account, you can either revoke access to the key vault or rotate the storage account keys, which invalidates the SAS URL.
102
102
103
103
## Frequently Asked Questions
104
104
105
-
### Is there any additional charge for running my web app from the deployment package?
105
+
### Is there any additional charge for running my function app from the deployment package?
106
106
107
107
Only the cost associated with the Azure Storage Account and any applicable egress charges.
108
108
109
-
### How does running from the deployment package affect my web app?
109
+
### How does running from the deployment package affect my function app?
110
110
111
111
- Running your app from the deployment package makes `wwwroot/` read-only. Your app receives an error when it attempts to write to this directory.
0 commit comments