accessing AI foundry/ agent creation / thread creation

Question

accessing AI foundry/ agent creation / thread creation

Bhatt, Nitin 0

How can we access Ai foundry features like agent creation / thread creation etc. within azure foundryportal. why is it giving me error that it has to be public access ? I am in same resource group and have all acccess with in portal ( not from outside)

Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-06T18:21:09.5566667+00:00
Hi Bhatt, Nitin,

Thanks for the clarification in the private chat. **BYO(**Bring Your Own) is not required in your case.

If you want to use only Foundry‑managed features (built‑in Vector Store, Storage, and Notebooks) and your user ID already has Contributor access on the resource group, the recommended approach is:

Use Foundry‑managed resources (default vector DB and storage) created from the AI Foundry portal.

Start with Public network access enabled (no VNet / Private Endpoints). This avoids connectivity and permission issues.

Create and attach Vector Store and Storage directly from Foundry → Connections.

Launch a Python notebook / compute session inside the Foundry portal. It uses Azure AD authentication, and your RBAC (Contributor) is automatically honored.

Upload documents and index them into the Foundry‑managed vector store and use them directly in Agents and notebooks.

VNet and Private Link are only needed if you’re bringing enterprise‑restricted networking.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!
Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-08T18:47:00.3866667+00:00

Hi Bhatt, Nitin,

Did you get any chance to review the response.
Thankyou!
Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-09T19:04:22.8466667+00:00

Hi Bhatt, Nitin,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thankyou!

1 answer

Your answer

Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-06T18:21:09.5566667+00:00

Hi Bhatt, Nitin,

Thanks for the clarification in the private chat. **BYO(**Bring Your Own) is not required in your case.

If you want to use only Foundry‑managed features (built‑in Vector Store, Storage, and Notebooks) and your user ID already has Contributor access on the resource group, the recommended approach is:

Use Foundry‑managed resources (default vector DB and storage) created from the AI Foundry portal.

Start with Public network access enabled (no VNet / Private Endpoints). This avoids connectivity and permission issues.

Create and attach Vector Store and Storage directly from Foundry → Connections.

Launch a Python notebook / compute session inside the Foundry portal. It uses Azure AD authentication, and your RBAC (Contributor) is automatically honored.

Upload documents and index them into the Foundry‑managed vector store and use them directly in Agents and notebooks.

VNet and Private Link are only needed if you’re bringing enterprise‑restricted networking.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!
Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-08T18:47:00.3866667+00:00

Hi Bhatt, Nitin,

Did you get any chance to review the response.
Thankyou!
Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-09T19:04:22.8466667+00:00

Hi Bhatt, Nitin,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thankyou!

Answer 1

Hi Bhatt, Nitin,

Thank you for posting your question on Microsoft Q&A.

The behavior you’re seeing (agent creation / thread creation failing unless public access is enabled) is expected based on how Azure AI Foundry Agent Service networking works, depending on the setup type you’re using.

By default, Azure AI Foundry projects are created using the Basic Agent Setup. In this setup:

The platform uses Microsoft‑managed resources
Agent creation and thread creation require public network accessibility
If your Azure AI Search, storage, or other dependent resources have public access disabled, the portal will block agent/thread creation

That’s why you are seeing the error that public access is required even though everything is in the same resource group.

You have two supported options, depending on your security requirements.

1.Keep Basic setup (Quickest fix)

If you are currently testing or prototyping, you can:

Enable Public network access on the dependent resources (for example:
- Azure AI Search
- Storage account used by the project)
Retry agent creation and thread creation in the AI Foundry portal

This aligns with how the Basic Agent Setup is designed.

2.Use Standard Agent Setup with Private Networking (Recommended)

If your requirement is to keep all resources private, you should use the Standard Agent Setup, which fully supports:

Private endpoints
BYO Azure AI Search
BYO Storage
BYO Thread storage (Cosmos DB)
VNet isolation for agent execution

With this setup:

Agents run inside your VNet
No public access is required
Thread creation works securely with private resources

Note: Full private networking is currently supported via the Classic Foundry experience or SDK/CLI-based deployment, not completely through the New Portal UI.

Official documentation:

Use a virtual network with Foundry Agent Service (Classic): https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks
Configure private endpoints for Foundry projects: https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/configure-private-link

Once networking is configured correctly, thread creation is supported via:

Portal
SDK
REST API

Thread API documentation:

Create Thread (REST API): https://learn.microsoft.com/en-us/rest/api/aifoundry/aiagents/threads/create-thread
Threads, Runs, and Messages concept: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/threads-runs-messages

In Short: The error is not a permission issue. It’s caused by using Basic Agent Setup with private-only resources.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!

Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator

2026-01-12T19:12:07.9266667+00:00

Hi Bhatt, Nitin,

Please let me know if the issue persists after these checks. If you have any remaining questions or need additional details, I’ll be glad to provide further clarification or guidance.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Thankyou!

Share via

accessing AI foundry/ agent creation / thread creation

1 answer

Your answer