An Azure service that provides natural language capabilities including sentiment analysis, entity extraction, and automated question answering.
Hello @Riswan Jaman
The F0 tier should not, by itself, prevent you from completing the Custom Text Classification exercise.
Microsoft currently documents Custom Text Classification as supporting both:
- F0 - Free tier
- S - Paid tier
F0 does have lower quotas. For example, one hour of training per month and one deployment per project—but the Authoring API is supported.
So I wouldn't recommend upgrading to S solely to resolve the 404 Resource Not Found error.
Instead, check how the Language resource was created. Microsoft states that Custom Text Classification requires the resource to have the Custom text classification / Custom Named Entity Recognition feature enabled, along with a connected Azure Storage account and system-assigned managed identity.
In the Azure portal, check your Language resource and verify:
- Custom text classification / Custom NER is enabled.
- System-assigned managed identity is enabled.
- A supported Azure Storage account is connected.
- The resource is in a region supported by Custom Text Classification.
Microsoft's current setup instructions are here:
Microsoft Learn: Create a Custom Text Classification project
Also check the Authoring API URL. The current API pattern is:
{ENDPOINT}/language/authoring/analyze-text/projects/{PROJECT-NAME}?api-version={API-VERSION}
A 404 Resource Not Found can therefore indicate an incorrect endpoint/resource configuration rather than an F0 restriction.
Regarding Language Studio, I wouldn't recommend trying to solve this by obtaining an organizational/school email specifically for the lab. Microsoft's current Custom Text Classification documentation provides both portal/Foundry and REST API workflows, so the exercise can be approached using the supported resource/API path.
I would therefore first recreate or verify the Language resource using Microsoft's current Custom Text Classification quickstart rather than requesting temporary S-tier credits.
If you still receive 404 Resource Not Found, please post the request URL with the resource name/key removed, API version, and the Azure resource type shown under Properties. Don't post your subscription ID, resource key, or other credentials publicly.
One additional point: if the AI-103 Module 2 instructions specifically require the old Language Studio experience and that experience no longer accepts the account type used by the learner, that may indicate the training exercise needs updating to match Microsoft's current Foundry workflow. A Microsoft Learn moderator could help confirm that part.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.