This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 31%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I created a new subscription in order to create a bing search api endpoint. It originally looked OK, but when I went to get the keys to test, they were blank. I tried to regenerate the keys and got "Failed to regenerate the key."
I tried to delete the resource and create a new one. I'm undable to delete it, and get
Error code ResourceCreationValidateFailed
Message. The resource validation failed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 24%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
@MatthewMaker Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
.
Many customers have reported this issue. I am looking into the details internally.
In the meantime, Could you please share the below details over private message ?
Awaiting your reply.
Sent via PM. Thanks for the response!
@MatthewMaker Please note, many customers have reported this issue. Thanks for sharing the details. I am looking into the internal logs and get back to you with an update.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 23%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAY%3C/text%3E%3C/svg%3E)
Is there a solution? I'm unable to create a new Big Search v7 resource too?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 86%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUN%3C/text%3E%3C/svg%3E)
im getting the below error. Also on the status window it says : InternalServerError
{
"status": "Failed",
"error": {
"code": "Suspended",
"message": "Bing resources are suspended for the subscription"
}
}
@Usama Naeem This issue is different than the one reported in this thread. In order to unblock your subscription, you need to open a support ticket with Microsoft.
@navba-MSFT i was originally getting the same issue as everyone before. Now that you told us that the team has implemented the necessary fixes im getting this error after the fix. A week back the api was working fine for me.
@navba-MSFT 1 more update i can manage to see the keys now they are not blank also i can regenerate the keys succesfully but when i try to deploy a new resource i get the error mentioned above. Thanks
@Usama Naeem Yes, your subscription needs to be unblocked for creating new Bing resource which requires a support ticket to be created with Microsoft.
My problem is fixed now for the keys. I haven't tried deleting or redeploying a new one.
@MatthewMaker Thanks for confirmation. Please try creating a new resource or deleting an existing one and check if you encounter the same issue.
@MatthewMaker A quick follow-up to check if you had a chance to look at my above suggestion. Please let me know if you are still facing the same issue.
I seem to be able to create and delete things again as well. I wasn't able to deploy a new search endpoint, but it was because of quota, which makes sense because I already had one in that region. Azure console seems to be working correctly now.
@MatthewMaker Thanks for your reply. For the below answer, Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
@ark yum @MatthewMaker Our Engineering team has implemented the necessary fixes, and we believe the problem has been resolved. Please test this again and let me know if you encounter the issue.
Awaiting your reply.
@MatthewMaker We believe this issue is now resolved. A quick follow-up to check if you are still encountering this issue.
**
For the above answer, Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.