Heidi Steen
Heidi Steen
@vvamaraju All of the supported indexer data sources are documented -- we just don't have one for Azure Synapse. There is a non-indexer approach to indexing however, in the form...
I believe this issue is closed, so I'm going to close the ticket. If you disagree, please feel free to reopen it. #please-close
Hi @webczat, in the "Assign roles" section on step 4, there's a table that lists which roles are needed for different tasks. If you need read permissions, you'll need to...
@webczat, you mentioned that you "enabled trusted service access". Is Azure Storage behind a firewall and in the same region as Search, and did you enable the "Allow trusted Microsoft...
You removed all network protections, but you still can't connect to table storage using a managed identity? That would be a bug. I'll test on my side, but I won't...
Cognitive Search doesn't retrieve the storage account keys, ever. The only time it retrieves keys of any kind are the encryption keys from Azure Key Vault (assuming your using double...
Using the RBAC support in Cognitive Search, you should be able to completely do away with key-based authentication. An alternative to key-based auth was the primary motivation for adding RBAC...
hi @webczat, I can repro the issue and it's a product bug. I'll file a ticket. Sorry for the extended dialogue about unrelated security features. Had I tested it right...
For now, assume that you can't use Azure roles and managed identities for table projections in a knowledge store. I would either avoid table projections for now, or use a...
After the fix, you'll be able to project to tables in a knowledge store using a managed identity. I can't say whether the permissions will continue to be "Reader and...