Skip to content

Commit 1472b78

Browse files
committed
remove empty outputs file
1 parent 51a37b4 commit 1472b78

File tree

2 files changed

+2
-6
lines changed

2 files changed

+2
-6
lines changed

articles/ai-foundry/concepts/architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Azure AI Foundry enforces a clear separation between management and development
4242

4343
- **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.
4444

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.
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.md) can be assigned at either scope to support secure automation and service access.
4646

4747
- **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.
4848

articles/ai-foundry/how-to/create-resource-terraform.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,7 @@ The examples used in article use the [AzAPI](../../developer/terraform/overview-
5858

5959
1. Create a file named `variables.tf` and insert the following code.
6060

61-
:::code language="Terraform" source="~/foundry-samples-main/samples/microsoft/infrastructure-setup-terraform/15a-private-network-standard-agent-setup/code/variables.tf":::
62-
63-
1. Create a file named `outputs.tf` and insert the following code.
64-
65-
:::code language="Terraform" source="~/foundry-samples-main/samples/microsoft/infrastructure-setup-terraform/15a-private-network-standard-agent-setup/code/outputs.tf":::
61+
:::code language="Terraform" source="~/foundry-samples-main/samples/microsoft/infrastructure-setup-terraform/15a-private-network-standard-agent-setup/code/variables.tf":::
6662

6763
## Initialize Terraform
6864

0 commit comments

Comments
 (0)