Emotion API is being retired on Feb 15th with the Face API superseding this. Need to create a Face API component and migrate (if possible) any emotion API functionaloity to that API platform.
Our Face API, now generally available, recognizes emotions of human faces in your apps. Because Face fully replaces the existing Emotion API capabilities, we’re retiring the Emotion API on February 15, 2019.
The Emotion API will be retired on February 15, 2019—migrate to the Face API
To continue using the Emotion capabilities, please migrate to Face by that date. We encourage you to make the switch sooner to gain the benefits of Face, including richer face-recognition capabilities, a service-level agreement, and full support from Azure.
Required Action
Migrate to the Face API no later than February 15, 2019, to avoid any service disruptions to your applications and take advantage of the emotion-recognition capabilities.
glav
commented
5 years ago
Emotion API is being retired on Feb 15th with the Face API superseding this. Need to create a Face API component and migrate (if possible) any emotion API functionaloity to that API platform.
https://docs.microsoft.com/en-us/azure/cognitive-services/face/
See email notification content below.