@Rishabh Kumar (XRISKazadm) I think the error that is caused in this case is because of the bing search resource that is used for this call. Bing resources migrated from cognitive services to bing in october 2020 and if you are using a key of the instance that is created previously such error could be seen. You can try to create a new custom search resource by using the issue paid key option from the screen shot or try out a free trial key if you are eligible. Trying out a new key worked for me because my older resources of bing were under a different pricing plan as the resources were created under cognitive services namespace.