We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using the cognitive services provider (https://marketplace.upbound.io/providers/upbound/provider-azure-cognitiveservices/v1.9.0) to create the azure openai deployments for difererent large language models (like gpt-35-turbo , gpt-4) . for all this deployment i also need to attach a certain level of filters of content like Hate and Fairness, Sexual, Violenence. more details here : https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/content-filter.
currently the cognitive services provider do not support creating of content filter.
Addition of content filter module to cognitive services provider so that we can attach it to the deployments created.
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
No branches or pull requests
Unable to create content filter for azure openai models.
I am using the cognitive services provider (https://marketplace.upbound.io/providers/upbound/provider-azure-cognitiveservices/v1.9.0) to create the azure openai deployments for difererent large language models (like gpt-35-turbo , gpt-4) . for all this deployment i also need to attach a certain level of filters of content like Hate and Fairness, Sexual, Violenence. more details here : https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/content-filter.
currently the cognitive services provider do not support creating of content filter.
What could help solve your problem?
Addition of content filter module to cognitive services provider so that we can attach it to the deployments created.
The text was updated successfully, but these errors were encountered: