Clarify Azure Translator resource region requirement#6363
Merged
Conversation
Added note about setting the translator resource region to Global to avoid 401 errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added note about setting the translator resource region to Global to avoid 401 errors.
Description
Had a bit of trouble with the lyrics plugin where the translator was not working. Creating a global resource instead of a regional one fixed the issue. Added a small note to the documentation so that people won't run into the same issue in the future.
For a bit more info, you need to specify the region in the request headers if its a regional resource. This is not required for a global one.
To Do
DocumentationChangelogTests