Implemented support for Microsoft Translator with Private Endpoints #1117
Conversation
This file contains 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
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.
Hi RWS Team,
I developed a new feature for the MT Enhanced Provider Plugin which allows to configure the Azure Translation using a private endpoint connected to a company network. Using such a private endpoint the data to translate does not need to be send to Azure via the public internet.
In case of any questions, don't hesitate to contact me. At continental we would be very happy if you can merge those changes into the next version and also offer the modified plugin via your store.
Kind Regards,
Daniel