Skip to content

Commit 9e8899c

Browse files
committed
add link to recover-purge
1 parent 219b3e6 commit 9e8899c

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/ai-foundry/how-to/develop/planning.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -65,18 +65,18 @@ For most use cases, Contoso does **not use CMK**, relying on Microsoft-managed
6565

6666
Effective access management is foundational to a secure and scalable AI Foundry setup.
6767

68-
- Define required access roles and responsibilities:
68+
- **Define required access roles and responsibilities**
6969
- Identify which user groups require access to various aspects of the AI Foundry environment.
7070
- Assign built-in or custom Azure RBAC roles based on responsibilities such as:
7171
- Account owner: Manage top-level configurations such as security and shared resource connections.
7272
- Project Managers: Create and manage AI Foundry projects and their contributors.
7373
- Project Users: contribute to existing projects.
74-
- Determine Access Scope
74+
- **Determine access scope**
7575
- Choose the appropriate scope for access assignments:
7676
- Subscription level: broadest access, typically suitable for central IT or platform teams or smaller organizations.
7777
- Resource group level: Useful for grouping related resources with shared access policies. For example, an Azure Function that follows the same application lifecycle as your AI Foundry environment.
7878
- Resource or project level: Ideal for fine-grained control, especially when dealing with sensitive data or enabling self-service.
79-
- Align Identity Strategy
79+
- **Align identity strategy**
8080
- For data sources and tools integrated with AI Foundry, determine whether users should authenticate using:
8181
- Using managed identities or API key: suitable for automated services and shared access across users.
8282
- User identities: Preferred when user-level accountability or auditability is required.
@@ -137,6 +137,7 @@ A hub resource is deployed side-by-side with your AI Foundry resource and takes
137137
- Customer-Managed Keys (CMK): [Customer-managed keys in Azure AI Foundry](../../concepts/encryption-keys-portal.md)
138138
- Authentication & RBAC: [Role-based access control in Azure AI Foundry](../../concepts/rbac-azure-ai-foundry.md)
139139
- Sample Templates: [Create an AI Foundry hub using a Bicep template](../create-azure-ai-hub-template.md)
140+
- [Recover or purge deleted Azure AI Foundry resources](../../../ai-services/recover-purge-resources.md)
140141

141142
### Establish Connectivity with Other Azure Services
142143

0 commit comments

Comments
 (0)