First impressions and feedback on Azure Content Moderator

rbrundritt 15,226 Reputation points Microsoft Employee
2023-03-03T00:10:31.31+00:00

I'm going through a couple of training modules on Azure Content Moderator and noticed a few things that really bothered me about the service that I wanted to provide as feedback as considerations for a future major version update:

  • Non-descriptive category names are returned (Category1, Category2, Category3). A key part of Microsoft's standards of well-designed systems is using descriptive names for services and parameters. One training module I went through didn't explain what these categories are, and it wasn't possible to get a sense looking at a sample response. Something like the following would be much more developer friendly:
    • Category1: explicitAdult
    • Category2: suggestiveMature
    • Category3: offensive
  • Use of ISO 639-2 language code. This is the only Azure service I have ever come across (possibly only Microsoft service) that uses "eng" for English (ISO 639-2) rather than an "en" (ISO 639-1 code) or a localized version like "en-US" (IETF). This is something that could be handled on the backend without any changes to the frontend API by simply adding some logic to map "en", and "en-[any country code]" to the "eng". I know of a couple of Azure services that do this behind the scenes so as to be more flexible.
Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,935 questions
{count} votes

Accepted answer
  1. romungi-MSFT 41,866 Reputation points Microsoft Employee
    2023-03-03T11:51:39.23+00:00

    rbrundritt Thanks for adding your feedback. We will relay this back to the PG for incorporating the same in the future version of the product. I believe the service is now offering a new private preview API called "Project Carnegie". You can sign up for this private preview and try the new API by following this documentation that is available at this point. Going through the preview documentation link I think the language code scenario is addressed by following "en" instead of "eng", some of the categories have also changed with level added to each of them. You could also drop an email to the team using the email at the bottom of the documentation link to share your feedback. Thanks!!

    0 comments No comments

0 additional answers

Sort by: Most helpful