search

Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.47k stars 4.8k forks source link

Spell check endpoint Invalid for Bing Search #33588

Open VarunSaiTeja opened 1 year ago

VarunSaiTeja commented 1 year ago

Library name and version

Microsoft.Azure.CognitiveServices.Language.SpellCheck 4.0.0

Describe the bug

The new endpoint for spell check is https://api.bing.microsoft.com/v7.0/spellcheck But the library referring to https://api.cognitive.microsoft.com/bing/v7.0/spellcheck

The class SpellCheckClient has the property Endpointconfigurable, but the URL path bing can't be removed. Please provide a solution to solve the problem or update the package with the correct endpoint.

Expected behavior

Endpoint should point to https://api.bing.microsoft.com/v7.0/spellcheck

Actual behavior

Endpoint pointing to https://api.cognitive.microsoft.com/bing/v7.0/spellcheck

Reproduction Steps

Create a Azure resource of type Bing Search v7

Create a c# console app with the following code, and replace the subscription key with the one provided by the azure resource. var _spellCheckClient = new SpellCheckClient(new ApiKeyServiceClientCredentials("<<Subscription Key>>"));

Run the app, the instance won't be created, it will be through an UnAuthorized Exception.

Environment

No response

ghost commented 1 year ago

Thank you for your feedback. This has been routed to the support team for assistance.

SaurabhSharma-MSFT commented 1 year ago

@VarunSaiTeja We are looking into it and get back to you for any additional information.

SaurabhSharma-MSFT commented 1 year ago

@VarunSaiTeja The SDK needs an update to support the new common URL. Product team is internally working to address this issue and using the REST API would be the way to go in the meantime.

github-actions[bot] commented 1 year ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jaggerbodas-ms @arwong.