Currently there isn't a way to clear out all existing QnA pairs within a Knowledgebase. The PATCH interface is good, but if I just want to re-create the items in my current model then a full PUT would be required and I can then re-submit all items that should exist within the KB. Any items not in the PUT request would be deleted.3 votes
In the v2.0 APIs you are limited to the single PATCH operation to update a Knowledgebase. I find that this API is slow and would like to see support for single QnA CRUD updates10 votes
Currently the only API endpoint returns the first highest scoring answer.
However, for the sake of providing alternatives to the end user if that answer wasn't helpful - or if the highest answer wasn't higher than a given threshold. It would be nice to provide them the top alternative questions in our knowledge base that the service may have ranked lower.
Honestly - I think this should be a priority. You've got an undocumented API that does just this.22 votes
Top N feature added with the V2.0 APIs.
To use this service internal in our Organisation it should be possible to restrict the access to security groups within our AAD.24 votes
This has been addressed with the GA stack.
While this service is in free preview, it would be nice to see the quota usage in the Subscription keys panel3 votes
There doesn't seem to be a way to programmatically manage knowledge bases. This should be an option outside of using the web-based interface.6 votes
API management added with the V2.0 APIs. See https://qnamaker.ai/Documentation/ApiReference
- Don't see your idea?