An Azure service that provides natural language capabilities including sentiment analysis, entity extraction, and automated question answering.
To create a project in a Microsoft Foundry (classic) hub, the account must have sufficient permissions on the underlying Azure resources. A “restricted permission” or similar error when creating a project typically indicates missing Contributor/Owner rights or insufficient access to the hub’s resource group or subscription.
Troubleshoot and resolve as follows:
- Verify Azure role assignments
- Ensure the user has Contributor or Owner role on at least the resource group where the hub and project will be created, or on the subscription.
- If part of a team, ask the Azure administrator to grant these permissions or to create the hub/project on behalf of the user.
- Confirm access to the hub
- If a hub already exists, confirm that the user has access to that hub’s resource group with at least Contributor permissions. Without this, project creation in that hub will fail with a permission-related error.
- Try creating the project from the Foundry portal
- Sign in to Microsoft Foundry with the correct account.
- Make sure New Foundry is toggled off (using Foundry (classic)).
- If not in any project, select Create new (top right). If already in a project, select the project breadcrumb → Create new resource.
- Select AI hub resource → Next.
- Enter a project name.
- Choose an existing hub from the dropdown, or select Create a new hub.
- If creating a new hub, ensure the user has Owner or Contributor permissions on the selected resource group; otherwise, the creation will fail due to restricted permissions.
- Select Create.
- If creating a new hub as part of the project
- In the Create a project form, expand the hub customization panel.
- Select a Resource group where the user has Contributor or Owner.
- Select a Location.
- Select Create a project.
- If the error persists, have an administrator create the hub separately with the required configuration and then create the project in that hub.
- Validate using CLI or SDK (optional)
- Use Azure CLI to confirm authentication and visibility of existing hubs:
az login az ml workspace list --resource-group <your-resource-group-name> - If listing workspaces (hubs) fails with a permission error, the user lacks required rights on that resource group or subscription.
- Use Azure CLI to confirm authentication and visibility of existing hubs:
If, after these checks, the error still appears, the next step is for an Azure administrator to review the user’s role assignments on the subscription and resource group and ensure at least Contributor access is granted before attempting project creation again.
References: