Microsoft Foundry cannot access exist agent and create agent

Question

Our company has been using Microsoft Foundry to build Agents. It was working fine two weeks ago, but now the existing Agents can no longer be accessed (they appear as deleted). I also cannot create new Agents anymore.

My account has already been assigned the following roles in the resource IAM:

Contributor

Azure AI User

Azure AI Developer

• Cognitive Services OpenAI Contributor But the issue still persists. May I ask if there are currently any known outages or problems with Microsoft Foundry?
  

Answer 1

Hello Benson KH Chen ,

Welcome to Microsoft Q&A .Thank you for reaching out with detailed description of the case.

It is understood that you are getting 403 errors while trying to create or build agents on Foundry, which were previously working fine with your enabled roles – Contributor, Azure AI User , Azure AI Developer and Cognitive Services OpenAI Contributor.

From the mentioned details, the 403 errors are not likely because of the assigned roles

1.      If the issue was because of RBAC , the error would be thrown as “access denied”.

2.      You were able to access and build agents with the same roles earlier.

As asked, currently few users are facing similar outages and problems with Microsoft Foundry.

The below link can be used to check for Foundry related outages

Microsoft Foundry Status

Please also visit your Azure Service Health dashboard on the portal to check for any planned maintenance activities or outages in your region.

If there are no reported outages or planned activities being reflected on the Service Health, then please go ahead with the following:

As the agents were working 2 weeks ago , but now existing agents appear deleted and new agents cannot be created  throwing 403 errors – this usually points to an access, subscription or resource-level change.

Please check if any of the following are contributing to the issue.

1.      If the subscription is switched or Azure AD tenant changed or the Foundry project itself is moved to other resource groups, then agents will “appear deleted” and the creation fails with 403 error. This is because we are looking at a different backend resource.

2.      If Azure OpenAI Resource was deleted or moved, then the agents depending on  the underlying Azure OpenAI Service break and new ones cannot be created. Please check if that resource was deleted , was renamed ,was moved to another subscription, has networking restrictions applied or lost if you lost your  RBAC access on them. They don’t truly disappear — the backend call fails.

3.      Please recheck your RBAC on the resources got removed or if the scope changed. Maybe the Resource group scope got changed or OpenAI resource got moved to another RG.

4.      Additionally , please also check for private endpoint issues, key vault dependencies and if the associated storage account is removed

 

As the agents are “Appearing Deleted” –

1. On Azure Portal > Confirm correct Subscription
2. Then open the Azure OpenAI resource please check if it still exists
3. Check IAM on that resource to RBAC and roles
   • Contributor OR
   • Cognitive Services OpenAI Contributor
4. Check Activity Log to confirm if the resource deleted or moved

 

Please refer these for additional information –

Role-based access control for Microsoft Foundry - Microsoft Foundry | Microsoft Learn

Role-based access control for Azure OpenAI - Microsoft Foundry | Microsoft Learn

 

Please let me know if you have any questions.

Thank you!