MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.2k stars 21.35k forks source link

Bing custom search docs on for recovering service? #117429

Closed S3j5b0 closed 9 months ago

S3j5b0 commented 9 months ago

Hi,

I have a website with some searching that was provided by a azure service of the type "Azure AI service". The search basically worked by calling an endpoint on the service that looked like this:

image All of the sudden, the search started returning 404, with no apparent info on why, or if the health of the service is bad.

I find other people asking similar questions on this forum, where there is linked this https://azure.microsoft.com/en-ca/updates/bing-search-apis-will-transition-from-azure-cognitive-services-to-azure-marketplace-on-31-october-2023/

Here it basically hints that I should migrate the resource to azure marketplace, and then links to a tutorial about how to create a new service.

But, it is incredibly unclear to me how I should set up my new service in accordance with the old one. That it points to the same site, searches up the same kinds of results etc.

For instance, I can find virtually no info on how I set up this new service to point at the same site. Currently I'm considering moving to google search, since the path forward seems so unclear to me

Can someone help me with how to look for it?


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Azure documentation issue guidance

Thanks for opening an issue in the Azure technical documentation repository.

We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.

Creating an issue

We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.

You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

Pull requests and article contributions

If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

We'll route the issue to the appropriate content team for review and discussion.

Tech support and product feedback

If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

AjayBathini-MSFT commented 9 months ago

@S3j5b0

Thanks for posting your question! Can you please confirm if your issue is related to a document that you are following and want to point out an issue in the document or share feedback to a document to avoid such failures you have reported? In this case could you provide the URL of the specific documentation that your feedback is applicable to? That way, we can make sure your feedback is addressed by the right team and it can help others who are looking for help on similar topics.

AjayBathini-MSFT commented 9 months ago

@S3j5b0 Thank you for your feedback! I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds. [Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.