False Positives in Azure Content Safety Image Moderation (Paid Plan)

Question

We are using the paid version of Azure AI Content Safety to moderate images, but we’re encountering multiple false positives—images flagged as inappropriate when they shouldn’t be.

Is there a way to fine-tune or adjust the model to reduce these false positives? Are there specific settings or best practices to improve moderation accuracy while using the paid plan?

Despite being on a paid plan, we’re facing issues with Azure Content Safety flagging legitimate images incorrectly. We’d like to reduce these false positives without losing accuracy for actual harmful content. Has anyone else experienced this, and how did you resolve it? Any recommendations or steps to fine-tune the service would be greatly appreciated.

Thank you!

Answer 1

@Naresh Khuriwal I understand that the service is flagging some of your images incorrectly with the current model. For such scenarios, the recommendation is to customize your severity settings. See this page for details about setting the same with content safety standalone API.

If you are still seeing issues after applying the severity settings, you can raise a support case to share your data i.e. images to the team to check how the service can be improved for such false positives.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.