A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
Hello Kenny Wong (HK),
Welcome to Microsoft Q&A and Thank you for reaching out.
I understand that you’re encountering this issue because your current permissions don’t allow tool configuration in Microsoft Foundry. When a user lacks the required access rights, the Foundry UI intentionally greys out or leaves blank certain configuration fields (such as the Remote MCP Server endpoint) to prevent edits. The Azure AI User role you currently have only allows you to run and use existing tools and agents, but it does not permit configuring or modifying them.
To configure or edit tools in Microsoft Foundry, you must be assigned a higher-privilege role at the AI Project scope (or higher, such as Resource Group or Subscription). Roles such as Azure AI Project Contributor, Azure AI Project Manager, Azure AI Developer, or Owner allow both tool usage and configuration. In addition, if the tool interacts with Azure OpenAI or reasoning models, you must also have the Cognitive Services OpenAI Contributor role assigned. This role is required even if you already hold elevated Azure permissions, such as Service Administrator.
In terms of role capabilities, the Azure AI User role allows you to use tools but not configure them, whereas Azure AI Developer, Azure AI Project Contributor, Azure AI Project Manager, and Owner roles all allow both using and configuring tools, including editing endpoints, authentication settings, and Remote MCP server details.
To resolve the issue, go to the Azure Portal, navigate to your Azure AI Foundry / AI Project, and open Access control (IAM). Use Check access to verify your current role assignments. If the required roles are missing, request assignment of Azure AI Project Contributor (recommended minimum) and, if applicable, Cognitive Services OpenAI Contributor from your subscription administrator. After any role changes, allow 5–10 minutes for permissions to propagate, then refresh the Foundry UI and try again.
Finally, if the tool depends on other Azure resources—such as Fabric, Storage, Key Vault, or external APIs make sure you also have the necessary permissions on those resources. Missing access to a dependent resource can also cause configuration fields to remain disabled.
The behaviour you’re seeing is expected when only the Azure AI User role is assigned. Tool configuration in Microsoft Foundry requires Contributor-, Developer-, or Manager-level access, and in some scenarios, the Cognitive Services OpenAI Contributor role as well. Once the correct permissions are in place and fully propagated, the configuration fields will become editable.
Please refer this
I Hope this helps. Do let me know if you have any further queries.
Thank you!