Unable to save cognitiveServices key in AI Search skillset

John M 0 Reputation points

I created an "Azure AI services multi-service account" to attach to my AI Search skillset to move to pay-per-use and avoid the 20 document per day limit. When I try to add it to the skillset, it seems like the save works, but the key does not actually save.

When I first go to the skillset, it looks like this

  "cognitiveServices": {
    "@odata.type": "#Microsoft.Azure.Search.CognitiveServicesByKey",
    "description": "-clipped-",
    "key": null

If I click "Connect AI Service", I see the "multi-service account". I can also manually enter the key in the JSON

User's image

Either way, the resulting JSON will be:

  "cognitiveServices": {
    "@odata.type": "#Microsoft.Azure.Search.CognitiveServicesByKey",
    "key": "f676-changed-e705"

Clicking save on the skillset results in a "success", but the save does not really happen. Clicking refresh will return "key" to null.

Any idea what would cause this or how to get it to save?

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
757 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 19,301 Reputation points Microsoft Employee

    @John M Thanks for your patience on this.

    I have checked with Azure Cognitive Service engineering team and sharing the below.

    The key will be stored in the backend and will only be used by the indexer. It is not displayed for security reasons.

    Additionally, if you attempt to retrieve the skillset details using the (Get Skillset) REST API, no keys will be returned in any GET calls to address a security vulnerability.

    This behavior is documented in the API versions of Search REST APIs on the Azure AI Search | Microsoft Learn website.

    Hope this helps, let me know if you have any further questions on this.

    1 person found this answer helpful.