Document Azure API key usage for Azure Document Intelligence conversion#1559
Open
kei-yamazaki wants to merge 1 commit intomicrosoft:mainfrom
Open
Document Azure API key usage for Azure Document Intelligence conversion#1559kei-yamazaki wants to merge 1 commit intomicrosoft:mainfrom
kei-yamazaki wants to merge 1 commit intomicrosoft:mainfrom
Conversation
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
1 participant
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.
Summary
This PR updates the documentation for Azure Document Intelligence conversion to clarify that users can provide credentials via the
AZURE_API_KEYenvironment variable.Changes
README.mdshowing how to setAZURE_API_KEYWhy
AZURE_API_KEYsupport already exists inmain, but the README did not clearly describe how to use it for Document Intelligence conversion. This change makes the setup path more discoverable for users.Impact