Azure Cognitive Services

Customer Feedback & Ideas for Azure Cognitive Services

Share your ideas for making Cognitive Services and the accompanying APIs work better for the applications you develop.


Catch up on the latest News and Updates


Share your Ideas and Feedback

To share your ideas on how we can make Cognitive Services better, click one of the categories underneath "Give Feedback" located in the sidebar menu to access the forum.


Documentation

API documentation available here. Within, you'll find:

§  Getting started samples
§  API References
§  Testing Consoles

Using one or more of the APIs as a "Free" preview?  Be sure to read our Terms of Service.

Contact Support

UserVoice is intended for product feedback. If you need product support, please contact either: Azure support (https://azure.microsoft.com/en-us/support/plans/) or ask a question on stack overflow (https://stackoverflow.com/questions/tagged/microsoft-cognitive)


Become a Cloud Design Insider!

Join Cloud Design Insiders, and help shape the future of Cognitive Services! As an insider, you’ll speak with program managers, designers & researchers, see new designs and ideas, provide feedback through surveys, and try out prototypes. Take the short survey to join the Cloud Design Insiders now, and we’ll see you in the community.


  1. Add «cheque» to prebuilt models

    It would be really useful to have a prebuilt model for cheques, which are much more bound to a standard than current prebuilt models (invoices, business cards and receipts).

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Vision  ·  Flag idea as inappropriate…  ·  Admin →
  2. Magnetic Ink Character Recognition (MICR) for cheques

    Right now, Azure Form Recognizer mistakenly interpret MICR special encoding characters as regular characters, as you can see in the attached screenshot. It would be very userful that it ignore/handle those special characters.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Vision  ·  Flag idea as inappropriate…  ·  Admin →
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Language  ·  Flag idea as inappropriate…  ·  Admin →
  4. Luis.ai renaming prebuilt entities

    In the Luis.ai Entities view, it's impossible to rename prebuilt entities. This might be a reasonable design decision, but the user gets no feedback when they click on the checkbox next to the entity -> Rename -> Done that this didn't work. See attached Screenshot, where renaming "percentage" does nothing.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Language  ·  Flag idea as inappropriate…  ·  Admin →
  5. iOS Speech SDK: 'SPXDialogServiceConnector' class is missing

    With ref. to https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/860#issuecomment-726436315 raising it here.

    Missing Wrapper Class:
    Connection to Bot service using 'SPXDialogServiceConnector' class is unavailable in iOS Speech SDK.
    Note: It is available for Windows SDK and Android SDK.

    Alternative: Developers need to write their own Objective-C++ wrapper to utilize the core C++ SDK class.

    If it will be available natively from iOS Speech SDK, everyone won't have to write!!!

    And this is a need of time where SDK has more potential when we connect Speech to Bot service.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Speech  ·  Flag idea as inappropriate…  ·  Admin →
  6. Azure TTS bug: <prosody rate="100%"> not handled correctly

    Problem you have encountered:
    <prosody rate="108%"> does not work as per the W3C spec for SSML.
    Neither does <prosody rate="100%">

    These result in the TTS being spoken at about twice normal rate - Which is not right.

    What you expected to happen:
    I expect the speaking rate to be DEFAULT with rate="100%", as the W3C spec your documentation references at: https://www.w3.org/TR/speech-synthesis/#S3.3.2
    literally says: "For example, a value of 100% means no change in speaking rate"

    However if instead we used: <prosody rate="+100%"> (With a '+') - THEN the speed should be doubled. The "+" and "-" are critical for relative…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Speech  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve auditing experience for qnamaker.ai to offer better action logging capabilities

    At present, the only audit logs that can be attributed to specific Azure Active Directory users are the ListKeys endpoint. From that point onwards QnAMaker.ai communicates with APIs using the endpoint keys which means there is no way differentiate between users using QnAMaker.ai.

    For us, this has posed a challenge, as it's been impossible to unpick which users have Updated, Replaced or Published APIs using QnAMaker.ai despite them being logged in using an Azure AD account.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General Cognitive Services Feedback  ·  Flag idea as inappropriate…  ·  Admin →
  8. Speaker diarization for more than 2 speakers

    Speaker diarization for more than 2 speakers.

    See this one: https://cognitive.uservoice.com/forums/555925-speaker-recognition/suggestions/34823824-add-support-for-speaker-diarization-for-untrained

    I dont feel this should be marked as resolved. Would expect support for at least 10 speakers. Additionally its currently really poor and switches between speaker 1 and 2 almost randomly. Please make this more intelligent. Its a deal breaker for us and I'm sure many others. Especially considering the google alternative can handle unlimited speakers and is far more accurate at identifying them.

    https://cloud.google.com/speech-to-text/docs/multiple-voices

    And no... expecting a sample to train it for each voice is not an option. We literally just need it to assign a number…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Speech  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base