Skip to content

Commit b89ab2b

Browse files
committed
Update that QP isn't supported.
1 parent 67fc8f0 commit b89ab2b

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/azure-monitor/logs/private-storage.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -60,13 +60,14 @@ The storage account and the key vault must be in the same region, but they also
6060
#### Apply CMKs to your storage accounts
6161
To configure your Azure Storage account to use CMKs with Key Vault, use the [Azure portal](../../storage/common/customer-managed-keys-configure-key-vault.md?toc=%252fazure%252fstorage%252fblobs%252ftoc.json), [PowerShell](../../storage/common/customer-managed-keys-configure-key-vault.md?toc=%252fazure%252fstorage%252fblobs%252ftoc.json), or the [Azure CLI](../../storage/common/customer-managed-keys-configure-key-vault.md?toc=%252fazure%252fstorage%252fblobs%252ftoc.json).
6262

63-
## Link storage accounts to your Log Analytics workspace
64-
6563
> [!NOTE]
66-
> - When linking Storage Account for query, existing saved queries in workspace are deleted permanently. You can existing saved queries using a template as described in [Workspace move procedure](./move-workspace-region.md).
67-
> - Saved queries are stored in table storage and can be encrypted using Customer-managed key when configured at Storage Account creation.
68-
> - Log alerts are saved in blob storage, and you can configure Customer-managed key encryption at Storage Account creation, or update later.
69-
> - You can use a single Storage Account for query and alert. Linking storage for custom log and IIS logs might require more Storage Accounts depending on the ingestion rate and storage limits. You can link up to five Storage Accounts to a workspace.
64+
> - When linking Storage Account for query, existing saved queries in workspace are deleted permanently for privacy. You can copy existing saved queries before storage link using a template as described in [Workspace move procedure](./move-workspace-region.md).
65+
> - Queries saved in [query pack](./query-packs.md) aren't encrypted with Customer-managed key. Select **Save as Legacy query** when saving queries instead to protect them with Customer-managed key.
66+
> - Saved queries are stored in table storage and encrypted with Customer-managed key when encryption is configured at Storage Account creation.
67+
> - Log alerts are saved in blob storage where configuration of Customer-managed key encryption can be at Storage Account creation, or later.
68+
> - You can use a single Storage Account for all purposes, query, alert, custom log and IIS logs. Linking storage for custom log and IIS logs might require more Storage Accounts for scale, depending on the ingestion rate and storage limits. You can link up to five Storage Accounts to a workspace.
69+
70+
## Link storage accounts to your Log Analytics workspace
7071

7172
### Use the Azure portal
7273
On the Azure portal, open your workspace menu and select **Linked storage accounts**. A pane shows the linked storage accounts by the use cases previously mentioned (ingestion over Private Link, applying CMKs to saved queries or to alerts).

0 commit comments

Comments
 (0)