Azure-docs: confusing for the qna subscriptionKey

[xtianus79]

The way you assume the key for the qna authorization is from the EndpointKey but that is incorrect it is the service key... clearly documentation would help that

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2f497268-0c29-4346-b9e9-3a037a13e3d5
• Version Independent ID: e6c64346-6e47-36bb-ef2a-9d6609805377
• Content: Tutorial: Composite entity tutorial - LUIS - Azure Cognitive Services
• Content Source: articles/cognitive-services/LUIS/luis-tutorial-composite-entity.md
• Service: cognitive-services
• Sub-service: language-understanding
• GitHub Login: @diberry
• Microsoft Alias: diberry

[diberry]

@xtianus79 - did you mean to log this issue against the composite tutorial? #in-progress

[YutongTie-MSFT]

@diberry Hi Dina, yes. I believe there are some customers who are confused about different keys for service. Would you like to add more details about it? Thanks.

[diberry]

@YutongTie-MSFT @xtianus79 The tutorial this issue is on/about doesn't use the QnA Maker subscriptionkey - that I know of. That is what I'm confused about.

[xtianus79]

@diberry and @YutongTie-MSFT there are service level keys and keys that appear in the the portals that have a little bit of confusion to which key is being referred to in the documentation. For example in the portal and in the documentation for the QNA maker it refers to an endpoint key but it wants the key from the service and not the portal.

The api checker for the azure service is really good and helps find all the right keys so that is a good place to check but it is confusing when using the wrong key and you get an unhelpful error responding.

[diberry]

@xtianus79 What is the api checker?

[xtianus79]

When you create a service in azure in the > quick start section -> step 2 you have this information about your api

Make an API call to this endpoint: https://xxxxxx.cognitiveservices.azure.com/qnamaker/v4.0
Get in-depth information about the properties and methods of the API. Test your keys with the built-in testing console without writing a single line of code. Once you have the API running, you can check your consumption and the API health on Azure portal in your API 'Overview'.

with a link to here below
API reference:

which takes you to this dev service form Azure.
https://westus.dev.cognitive.microsoft.com/docs/services

It lists out the api reference which provides the reference and definition for the version.

Here it is in snips

[diberry]

@xtianus79 This is referred to as the APIM internally because that is the service hosting the API docs. The official reference documentation is implementing the same functionality - not sure when that will be released. I'm closing this issue since the work is actually taking place on the bot framework public issue. #please-close