Skip to content

Commit db6bfae

Browse files
committed
Address Reviewer Feedback
1 parent d2e4099 commit db6bfae

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

learn-pr/advocates/intro-ai-agent-service-security-controls/1-understand-azure-ai-agent-service.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ uid: learn.introduction-ai-agent-service-security-controls.understand-azure-ai-a
33
title: Understand the Azure AI Agent Service
44
metadata:
55
title: Understand the Azure AI Agent Service
6-
description: Lern about the Azure AI Agent Service.
6+
description: Learn about the Azure AI Agent Service.
77
ms.date: 03/20/2025
88
author: Orin-Thomas
99
ms.author: orthomas

learn-pr/advocates/intro-ai-agent-service-security-controls/includes/1-understand-azure-ai-agent-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@ Azure AI Agent Service is a fully managed service designed to empower developers
22

33
An AI Agent acts as a "smart" microservice that can be used to answer questions (Retrieval Augmented Generation), perform actions, or completely automate workflows. AI agents achieve this by combining the power of generative AI models to understand information resources with tools that allow that model to access and interact with real-world data sources.
44

5-
Because Azure AI Agent Service is a service fully managed by Microsoft, you can focus on building workflows and the agents that power them without needing to worry about scaling, security, or management of the underlying infrastructure for individual agents.
5+
Because Azure AI Agent Service is a service fully managed by Microsoft, you can focus on building workflows and the agents that power them without needing to worry about scaling, security, or management of the underlying infrastructure for individual agents.
66

77
As Azure AI Agent Service is a service managed by Microsoft and you don't need to worry about the underlying security of its moving parts, you should still apply standard security principals when you use the AI agent service. These principles include:
88

99
- Restrict access to the service using role based access control. Ensure that only appropriate security principals can interact with the AI agent service.
10-
- Restrict the access of the AI Agent service. The AI Agent service will be interacting with sensitive resources, such as organizational data. Ensure that the scope of this access is limited and that the AI Agent service and its tools only has necessary visibility of resources such as data stores.
10+
- Restrict the access of the AI Agent service. The AI Agent service is interacting with sensitive resources, such as organizational data. Ensure that the scope of this access is limited and that the AI Agent service and its tools only have necessary visibility of resources such as data stores.
1111
- Restrict network access to the AI Agent service and the network access of the AI agent service. Limit which network hosts can interact with the AI Agent service and control which network hosts the AI Agent service and it's associated tools are able to reach.

learn-pr/advocates/intro-ai-agent-service-security-controls/includes/2-secure-azure-ai-agent-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@ In Azure AI Foundry, Agents are associated with projects and projects are locate
22

33
Projects function as isolated development spaces, allowing developers and data scientists to build, test, and deploy AI systems. Each time a new project gets created within a hub, it automatically inherits that hub's security settings. Agents, being part of projects, can leverage the resources and configurations set at both the hub and project levels.
44

5-
You can apply security controls through the Azure AI Foundry interface or by applying security controls through the Azure portal. When you deploy a hub and project, these resources are stored within a resource group in your Azure subscription. The Azure AI Foundry provides an abstracted way of interacting with these security controls without requiring an understanding of Azure administration principles. Azure AI Foundry allows you to configure role based access control roles. Within the Azure portal, you can configure the following security settings at the Azure AI Hub level:
5+
You can apply security controls through the Azure AI Foundry interface or by applying security controls through the Azure portal. When you deploy a hub and project, these resources are stored within a resource group in your Azure subscription. The Azure AI Foundry provides an abstracted way of interacting with these security controls without requiring an understanding of Azure administration principles. Azure AI Foundry allows you to configure role based access control roles. Within the Azure portal, you can configure the following security settings at the Azure AI Hub level:
66

77
- Role based access control
88
- Network access
99
- Monitoring alerts, metrics and logs
1010

11-
At the Azure AI project level, you can configure role based access control, monitoring alerts, metrics, and logs, but can't configure network access restrictions. In most scenarios you'll configure security controls related to Azure AI Agents Service agents at the hub level. When you need to have different sets of security controls, you'll host Azure AI Agent Service agents in different Azure AI hubs.
11+
At the Azure AI project level, you can configure role based access control, monitoring alerts, metrics, and logs, but can't configure network access restrictions. In most scenarios you configure security controls related to Azure AI Agents Service agents at the hub level. When you need to have different sets of security controls, you host Azure AI Agent Service agents in different Azure AI hubs.

learn-pr/advocates/intro-ai-agent-service-security-controls/includes/3-azure-ai-agent-service-role-based-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,4 +33,4 @@ When you create a hub, the built-in role-based access control permissions grant
3333
- The resource you're trying to use has permissions set up to allow you to access it.
3434
- Your hub is allowed to access it.
3535

36-
For example, if you're trying to consume a new Blob storage that isn't hosted within the associated Azure AI hub. In this circumstance you need to ensure that hub's managed identity is added to the Blob Storage Reader role for the Blob. You will also need to ensure that you have configured workplace managed outbound access to allow network communication to the endpoint associated with the blob storage. Network access configuration is covered in more detail by the next unit.
36+
For example, if you're trying to consume a new Blob storage that isn't hosted within the associated Azure AI hub. In this circumstance, you need to ensure that hub's managed identity is added to the Blob Storage Reader role for the Blob. You'll also need to ensure that you have configured workplace managed outbound access to allow network communication to the endpoint associated with the blob storage. Network access configuration is covered in more detail by the next unit.

learn-pr/advocates/intro-ai-agent-service-security-controls/includes/4-agent-service-network-access.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ You have the following options when configuring network access:
99
- Allow Internet Outbound: Compute can access private resources and outbound data movement is unrestricted.
1010
- Allow Only Approved Outbound. Compute can access resources that specifically allowlisted and outbound data movement is restricted to approved addresses.
1111

12-
![Screenshot of Azure AI Hub networking configuraiton in Azure portal](../media/networking-configuration.png)
12+
![Screenshot of Azure AI Hub networking configuraiton in Azure portal.](../media/networking-configuration.png)
1313

1414
To access your non-Azure resources located in a different virtual network or located entirely on-premises from your Azure AI Foundry's managed virtual network, you need to configure and deploy an Application Gateway. Through this Application Gateway, you can configure full end to end access to your resources. Once you configure the Application Gateway, you can create a private endpoint from the Azure AI Foundry hub's managed virtual network to the Application Gateway. With the private endpoint, the full end to end path is secured and not routed through the Internet.
1515

16-
![Architecture diagram of Application Gateway connection from Azure AI Foundary to external resources](../media/ai-foundry-app-gateway.png)
16+
![Architecture diagram of Application Gateway connection from Azure AI Foundary to external resources.](../media/ai-foundry-app-gateway.png)

0 commit comments

Comments
 (0)