What are the valid kind values for Microsoft.CognitiveServices/accounts?

Question

What are the valid kind values for Microsoft.CognitiveServices/accounts?

Sachdeva, Sonika 40

Hello,

I'm writing Azure Policy rules based on the kind property of Microsoft.CognitiveServices/accounts. Is there an official, up to date list of all valid kind values?

I want to confirm two things:

My list below is complete and current.
AIServices and CognitiveServices are both still valid, separate kinds (not one replacing the other).

My current list: OpenAI, FormRecognizer, SpeechServices, TextAnalytics, ComputerVision, Face, TextTranslation, ContentSafety, AIServices, CognitiveServices.

Thank you,
Sonika

Anshika Varshney 14,870 Reputation points Microsoft External Staff Moderator

2026-07-20T17:07:47.4666667+00:00

Hello @Sachdeva, Sonika

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thankyou!

Answer accepted by question author

0 additional answers

Your answer

Anshika Varshney 14,870 Reputation points Microsoft External Staff Moderator

2026-07-20T17:07:47.4666667+00:00

Hello @Sachdeva, Sonika

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thankyou!

Answer 1

Hello @Sachdeva, Sonika

Thanks for raising this question.

The kind property for Microsoft.CognitiveServices/accounts is intentionally defined as a string, so there is no fixed enum published in the ARM/Bicep schema. The recommended way to retrieve the currently supported kinds is:

az cognitiveservices account list-kinds --query "sort(@)" -o tsv

This returns the provider's current list for your subscription and is a more reliable source than maintaining a static list from documentation.

Regarding your second question, AIServices and CognitiveServices are currently separate and valid kinds. AIServices is used for newer AI Services/Foundry scenarios, while CognitiveServices represents the traditional multi-service Cognitive Services account type.

Also note that a valid kind does not guarantee SKU availability in every region. You can verify regional support by running:

az cognitiveservices account list-skus --kind <kind> --location <region>

Hope this helps. Do let me know if you have any further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thankyou!

Answer 2

The ARM/Bicep reference is not an enum source because kind is intentionally defined as a string. The supported discovery command is:

az cognitiveservices account list-kinds --query "sort(@)" -o tsv

Run it after selecting the target subscription. Treat that output as the current provider list rather than copying a list from documentation. To check whether a valid kind is deployable with a particular regional SKU, also run:

az cognitiveservices account list-skus --kind <kind> --location <region> -o table

A valid kind does not guarantee that every SKU is available in every region or subscription.

Your current list should not be considered exhaustive; older or specialized kinds can remain valid even when they are no longer prominent in the portal. AIServices and CognitiveServices are currently separate kinds. AIServices is used for the newer Foundry resource, including project management. CognitiveServices is the older multi-service account kind; it is not simply an alias replaced by AIServices.

For Azure Policy, scope the rule to Microsoft.CognitiveServices/accounts and evaluate the top-level kind field. Put your approved kinds in a policy parameter, then audit or deny when kind is notIn that array. Refresh the parameter through a reviewed pipeline instead of automatically allowing every newly introduced kind. You can separately inventory deployed values with az resource list, filtered to this resource type, and project each resource's kind.