Hello naoki_takashima,
Thank you for providing an incredibly detailed and thorough breakdown of the issue and the extensive troubleshooting steps you have already taken. Your investigation is very clear and helps to quickly isolate the problem.
Based on your report and multiple other identical reports from other users starting around September 8, 2025, it is clear that this is a widespread service issue with Azure Custom Vision that is beyond your control.
You are not alone in this. Other users have confirmed the exact same behavior :
- The issue is specific to object detection models; image classification works fine.
Training jobs get stuck indefinitely with no completion or failure message.
The problem began on or around September 8, 2025.
It is occurring across multiple Azure regions, including South Central US and Japan East.
Your assessment is correct. Since you have systematically ruled out project, data, and resource-specific causes, and because the issue is impacting multiple tenants, the root cause is almost certainly a service-side bug within the Azure Custom Vision platform that was introduced recently. Historical data shows that similar "stuck training" incidents have occurred in the past and required a fix from the Azure product team to resolve.
Recommendation
Given that this is a platform-level problem, there are no further troubleshooting steps on your side that will resolve it. The only path to a solution is to ensure the Azure engineering team is aware of the widespread impact and is actively working on a fix.
The most important action you can take is to file an official Azure Support Ticket immediately.
Go to the Azure Portal.
Navigate to "Help + support" and create a new support request.
For the issue type, select "Technical."
For the service, choose "AI Language" and then select "Custom Vision."
In the ticket description, provide all the excellent details from your post. Crucially, mention that this is a widespread issue affecting multiple users and link to your own forum post and the others you found. This will help the support engineer escalate the ticket with higher priority.
By filing a support ticket, you add your case to the official count of affected customers, which is the primary metric Microsoft uses to determine the severity and priority of an outage or service degradation.
Unfortunately, you will likely have to wait for Microsoft to deploy a fix. You can monitor the Azure Status page for any official acknowledgment of the problem, although sometimes these smaller service issues are not posted there.
Thank you for your excellent and detailed report, which is very helpful to the community and to Microsoft for diagnosing the issue.
Best regards, Jerald Felix