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
Customer-managed keys (CMKs) in [Azure AI Foundry portal](https://ai.azure.com/) provide enhanced control over the encryption of your data. By using CMKs, you can manage your own encryption keys to add an extra layer of protection and meet compliance requirements more effectively.
20
20
21
-
## About encryption in Azure AI Foundry portal
21
+
## About encryption in Azure AI Foundry
22
22
23
-
Azure AI Foundry is a service in the Microsoft Azure cloud, and it also relies on other Azure services. By default, these services use Microsoft-managed encryption keys to encrypt data in transit and at rest.
23
+
Azure AI Foundry is a service in the Microsoft Azure cloud. By default, services use Microsoft-managed encryption keys to encrypt data in transit and at rest.
24
24
25
25
::: zone pivot="hub-project"
26
26
27
27
Hub and [!INCLUDE [hub](../includes/hub-project-name.md)] resources are implementations of the Azure Machine Learning workspace and encrypt data in transit and at rest. For details, see [Data encryption with Azure Machine Learning](../../machine-learning/concept-data-encryption.md).
28
28
29
-
Azure AI services data is encrypted and decrypted using [FIPS 140-2](https://en.wikipedia.org/wiki/FIPS_140-2) compliant [256-bit AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) encryption. Encryption and decryption are transparent, meaning encryption and access are managed for you. Your data is secure by default and you don't need to modify your code or applications to take advantage of encryption.
30
-
31
29
::: zone-end
32
30
33
31
::: zone pivot="fdp-project"
34
32
35
-
## Service-side storage of encrypted data when using customer-managed keys
33
+
Data is encrypted and decrypted using [FIPS 140-2](https://en.wikipedia.org/wiki/FIPS_140-2) compliant [256-bit AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) encryption. Encryption and decryption are transparent, meaning encryption and access are managed for you. Your data is secure by default and you don't need to modify your code or applications to take advantage of encryption.
34
+
35
+
::: zone-end
36
36
37
-
Customer-managed key encryption can be enabled during project creation through the Azure portal or Bicep template. The encrypted data is stored service-side on Microsoft-managed resources. Metadata is stored in multitenant resources using document-level CMK encryption. Due to its dedicated resource model, its Azure cost is charged in your subscription.
37
+
## Storage of encrypted data when using customer-managed keys
38
+
39
+
Customer-managed key encryption can be enabled during resource creation through the Azure portal or template options. The encrypted data is stored service-side on Microsoft-managed resources using your encryption key.
38
40
39
41
> [!NOTE]
40
-
> When you use server-side encryption, Azure charges will continue to accrue during the soft delete retention period.
42
+
> Due to the dedicated hosting model for certain services when using customer-managed key encrypted data, additional charges may apply.
41
43
42
-
::: zone-end
44
+
> [!NOTE]
45
+
> When you use server-side encryption, Azure charges will continue to accrue during the soft delete retention period.
43
46
44
47
::: zone pivot="hub-project"
45
48
46
-
## Data storage in your subscription when using customer-managed keys
49
+
## Service-side storage of encrypted data when using customer-managed keys with AI hub
47
50
48
-
Hub resources store metadata in your Azure subscription when using customer-managed keys. Data is stored in a Microsoft-managed resource group that includes an Azure Storage account, Azure Cosmos DB resource and Azure AI Search.
51
+
Two architecture options are available when using customer-managed keys:
49
52
50
-
> [!IMPORTANT]
51
-
> When using a customer-managed key, the costs for your subscription will be higher because encrypted data is stored in your subscription. To estimate the cost, use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
53
+
***Encrypted data is stored in Microsoft subscription (recommended)**
52
54
53
-
The encryption key you provide when creating a hub is used to encrypt data that is stored on Microsoft-managed resources. All projects using the same hub store data on the resources in a managed resource group identified by the name `azureml-rg-hubworkspacename_GUID`. Projects use Microsoft Entra ID authentication when interacting with these resources. If your hub has a private link endpoint, network access to the managed resources is restricted. The managed resource group is deleted, when the hub is deleted.
55
+
Data is stored service-side on Microsoft-managed resources instead of in managed resources in your subscription. Metadata is stored in multitenant resources using document-level CMK encryption. An Azure AI Search instance is hosted on the Microsoft-side per customer, and for each hub.
54
56
55
-
The following data is stored on the managed resources.
57
+
***Encrypted data is stored in your subscription**
56
58
57
-
|Service|What it's used for|Example|
58
-
|-----|-----|-----|
59
-
|Azure Cosmos DB|Stores metadata for your Azure AI projects and tools|Index names, tags; Flow creation timestamps; deployment tags; evaluation metrics|
60
-
|Azure AI Search|Stores indices that are used to help query your Azure AI Foundry content.|An index based off your model deployment names|
61
-
|Azure Storage Account|Stores instructions for how customization tasks are orchestrated|JSON representation of flows you create in [Azure AI Foundry portal](https://ai.azure.com/)|
59
+
Data is stored in your subscription using a Microsoft-managed resource group that includes an Azure Storage account, Azure Cosmos DB resource and Azure AI Search. The configuration of these resources cannot be modified. Changes to its configurations are not supported.
62
60
63
-
>[!IMPORTANT]
64
-
> Azure AI Foundry uses Azure compute that is managed in the Microsoft subscription, for example when you fine-tune models or or build flows. Its disks are encrypted with Microsoft-managed keys. Compute is ephemeral, meaning after a task is completed the virtual machine is deprovisioned, and the OS disk is deleted. Compute instance machines used for 'Code' experiences are persistant. Azure Disk Encryption isn't supported for the OS disk.
61
+
All projects using the same hub store data on the resources in a managed resource group identified by the name `azureml-rg-hubworkspacename_GUID`. Projects use Microsoft Entra ID authentication when interacting with these resources. If your hub has a private link endpoint, network access to the managed resources is restricted. The managed resource group is deleted, when the hub is deleted.
65
62
66
-
## (Preview) Service-side storage of encrypted data when using customer-managed keys
63
+
The following data is stored on the managed resources.
67
64
68
-
A new architecture for customer-managed key encryption with hubs is available in preview, which resolves the dependency on the managed resource group. In this new model, encrypted data is stored service-side on Microsoft-managed resources instead of in managed resources in your subscription. Metadata is stored in multitenant resources using document-level CMK encryption. An Azure AI Search instance is hosted on the Microsoft-side per customer, and for each hub. Due to its dedicated resource model, its Azure cost is charged in your subscription via the hub resource.
65
+
|Service|What it's used for|Example|
66
+
|-----|-----|-----|
67
+
|Azure Cosmos DB|Stores metadata for your Azure AI projects and tools|Index names, tags; Flow creation timestamps; deployment tags; evaluation metrics|
68
+
|Azure AI Search|Stores indices that are used to help query your Azure AI Foundry content.|An index based off your model deployment names|
69
+
|Azure Storage Account|Stores instructions for how customization tasks are orchestrated|JSON representation of flows you create in [Azure AI Foundry portal](https://ai.azure.com/)|
69
70
70
-
> [!NOTE]
71
-
> - During this preview key rotation and user-assigned identity capabilities are not supported. Service-side encryption is currently not supported in reference to an Azure Key Vault for storing your encryption key that has public network access disabled.
72
-
> - If you are using the preview server-side storage, Azure charges will continue to accrue during the soft delete retention period.
73
71
74
72
::: zone-end
75
73
@@ -95,15 +93,16 @@ To enable customer-managed keys, the key vault containing your keys must meet th
95
93
- If you use the [Key Vault firewall](/azure/key-vault/general/access-behind-firewall), you must allow trusted Microsoft services to access the key vault.
96
94
- You must grant your hub and Azure AI Services resource's system-assigned managed identity the following permissions on your key vault: *get key*, *wrap key*, *unwrap key*.
97
95
98
-
The following limitations hold for Azure AI Services:
96
+
The following limitations hold for Azure AI Foundry:
99
97
- Only Azure Key Vault with [legacy access policies](/azure/key-vault/general/assign-access-policy) are supported.
100
98
- Only RSA and RSA-HSM keys of size 2048 are supported with Azure AI services encryption. For more information about keys, see **Key Vault keys** in [About Azure Key Vault keys, secrets, and certificates](/azure/key-vault/general/about-keys-secrets-certificates).
99
+
- Updates from Customer-Managed keys to Microsoft-managed keys are currently not supported for project sub-resources. Projects will keep referencing your encryption keys if updated.
101
100
102
-
### Enable your Azure AI Services resource's managed identity
101
+
### Enable your Azure AI Foundry resource's managed identity
103
102
104
-
If connecting with Azure AI Services, or variants of Azure AI Services such as Azure OpenAI, you need to enable managed identity as a prerequisite for using customer-managed keys.
103
+
Managed identity must be enabled as a prerequisite for using customer-managed keys.
105
104
106
-
1. Go to your Azure AI services resource.
105
+
1. Go to your Azure AI Foundry resource in Azure portal.
107
106
1. On the left, under **Resource Management**, select **Identity**.
108
107
1. Switch the system-assigned managed identity status to **On**.
109
108
1. Save your changes, and confirm that you want to enable the system-assigned managed identity.
@@ -149,11 +148,9 @@ Alternatively, use infrastructure-as-code options for automation. Example Bicep
149
148
150
149
* The customer-managed key for encryption can only be updated to keys in the same Azure Key Vault instance.
151
150
* After deployment, hubs can't switch from Microsoft-managed keys to Customer-managed keys or vice versa.
152
-
*[Azure AI services Customer-Managed Key Request Form](https://aka.ms/cogsvc-cmk) is required to use customer-managed keys in combination with Azure Speech and Content Moderator capabilities.
153
-
* At the time of creation, you can't provide or modify resources that are created in the Microsoft-managed Azure resource group in your subscription.
154
-
* You can't delete Microsoft-managed resources used for customer-managed keys without also deleting your hub.
155
-
*[Azure AI services Customer-Managed Key Request Form](https://aka.ms/cogsvc-cmk) is still required for Speech and Content Moderator.
156
-
* If you are using the [server-side preview](#preview-service-side-storage-of-encrypted-data-when-using-customer-managed-keys), Azure charges will continue to accrue during the soft delete retention period.
151
+
*[Azure AI Foundry Customer-Managed Key Request Form](https://aka.ms/cogsvc-cmk) is required to use customer-managed keys in combination with Azure Speech and Content Moderator capabilities.
152
+
*[Azure AI Foundry Customer-Managed Key Request Form](https://aka.ms/cogsvc-cmk) is still required for Speech and Content Moderator.
153
+
* If your AI Foundry resource is in a soft-deleted state(#preview-service-side-storage-of-encrypted-data-when-using-customer-managed-keys), any additional Azure charges will continue to accrue during the soft delete retention period.
title: Choose an Azure resource type for AI foundry
3
+
titleSuffix: Azure AI Foundry
4
+
description: Learn about the supported Azure resource types in Azure AI Foundry portal.
5
+
manager: scottpolly
6
+
ms.service: azure-ai-foundry
7
+
ms.topic: conceptual
8
+
ms.date: 05/18/2025
9
+
ms.author: deeikele
10
+
author: deeikele
11
+
ms.reviewer: larryfr
12
+
reviewer: larryfr
13
+
ms.custom:
14
+
---
15
+
16
+
# Choose an Azure resource type for AI foundry
17
+
18
+
An Azure resource is required to use and manage services in Azure. It defines the scope for configuring, securing, and monitoring the tools or capabilities you want to use—like AI models, agents, or storage.
19
+
20
+
AI Foundry Portal and SDK clients support multiple distinct Azure resource types, each designed to serve different development and operational needs. This article explains which use case requires which type.
21
+
22
+
## Resource Types supported with AI Foundry
23
+
24
+
***Azure AI Foundry** – The primary resource type for designing, deploying, and managing generative AI applications and agents. It provides access to agent service, models that are hosted using a serverless hosting model, evaluations, and Azure OpenAI service. This is the recommended resource type for most applications built in Azure AI Foundry.
25
+
26
+
Get started by [creating a first AI Foundry resource](../../ai-services/multi-service-resource.md?context=/azure/ai-foundry/context/context).
27
+
28
+
***Azure AI Hub** – Use this resource type in combination with Azure AI Foundry to additionally access open-source model hosting and fine-tuning capabilities, as well as Azure Machine Learning capabilities. When you create an AI Hub, an Azure AI Foundry resource is automatically provisioned. Hub resources can be used in both AI Foundry Portal and Machine Learning Studio.
29
+
30
+
***Azure AI Search** – A resource used to index and retrieve data for grounding AI applications. It can be [connected](../how-to/connections-add.md) to Azure AI Foundry agents to enable retrieval-augmented generation (RAG) and semantic search experiences.
31
+
32
+
***Azure OpenAI** – A specialized resource type that provides access to OpenAI models such as GPT-4 and GPT-4o. It offers a subset of the capabilities available in Azure AI Foundry and provides solely access to Azure OpenAI APIs.
33
+
34
+
## References
35
+
36
+
*[What is Azure Resource Manager?](/azure/azure-resource-manager/management/overview)
37
+
*[Create a first AI Foundry resource](../../ai-services/multi-service-resource.md?context=/azure/ai-foundry/context/context)
38
+
*[Create AI Foundry with advanced options](../how-to/create-resource-template.md)
39
+
*[Create a first AI Hub](../how-to/create-azure-ai-resource.md)
40
+
*[Create AI Hub with advanced options](../how-to/create-azure-ai-hub-template.md)
Copy file name to clipboardExpand all lines: articles/ai-foundry/how-to/costs-plan-manage.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ When you create resources for a hub, resources for other Azure services are also
55
55
56
56
| Service pricing page | Description with example use cases |
57
57
| --- | --- |
58
-
|[Azure AI services](https://azure.microsoft.com/pricing/details/cognitive-services/)| You pay to use services such as Azure OpenAI, Speech, Content Safety, Vision, Document Intelligence, and Language. Costs vary for each service and for some features within each service. For more information about provisioning of Azure AI services, see [Azure AI Foundry hubs](../concepts/ai-resources.md#azure-ai-services-api-access-keys).|
58
+
|[Azure AI services](https://azure.microsoft.com/pricing/details/cognitive-services/)| You pay to use services such as Azure OpenAI, Speech, Content Safety, Vision, Document Intelligence, and Language. Costs vary for each service and for some features within each service. For more information about provisioning of Azure AI services, see [Azure AI Foundry hubs](../concepts/ai-resources.md).|
59
59
|[Azure AI Search](https://azure.microsoft.com/pricing/details/search/)| An example use case is to store data in a [vector search index](./index-add.md). |
60
60
|[Azure Machine Learning](https://azure.microsoft.com/pricing/details/machine-learning/)| Compute instances are needed to run [Visual Studio Code (Web or Desktop)](./develop/vscode.md) and [prompt flow](./prompt-flow.md) via Azure AI Foundry.<br/><br/>When you create a compute instance, the virtual machine (VM) stays on so it's available for your work.<br/><br/>Enable idle shutdown to save on cost when the VM is idle for a specified time period.<br/><br/>Or set up a schedule to automatically start and stop the compute instance to save cost when you aren't planning to use it. |
61
61
|[Azure Virtual Machine](https://azure.microsoft.com/pricing/details/virtual-machines/)| Azure Virtual Machines gives you the flexibility of virtualization for a wide range of computing solutions with support for Linux, Windows Server, SQL Server, Oracle, IBM, SAP, and more. |
@@ -115,7 +115,7 @@ Here's an example of how to monitor costs for a project. The costs are used as a
115
115
116
116
:::image type="content" source="../media/cost-management/project-costs/project-settings-go-view-costs.png" alt-text="Screenshot of the Azure AI Foundry portal showing how to see project settings." lightbox="../media/cost-management/project-costs/project-settings-go-view-costs.png":::
117
117
118
-
1. Expand the **Resource** column to see the costs for each service that's underlying your [project](../concepts/ai-resources.md#organize-work-in-projects-for-customization). But this view doesn't include costs for all resources that you use in a project.
118
+
1. Expand the **Resource** column to see the costs for each service that's underlying your [project](../concepts/ai-resources.md). But this view doesn't include costs for all resources that you use in a project.
119
119
120
120
:::image type="content" source="../media/cost-management/project-costs/costs-per-project-resource.png" alt-text="Screenshot of the Azure portal cost analysis with the project and associated resources." lightbox="../media/cost-management/project-costs/costs-per-project-resource.png":::
121
121
@@ -131,9 +131,9 @@ Here's an example of how to monitor costs for a project. The costs are used as a
131
131
- The resource group name is **rg-contosoairesource**.
132
132
- The total cost for all resources and services in the example resource group is **$222.97**. In this example, $222.97 is the total cost for your application or solution that you're building with Azure AI Foundry. Again, this example assumes that all Azure AI Foundry Services are in the same resource group. But you can have resources in different resource groups.
133
133
- The project name is **contoso-outdoor-proj**.
134
-
- The costs that are limited to resources and services in the example [project](../concepts/ai-resources.md#organize-work-in-projects-for-customization) total **$212.06**.
134
+
- The costs that are limited to resources and services in the example [project](../concepts/ai-resources.md) total **$212.06**.
135
135
136
-
1. Expand **contoso-outdoor-proj** to see the costs for services underlying the [project](../concepts/ai-resources.md#organize-work-in-projects-for-customization) resource.
136
+
1. Expand **contoso-outdoor-proj** to see the costs for services underlying the [project](../concepts/ai-resources.md) resource.
137
137
138
138
:::image type="content" source="../media/cost-management/project-costs/costs-per-project-resource-details.png" alt-text="Screenshot of the Azure portal cost analysis with project expanded." lightbox="../media/cost-management/project-costs/costs-per-project-resource-details.png":::
0 commit comments