Wrong PII detected in Azure Content Moderation

Question

We tested our Azure Content Moderator in eastus.

The request URL is "https://omitted.cognitiveservices.azure.com/contentmoderator/moderate/v1.0/ProcessText/Screen?classify=True", body is "user.. admin@ssss .com", the service's response is:

Pragma: no-cache  
apim-request-id: 9f93e787-937a-4fab-9ca3-bbbcc9fc01c0  
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload  
x-content-type-options: nosniff  
CSP-Billing-Usage: CognitiveServices.ContentModerator.Transaction=1  
Cache-Control: no-cache  
Date: Fri, 06 Nov 2020 11:34:07 GMT  
X-AspNet-Version: 4.0.30319  
X-Powered-By: ASP.NET  
Content-Length: 745  
Content-Type: application/json; charset=utf-8  
Expires: -1  
  
{  
  "OriginalText": "user.. admin@example.com",  
  "NormalizedText": "user.. admin@example.com",  
  "Misrepresentation": null,  
  "PII": {  
    "Email": [{  
      "Detected": "admin@example.com",  
      "SubType": "Regular",  
      "Text": "admin@example.com",  
      "Index": 7  
    }, {  
      "Detected": "user.admin@example.com",  
      "SubType": "Suspected",  
      "Text": "user.admin@example.com",  
      "Index": 0  
    }],  
    "IPA": [],  
    "Phone": [],  
    "Address": [],  
    "SSN": []  
  },  
  "Classification": {  
    "ReviewRecommended": false,  
    "Category1": {  
      "Score": 0.00066937919473275542  
    },  
    "Category2": {  
      "Score": 0.2296631783246994  
    },  
    "Category3": {  
      "Score": 0.07756727933883667  
    }  
  },  
  "Language": "eng",  
  "Terms": null,  
  "Status": {  
    "Code": 3000,  
    "Description": "OK",  
    "Exception": null  
  },  
  "TrackingId": "USE_ibiza_4e2f4e99-d396-4495-84e8-263d713de05b_ContentModerator.F0_d0bd7af2-31c7-4946-8cfa-824aa3ab4e4c"  
}  

Why the second PII body (line 27) refers to "user.admin@ssss .com"?
There is no "user.admin@ssss .com" in the request.

Answer 1

@Now4real Thanks for the feedback. It's known issue, we have forwarded this feedback to our product team. You can also raise a user voice request here so the community can vote and provide their feedback, the product team then checks this feedback and implement this in future releases.

Answer 2

This bug is still present.