uploading data in microsoft foundry agent

Seeing an error like "Failed to create knowledge source" can be frustrating, especially when you're new to this. Don't worry—this is a common issue that usually comes down to just a few settings. Based on the search results, I've found the most likely causes and solutions for you.

The Short Answer

The problem is almost certainly one of two things:

1. Missing Permissions: Your Foundry Agent doesn't have the "key" to read your storage account.

Network Restrictions: Your storage account is blocking the connection from Foundry.

Let's go through the fixes one by one, starting with the most common one.

---

Step-by-Step Troubleshooting Guide

Here’s how to diagnose and fix the issue. You'll need to go into your Azure Portal to check these settings.

1. Check the Permissions (Most Likely Cause)

For Foundry to read your file, you must explicitly give it permission. Think of it like giving a friend a key to your house .

What to do: You need to assign the Storage Blob Data Reader role to your Foundry project's identity.

How to fix it:

In the Azure Portal, go to your Storage account.

  Select **Access Control (IAM)** from the left menu.
  
     Click **+ Add** and then **Add role assignment**.
     
        Search for and select the role **Storage Blob Data Reader**.
        
           On the next page (Members), under **Assign access to**, select **Managed identity**.
           
              Click **+ Select members**. In the panel that opens, search for your **Foundry project** (it might be listed under "AI Foundry" or have a similar name).
              
                 Select it and click **Save**.
                 

Tip: If you have already assigned this role, try temporarily switching your knowledge source's authentication method to "API Key" in the Foundry portal. If that works, it confirms the issue is definitely with the managed identity permissions .

2. Check the Network Settings

Your storage account might be set to "private," meaning it only accepts traffic from specific networks. Foundry might not be on that list .

What to do: Temporarily allow access from all networks to test the connection.

How to fix it:

Go to your Storage account in the Azure Portal.

  Select **Networking** from the left menu.
  
     Under "Public network access," select **Enabled from all networks**.
     
        Click **Save**.
        
           Go back to Foundry and try to create your knowledge source again.
           

If this works, you'll need to configure a more secure method (like a private endpoint or a service endpoint) for long-term use, but this is a great way to confirm the problem.

3. Double-Check Your Connection Details

Sometimes, the error is a simple typo .

What to do: Verify the exact name of your storage account and the container that holds your file.

How to fix it: When creating the knowledge source in Foundry, make sure the container URI is correct. It should look like: https://your-storage-account-name.blob.core.windows.net/your-container-name

Also, ensure your file is in a supported format (like .txt, .md, .pdf, or .docx) and is not corrupted.

If You're Still Stuck

If you've checked all the above and it still fails, the issue might be more technical. In that case, your best bet is to get help from someone with more Azure experience, as it may involve more complex setups like private endpoints or DNS .

You can also try the following community solutions that have worked for others:

Create the knowledge source using code: One user bypassed a similar portal error by creating their knowledge source using a Python script with the Azure SDK .

Create a "Capability Host": A Microsoft article suggests that for Agents to use your own storage, you sometimes need to configure a "capability host" in your Foundry project, which is an advanced step .

I hope this helps you get your data connected. Feel free to ask if you have more questions as you work through these stepsSeeing an error like "Failed to create knowledge source" can be frustrating, especially when you're new to this. Don't worry—this is a common issue that usually comes down to just a few settings. Based on the search results, I've found the most likely causes and solutions for you.

The Short Answer

The problem is almost certainly one of two things:

Missing Permissions: Your Foundry Agent doesn't have the "key" to read your storage account.

Network Restrictions: Your storage account is blocking the connection from Foundry.

Let's go through the fixes one by one, starting with the most common one.

---

Step-by-Step Troubleshooting Guide

Here’s how to diagnose and fix the issue. You'll need to go into your Azure Portal to check these settings.

1. Check the Permissions (Most Likely Cause)

For Foundry to read your file, you must explicitly give it permission. Think of it like giving a friend a key to your house .

What to do: You need to assign the Storage Blob Data Reader role to your Foundry project's identity.

How to fix it:

In the Azure Portal, go to your Storage account.

  Select **Access Control (IAM)** from the left menu.
  
     Click **+ Add** and then **Add role assignment**.
     
        Search for and select the role **Storage Blob Data Reader**.
        
           On the next page (Members), under **Assign access to**, select **Managed identity**.
           
              Click **+ Select members**. In the panel that opens, search for your **Foundry project** (it might be listed under "AI Foundry" or have a similar name).
              
                 Select it and click **Save**.
                 

Tip: If you have already assigned this role, try temporarily switching your knowledge source's authentication method to "API Key" in the Foundry portal. If that works, it confirms the issue is definitely with the managed identity permissions .

2. Check the Network Settings

Your storage account might be set to "private," meaning it only accepts traffic from specific networks. Foundry might not be on that list .

What to do: Temporarily allow access from all networks to test the connection.

How to fix it:

Go to your Storage account in the Azure Portal.

  Select **Networking** from the left menu.
  
     Under "Public network access," select **Enabled from all networks**.
     
        Click **Save**.
        
           Go back to Foundry and try to create your knowledge source again.
           

If this works, you'll need to configure a more secure method (like a private endpoint or a service endpoint) for long-term use, but this is a great way to confirm the problem.

3. Double-Check Your Connection Details

Sometimes, the error is a simple typo .

What to do: Verify the exact name of your storage account and the container that holds your file.

How to fix it: When creating the knowledge source in Foundry, make sure the container URI is correct. It should look like:
https://your-storage-account-name.blob.core.windows.net/your-container-name

Also, ensure your file is in a supported format (like .txt, .md, .pdf, or .docx) and is not corrupted.

If You're Still Stuck

If you've checked all the above and it still fails, the issue might be more technical. In that case, your best bet is to get help from someone with more Azure experience, as it may involve more complex setups like private endpoints or DNS .

You can also try the following community solutions that have worked for others:

Create the knowledge source using code: One user bypassed a similar portal error by creating their knowledge source using a Python script with the Azure SDK .

Create a "Capability Host": A Microsoft article suggests that for Agents to use your own storage, you sometimes need to configure a "capability host" in your Foundry project, which is an advanced step .

I hope this helps you get your data connected. Feel free to ask if you have more questions as you work through these steps

Hello @Akku Reba ,

Checking in to see if you had any chance to review the above response.

Do let me know if you have any further queries.

Thank you