[ ABORT TO HUD ]
SEQ. 1
SEQ. 2
SEQ. 3
SEQ. 4

Hubs, Projects & Organization

⚙️ Setting Up Your Environment 8 min 60 BASE XP

Understanding the Hierarchy

Foundry uses a two-level hierarchy to organize AI workloads:

Hub vs Project

ConceptPurposeAnalogy
HubTop-level governance container. Manages shared resources, networking, RBAC, and policiesThe IT department's control plane
ProjectIsolated workspace for building AI apps. Contains deployments, agents, indexes, evaluationsA team's development environment

Best Practices for Organization

  • One Hub per department/business unit — centralizes governance
  • One Project per application/team — provides isolation
  • Share connections at Hub level — models, search indexes accessible to all projects
  • Scope RBAC to Projects — developers get Project-level access, admins get Hub-level
Production Hub (Central IT manages)
  ├── Customer Service Project (CS team)
  ├── Internal Search Project (Platform team)
  └── Analytics Agent Project (Data team)

Development Hub (Lower restrictions)
  ├── Sandbox Project (Anyone can experiment)
  └── POC Project (Innovation team)
💡 Key Insight: In the new Foundry portal, the Hub concept is simplified. You create a Foundry resource that acts as both Hub and Project. The classic Hub/Project separation still applies to legacy "Azure AI Foundry hub" resources.
FOUNDRY VERIFICATION
QUERY 1 // 2
What is the recommended organizational pattern for Hubs and Projects?
One Hub per project
One Hub per department, one Project per application/team
No Hubs — use Projects only
One Project for the entire organization
Watch: 139x Rust Speedup
Hubs, Projects & Organization | Setting Up Your Environment — Azure Foundry Academy