Azure / Azure/azure-rest-api-specs

Azure AI Search REST API does not support UserAssigned Identity (Azure Portal does)

Open
#26,814 2 comments 4 reactions 0 assignees View on GitHub
customer-reported question Search Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
6k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

The current definition of the Azure AI Search service does not support user assigned identities: https://github.com/Azure/azure-rest-api-specs/blob/4ad21c4cd5f024b520b77907b8ac15fb84c8413a/specification/search/resource-manager/Microsoft.Search/stable/2023-11-01/search.json#L2428

The Azure portal allows creation of these identities:

![image](https://github.com/Azure/azure-rest-api-specs/assets/9567895/3a1bfb71-fff1-4867-9ed5-cc52d4f18f9d)

Related terraform issue: https://github.com/hashicorp/terraform-provider-azurerm/issues/19170

Contributor guide

Open the contributing guide

Research direction

Start by inspecting specification/search/resource-manager/Microsoft.Search/stable/2023-11-01/search.json around line 2428 and compare the current identity definition with the user-assigned identities supported by the Azure portal. Check the related Terraform issue for expected behavior; done when the Azure AI Search REST specification represents user-assigned identities.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud, search
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.