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/ai-foundry/concepts/architecture.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
@@ -22,27 +22,27 @@ This article is intended to provide IT security teams with details on the Azure
22
22
23
23
## Azure AI resource types and providers
24
24
25
-
Within the Azure AI product family, we distinguish three [Azure resource providers](https://learn.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types) supporting user needs at different layers in the stack.
25
+
Within the Azure AI product family, we distinguish three [Azure resource providers](../../azure-resource-manager/management/resource-providers-and-types) supporting user needs at different layers in the stack.
| Microsoft.CognitiveServices | Supports Agentic and GenAI application development composing and customizing pre-built models. | Azure AI Foundry; Azure OpenAI service; Azure Speech; Azure Vision |
30
30
| Microsoft.Search | Support knowledge retrieval over your data | Azure AI Search |
31
31
| Microsoft.MachineLearningServices | Train, deploy and operate custom and open source machine learning models | Azure AI Hub (and its projects); Azure Machine Learning Workspace |
32
32
33
-
Azure AI Foundry resource is the primary resource for Azure AI and is recommended for most use cases. It is built on the same [Azure resource provider and resource type](https://learn.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types) as Azure OpenAI service, Azure Speech, Azure Vision, and Azure Language service. It provides access to the superset of capabilities from each individual services combined.
33
+
Azure AI Foundry resource is the primary resource for Azure AI and is recommended for most use cases. It is built on the same [Azure resource provider and resource type](../../azure-resource-manager/management/resource-providers-and-types) as Azure OpenAI service, Azure Speech, Azure Vision, and Azure Language service. It provides access to the superset of capabilities from each individual services combined.
Resource types under the same provider namespace share the same control plane, hence use similar [Azure RBAC](https://learn.microsoft.com/azure/role-based-access-control/) actions, networking configurations and aliases for Azure Policy configuration. If you are upgrading from Azure OpenAI to Azure AI Foundry, this means your existing custom Azure policies and Azure RBAC options apply.
37
+
Resource types under the same provider namespace share the same control plane, hence use similar [Azure RBAC](../../role-based-access-control/) actions, networking configurations and aliases for Azure Policy configuration. If you are upgrading from Azure OpenAI to Azure AI Foundry, this means your existing custom Azure policies and Azure RBAC options apply.
38
38
39
39
## Security-driven separation of concerns
40
40
41
41
Azure AI Foundry enforces a clear separation between management and development operations to ensure secure and scalable AI workloads.
42
42
43
43
-**Top-Level Resource Governance:** Management operations—such as configuring security, establishing connectivity with other Azure services, and managing deployments—are scoped to the top-level Azure AI Foundry resource. Development activities are isolated within dedicated project containers, which encapsulate use cases and provide boundaries for access control, files, agents, and evaluations.
44
44
45
-
-**Role-Based Access Control (RBAC):** Azure RBAC actions are designed to reflect this separation of concerns. Control plane actions (e.g., creating deployments and projects) are distinct from data plane actions (e.g., building agents, running evaluations, uploading files). RBAC assignments can be scoped at both the top-level resource and individual project level. [Managed identities](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/overview) can be assigned at either scope to support secure automation and service access.
45
+
-**Role-Based Access Control (RBAC):** Azure RBAC actions are designed to reflect this separation of concerns. Control plane actions (e.g., creating deployments and projects) are distinct from data plane actions (e.g., building agents, running evaluations, uploading files). RBAC assignments can be scoped at both the top-level resource and individual project level. [Managed identities](../../../entra/identity/managed-identities-azure-resources/overview) can be assigned at either scope to support secure automation and service access.
46
46
47
47
-**Monitoring and Observability:** Azure Monitor metrics are segmented by scope. Management and usage metrics are available at the top-level resource, while project-specific metrics—such as evaluation performance or agent activity—are scoped to the individual project containers.
Copy file name to clipboardExpand all lines: articles/ai-foundry/how-to/create-resource-terraform.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ ai-usage: ai-assisted
20
20
21
21
In this article, you use Terraform to create an [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs) resource. You will learn how to use Terraform to create AI Foundry management configurations including projects, deployments and connections.
22
22
23
-
The examples used in article use the [AzAPI](https://learn.microsoft.com/azure/developer/terraform/overview-azapi-provider) Terraform provider. Similar [AzureRM](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs) provider support is available via the classic AzureRM_AIServices module, but is limited in functionality to resource and deployment creation.
23
+
The examples used in article use the [AzAPI](../../developer/terraform/overview-azapi-provider) Terraform provider. Similar [AzureRM](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs) provider support is available via the classic AzureRM_AIServices module, but is limited in functionality to resource and deployment creation.
0 commit comments