Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update generate-sas-tokens.md #81494

Closed
wants to merge 1 commit into from
Closed

Update generate-sas-tokens.md #81494

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/applied-ai-services/form-recognizer/generate-sas-tokens.md
View file
Open in desktop
Expand Up @@ -13,7 +13,7 @@ recommendations: false

# Generate SAS tokens for storage containers

In this article, you'll learn how to generate user delegation shared access signature (SAS) tokens. A user delegation SAS token is signed with Azure Active Directory (Azure AD) credentials instead of Azure storage keys. It provides superior secure and delegated access to resources in your Azure storage account.
In this article, you'll learn how to generate user delegation shared access signature (SAS) tokens for Azure Blob Storage containers. A user delegation SAS token is signed with Azure Active Directory (Azure AD) credentials instead of Azure storage keys. It provides superior secure and delegated access to resources in your Azure storage account.
At a high level, here's how it works: your application provides the SAS token to Azure storage as part of a request. If the storage service verifies that the SAS is valid, the request is authorized. If the SAS is deemed invalid, the request is declined with error code 403 (Forbidden).

Azure blob storage offers three types of resources:
Expand Down