Skip to content

Commit 2d871d0

Browse files
committed
Merge branch 'master' of https://github.com/Microsoft/azure-docs-pr into issue12574
2 parents e994adb + 244a51e commit 2d871d0

File tree

4 files changed

+19
-19
lines changed

4 files changed

+19
-19
lines changed

articles/backup/backup-introduction-to-azure-backup.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: carmonm
77
keywords: backup and restore; recovery services; backup solutions
88
ms.service: backup
99
ms.topic: overview
10-
ms.date: 3/1/2018
10+
ms.date: 8/2/2018
1111
ms.author: markgal
1212
ms.custom: mvc
1313
---
@@ -151,8 +151,8 @@ With **Full Backup**, each backup copy contains the entire data source. Full bac
151151
### Security
152152
| Feature | Azure Backup agent | System Center DPM | Azure Backup Server | Azure IaaS VM Backup |
153153
| --- | --- | --- | --- | --- |
154-
| Network security<br/> (to Azure) |![Yes][green] |![Yes][green] |![Yes][green] |![Partially][yellow] |
155-
| Data security<br/> (in Azure) |![Yes][green] |![Yes][green] |![Yes][green] |![Partially][yellow] |
154+
| Network security<br/> (to Azure) |![Yes][green] |![Yes][green] |![Yes][green] |![Yes][green] |
155+
| Data security<br/> (in Azure) |![Yes][green] |![Yes][green] |![Yes][green] |![Yes][green] |
156156

157157
![table key](./media/backup-introduction-to-azure-backup/table-key.png)
158158

@@ -165,7 +165,7 @@ All backup traffic from your servers to the Recovery Services vault is encrypted
165165
>
166166
167167
#### Data security
168-
Backing up Azure VMs requires setting up encryption *within* the virtual machine. Use BitLocker on Windows virtual machines and **dm-crypt** on Linux virtual machines. Azure Backup does not automatically encrypt backup data that comes through this path.
168+
Backing up Azure VMs requires setting up encryption *within* the virtual machine. Azure Backup supports Azure Disk Encryption, which uses BitLocker on Windows virtual machines and **dm-crypt** on Linux virtual machines. On the back end, Azure Backup uses [Azure Storage Service encryption](../storage/common/storage-service-encryption.md), which protects data at rest.
169169

170170
### Network
171171
| Feature | Azure Backup agent | System Center DPM | Azure Backup Server | Azure IaaS VM Backup |

articles/cosmos-db/performance-tips.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,9 +130,10 @@ So if you're asking "How can I improve my database performance?" consider the fo
130130
If you are testing at high throughput levels (>50,000 RU/s), the client application may become the bottleneck due to the machine capping out on CPU or Network utilization. If you reach this point, you can continue to push the Azure Cosmos DB account further by scaling out your client applications across multiple servers.
131131
8. **Cache document URIs for lower read latency**
132132

133-
Cache document URIs whenever possible for the best read performance.
133+
Cache document URIs whenever possible for the best read performance. You have to define logic to cache the resourceid when you create the resource. Resourceid based lookups are faster than name based lookups, so caching these values improves the performance.
134+
134135
<a id="tune-page-size"></a>
135-
9. **Tune the page size for queries/read feeds for better performance**
136+
1. **Tune the page size for queries/read feeds for better performance**
136137

137138
When performing a bulk read of documents using read feed functionality (for example, ReadDocumentFeedAsync) or when issuing a SQL query, the results are returned in a segmented fashion if the result set is too large. By default, results are returned in chunks of 100 items or 1 MB, whichever limit is hit first.
138139

articles/storage/common/storage-service-encryption-customer-managed-keys.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Azure Storage Service Encryption using customer-managed keys in Azure Key Vault | Microsoft Docs
3-
description: Use the Azure Storage Service Encryption feature to encrypt Azure Blob storage, Azure Files, Azure Queue storage, and Azure Table storage on the service side when storing the data, and decrypt it when retrieving the data using customer-managed keys.
3+
description: Use the Azure Storage Service Encryption feature to encrypt Azure Blob storage and Azure Files on the service side when storing the data, and decrypt it when retrieving the data using customer-managed keys.
44
services: storage
55
author: lakasa
66
manager: jeconnoc
@@ -19,7 +19,7 @@ You can use Microsoft-managed encryption keys with SSE or you can use your own e
1919
SSE for Azure Blob storage and Azure Files is integrated with Azure Key Vault, so that you can use a key vault to manage your encryption keys. You can create your own encryption keys and store them in a key vault, or you can use Azure Key Vault's APIs to generate encryption keys. With Azure Key Vault, you can manage and control your keys and also audit your key usage.
2020

2121
> [!Note]
22-
> Storage Service Encryption is not available for [Azure Managed Disks](../../virtual-machines/windows/managed-disks-overview.md). We recommend you use encryption on the OS level, such as [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md), which uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide encryption integrated with KeyVault.
22+
> Storage Service Encryption using customer-managed keys is not available for [Azure Managed Disks](../../virtual-machines/windows/managed-disks-overview.md). [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md) uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide an encryption solution integrated with KeyVault.
2323
2424
Why create your own keys? Custom keys give you more flexibility, so that you can create, rotate, disable, and define access controls. Custom keys also enable you to audit the encryption keys used to protect your data.
2525

@@ -117,7 +117,7 @@ Yes.
117117
There is a cost associated for using Azure Key Vault. For more details, visit [Key Vault Pricing](https://azure.microsoft.com/pricing/details/key-vault/). There is no additional cost for SSE, which is enabled for all storage accounts.
118118

119119
**Is Storage Service Encryption available on Azure Managed Disks?**
120-
No, Storage Service Encryption is not available for [Azure Managed Disks](../../virtual-machines/windows/managed-disks-overview.md). We recommend you use encryption on the OS level, such as [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md), which uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide encryption integrated with KeyVault.
120+
Storage Service Encryption is available for Azure Managed Disks with Microsoft-managed keys, but not with customer managed keys. In lieu of Managed Disks supporting SSE with customer-managed keys, we recommend [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md), which uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide encryption integrated with KeyVault.
121121

122122
**How is Storage Service Encryption different from Azure Disk Encryption?**
123123
Azure Disk Encryption provides integration between OS-based solutions like BitLocker and DM-Crypt and Azure KeyVault. Storage Service Encryption provides encryption natively at the Azure storage platform layer, below the virtual machine.

articles/storage/common/storage-service-encryption.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Azure Storage Service Encryption for data at rest | Microsoft Docs
3-
description: Use the Azure Storage Service Encryption feature to encrypt Azure Blob storage on the service side when storing the data, and decrypt it when retrieving the data.
3+
description: Use the Azure Storage Service Encryption feature to encrypt Azure Managed Disks, Azure Blob storage, Azure Files, Azure Queue storage, and Azure Table storage on the service side when storing the data, and decrypt it when retrieving the data.
44
services: storage
55
author: lakasa
66
manager: jeconnoc
@@ -12,19 +12,21 @@ ms.author: lakasa
1212
---
1313

1414
# Azure Storage Service Encryption for data at rest
15-
Azure Storage Service Encryption for data at rest helps you protect your data to meet your organizational security and compliance commitments. With this feature, the Azure storage platform automatically encrypts your data before persisting it to Azure Blob storage, Azure Files, or Azure Queue storage, and decrypts the data before retrieval. The handling of encryption, encryption at rest, decryption, and key management in Storage Service Encryption is transparent to users. All data written to the Azure storage platform is encrypted through 256-bit [AES encryption](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard), one of the strongest block ciphers available.
15+
Azure Storage Service Encryption for data at rest helps you protect your data to meet your organizational security and compliance commitments. With this feature, the Azure storage platform automatically encrypts your data before persisting it to Azure Managed Disks, Azure Blob storage, Azure Files, or Azure Queue storage, and decrypts the data before retrieval. The handling of encryption, encryption at rest, decryption, and key management in Storage Service Encryption is transparent to users. All data written to the Azure storage platform is encrypted through 256-bit [AES encryption](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard), one of the strongest block ciphers available.
1616

1717
Storage Service Encryption is enabled for all new and existing storage accounts and cannot be disabled. Because your data is secured by default, you don't need to modify your code or applications to take advantage of Storage Service Encryption.
1818

1919
The feature automatically encrypts data in:
2020

21-
- Azure Blob storage, Azure Files, Azure Queue storage, Azure Table storage.
21+
- Azure storage services:
22+
- Azure Managed Disks
23+
- Azure Blob storage
24+
- Azure Files
25+
- Azure Queue storage
26+
- Azure Table storage.
2227
- Both performance tiers (Standard and Premium).
2328
- Both deployment models (Azure Resource Manager and classic).
2429

25-
> [!Note]
26-
> Storage Service Encryption is not available for [Azure Managed Disks](../../virtual-machines/windows/managed-disks-overview.md). We recommend you use encryption on the OS level, such as [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md), which uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide encryption integrated with KeyVault.
27-
2830
Storage Service Encryption does not affect the performance of Azure storage services.
2931

3032
You can use Microsoft-managed encryption keys with Storage Service Encryption, or you can use your own encryption keys. For more information about using your own keys, see [Storage Service Encryption using customer-managed keys in Azure Key Vault](storage-service-encryption-customer-managed-keys.md).
@@ -51,14 +53,11 @@ Encryption is enabled by default, and there is no provision to disable encryptio
5153
There is no additional cost.
5254

5355
**Can I use my own encryption keys?**
54-
Yes, you can use your own encryption keys. For more information, see [Storage Service Encryption using customer-managed keys in Azure Key Vault](storage-service-encryption-customer-managed-keys.md).
56+
For Azure Blob storage and Azure Files, yes, you can use your own encryption keys. Customer-managed keys are not currently supported by Azure Managed Disks. For more information, see [Storage Service Encryption using customer-managed keys in Azure Key Vault](storage-service-encryption-customer-managed-keys.md).
5557

5658
**Can I revoke access to the encryption keys?**
5759
Yes, if you [use your own encryption keys](storage-service-encryption-customer-managed-keys.md) in Azure Key Vault.
5860

59-
**Is Storage Service Encryption available on Azure Managed Disks?**
60-
No, Storage Service Encryption is not available for [Azure Managed Disks](../../virtual-machines/windows/managed-disks-overview.md). We recommend you use encryption on the OS level, such as [Azure Disk Encryption](../../security/azure-security-disk-encryption-overview.md), which uses industry-standard [BitLocker](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview) on Windows and [DM-Crypt](https://en.wikipedia.org/wiki/Dm-crypt) on Linux to provide encryption integrated with KeyVault.
61-
6261
**How is Storage Service Encryption different from Azure Disk Encryption?**
6362
Azure Disk Encryption provides integration between OS-based solutions like BitLocker and DM-Crypt and Azure KeyVault. Storage Service Encryption provides encryption natively at the Azure storage platform layer, below the virtual machine.
6463

0 commit comments

Comments
 (0)