You are building an Azure Cognitive Search custom skill.

Code Recap (Custom Skill JSON Schema)

{

" @odata.type " : " #Microsoft.Skills.Custom.WebApiSkill " ,

" description " : " My custom skill description " ,

" uri " : " https://contoso-webskill.azurewebsites.net/api/process " ,

" context " : " /document/organizations/* " ,

" inputs " : [

{

" name " : " companyName " ,

" source " : " /document/organizations/* "

}

],

" outputs " : [

{

" name " : " companyDescription "

}

]

}

Statement Analysis

CompanyDescription is available for indexing.

Yes.

The skill produces an output field called companyDescription . Outputs of a custom skill become part of the enrichment tree, which can then be projected into the search index or knowledge store.

The definition calls a web API as part of the enrichment process.

Yes.

This is a Web API skill ( @odata.type: #Microsoft.Skills.Custom.WebApiSkill ) with a uri pointing to https://contoso-webskill.azurewebsites.net/api/process . This means an external web API is called to enrich data.

The enrichment step is called only for the first organization under /document/organizations .

No.

The context is set to " /document/organizations/* " , where the * means the skill runs for each element in the collection. It is not limited to the first element.

Final Answer

CompanyDescription is available for indexing → Yes

The definition calls a web API as part of the enrichment process → Yes

The enrichment step is called only for the first organization under /document/organizations → No

Microsoft References

Custom skills in Azure Cognitive Search

Enrichment tree and skill context