Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Description
When creating a cognitive Resource using the AzureRM provider it seems that in order to create the cognitive service resource there is an element of accepting terms. when trying to deploy via terraform it responds with this error:
"ResourceKindRequireAcceptTerms: This subscription cannot create ComputerVision until you agree to Responsible AI terms for this resource. You can agree to Responsible AI terms by creating a resource through the Azure Portal then trying again. For more detail go to https://go.microsoft.com/fwlink/?linkid=216491 "
this seems similar to the license acceptance of marketplace/ legal terms for vms.
As it suggests you can work around by manually creating an instance then removing it but it seems counter intuitive to the whole deploy via code ethos.
potentially you could either pass through the provider block itself given it seems to be slightly outside the actual resource remit)
else perhaps it should just default "accept" the terms in the background when trying to deploy this kind of resource. If deploying a cognitive resource for the first time - its logical you would want to accept the terms, and given it only needs to happen "once" per subscription maybe this is the better option?
Is there an existing issue for this?
Community Note
Description
When creating a cognitive Resource using the AzureRM provider it seems that in order to create the cognitive service resource there is an element of accepting terms. when trying to deploy via terraform it responds with this error:
"ResourceKindRequireAcceptTerms: This subscription cannot create ComputerVision until you agree to Responsible AI terms for this resource. You can agree to Responsible AI terms by creating a resource through the Azure Portal then trying again. For more detail go to https://go.microsoft.com/fwlink/?linkid=216491 "
this seems similar to the license acceptance of marketplace/ legal terms for vms.
As it suggests you can work around by manually creating an instance then removing it but it seems counter intuitive to the whole deploy via code ethos.
potentially you could either pass through the provider block itself given it seems to be slightly outside the actual resource remit)
else perhaps it should just default "accept" the terms in the background when trying to deploy this kind of resource. If deploying a cognitive resource for the first time - its logical you would want to accept the terms, and given it only needs to happen "once" per subscription maybe this is the better option?
New or Affected Resource(s)/Data Source(s)
azurerm_cognitive_account
Potential Terraform Configuration
No response
References
No response