Skip to content

Commit ba091b8

Browse files
authored
Merge pull request #196290 from LitKnd/note-oii-data-transmission
[azure-docs-pr] Adding note regarding OII data transmission
2 parents d71e6d8 + f115c34 commit ba091b8

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/synapse-analytics/security/workspaces-encryption.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ A complete Encryption-at-Rest solution ensures the data is never persisted in un
2424

2525
The first layer of encryption for Azure services is enabled with platform-managed keys. By default, Azure Disks, and data in Azure Storage accounts are automatically encrypted at rest. Learn more about how encryption is used in Microsoft Azure in the [Azure Encryption Overview](../../security/fundamentals/encryption-overview.md).
2626

27+
> [!NOTE]
28+
> Some items considered customer content, such as table names, object names, and index names, may be transmitted in log files for support and troubleshooting by Microsoft.
29+
2730
## Azure Synapse encryption
2831

2932
This section will help you better understand how customer-managed key encryption is enabled and enforced in Synapse workspaces. This encryption uses existing keys or new keys generated in Azure Key Vault. A single key is used to encrypt all the data in a workspace. Synapse workspaces support RSA 2048 and 3072 byte-sized keys, and RSA-HSM keys.

0 commit comments

Comments
 (0)