You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-blob-dotnet-get-started.md
+24-26Lines changed: 24 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,8 +61,6 @@ To learn more about creating and managing client objects, see [Create and manage
61
61
62
62
You can authorize a `BlobServiceClient` object by using an Azure Active Directory (Azure AD) authorization token, an account access key, or a shared access signature (SAS).
63
63
64
-
To learn more about each of these authorization mechanisms, see [Authorize access to data in Azure Storage](../common/authorize-data-access.md).
65
-
66
64
## [Azure AD](#tab/azure-ad)
67
65
68
66
To authorize with Azure AD, you'll need to use a security principal. The type of security principal you need depends on where your application runs. Use this table as a guide.
@@ -93,6 +91,28 @@ public static void GetBlobServiceClient(ref BlobServiceClient blobServiceClient,
93
91
94
92
If you know exactly which credential type you'll use to authenticate users, you can obtain an OAuth token by using other classes in the [Azure Identity client library for .NET](/dotnet/api/overview/azure/identity-readme). These classes derive from the [TokenCredential](/dotnet/api/azure.core.tokencredential) class.
95
93
94
+
## [SAS token](#tab/sas-token)
95
+
96
+
Create a [Uri](/dotnet/api/system.uri) by using the blob service endpoint and SAS token. Then, create a [BlobServiceClient](/dotnet/api/azure.storage.blobs.blobserviceclient) by using the [Uri](/dotnet/api/system.uri).
To learn more about generating and managing SAS tokens, see the following articles:
110
+
111
+
-[Grant limited access to Azure Storage resources using shared access signatures (SAS)](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json)
112
+
-[Create an account SAS with .NET](../common/storage-account-sas-create-dotnet.md)
113
+
-[Create a service SAS for a container or blob](sas-service-create.md)
114
+
-[Create a user delegation SAS for a container, directory, or blob with .NET](storage-blob-user-delegation-sas-create-dotnet.md)
115
+
96
116
## [Account key](#tab/account-key)
97
117
98
118
Create a [StorageSharedKeyCredential](/dotnet/api/azure.storage.storagesharedkeycredential) by using the storage account name and account key. Then use that object to initialize a [BlobServiceClient](/dotnet/api/azure.storage.blobs.blobserviceclient).
@@ -119,30 +139,8 @@ BlobServiceClient blobServiceClient = new BlobServiceClient(connectionString);
119
139
120
140
For information about how to obtain account keys and best practice guidelines for properly managing and safeguarding your keys, see [Manage storage account access keys](../common/storage-account-keys-manage.md).
121
141
122
-
## [SAS token](#tab/sas-token)
123
-
124
-
Create a [Uri](/dotnet/api/system.uri) by using the blob service endpoint and SAS token. Then, create a [BlobServiceClient](/dotnet/api/azure.storage.blobs.blobserviceclient) by using the [Uri](/dotnet/api/system.uri).
To generate and manage SAS tokens, see any of these articles:
138
-
139
-
-[Grant limited access to Azure Storage resources using shared access signatures (SAS)](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json)
140
-
141
-
-[Create an account SAS with .NET](../common/storage-account-sas-create-dotnet.md)
142
-
143
-
-[Create a service SAS for a container or blob](sas-service-create.md)
144
-
145
-
-[Create a user delegation SAS for a container, directory, or blob with .NET](storage-blob-user-delegation-sas-create-dotnet.md)
142
+
> [!IMPORTANT]
143
+
> The account access key should be used with caution. If your account access key is lost or accidentally placed in an insecure location, your service may become vulnerable. Anyone who has the access key is able to authorize requests against the storage account, and effectively has access to all the data. `DefaultAzureCredential` provides enhanced security features and benefits and is the recommended approach for managing authorization to Azure services.
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-blob-java-get-started.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,8 +87,6 @@ To learn more about creating and managing client objects, see [Create and manage
87
87
88
88
You can authorize a `BlobServiceClient` object by using an Azure Active Directory (Azure AD) authorization token, an account access key, or a shared access signature (SAS).
89
89
90
-
To learn more about each of these authorization mechanisms, see [Authorize access to data in Azure Storage](../common/authorize-data-access.md).
91
-
92
90
## [Azure AD (Recommended)](#tab/azure-ad)
93
91
94
92
To authorize with Azure AD, you'll need to use a [security principal](../../active-directory/develop/app-objects-and-service-principals.md). Which type of security principal you need depends on where your application runs. Use the following table as a guide:
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-blob-python-get-started.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,8 +53,6 @@ To learn more about creating and managing client objects, see [Create and manage
53
53
54
54
You can authorize a `BlobServiceClient` object by using an Azure Active Directory (Azure AD) authorization token, an account access key, or a shared access signature (SAS).
55
55
56
-
To learn more about each of these authorization mechanisms, see [Authorize access to data in Azure Storage](../common/authorize-data-access.md).
57
-
58
56
## [Azure AD](#tab/azure-ad)
59
57
60
58
To authorize with Azure AD, you'll need to use a [security principal](/azure/active-directory/develop/app-objects-and-service-principals). Which type of security principal you need depends on where your application runs. Use the following table as a guide:
@@ -74,6 +72,16 @@ The following example creates a `BlobServiceClient` object using `DefaultAzureCr
To use a shared access signature (SAS) token, provide the token as a string and initialize a [BlobServiceClient](/python/api/azure-storage-blob/azure.storage.blob.blobserviceclient) object. If your account URL includes the SAS token, omit the credential parameter.
To learn more about generating and managing SAS tokens, see the following article:
82
+
83
+
-[Grant limited access to Azure Storage resources using shared access signatures (SAS)](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json)
84
+
77
85
## [Account key](#tab/account-key)
78
86
79
87
To use a storage account shared key, provide the key as a string and initialize a [BlobServiceClient](/python/api/azure-storage-blob/azure.storage.blob.blobserviceclient) object.
@@ -86,13 +94,8 @@ You can also create a `BlobServiceClient` object using a connection string.
86
94
87
95
For information about how to obtain account keys and best practice guidelines for properly managing and safeguarding your keys, see [Manage storage account access keys](../common/storage-account-keys-manage.md).
88
96
89
-
## [SAS token](#tab/sas-token)
90
-
91
-
To use a shared access signature (SAS) token, provide the token as a string and initialize a [BlobServiceClient](/python/api/azure-storage-blob/azure.storage.blob.blobserviceclient) object. If your account URL includes the SAS token, omit the credential parameter.
To generate and manage SAS tokens, see [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json).
97
+
> [!IMPORTANT]
98
+
> The account access key should be used with caution. If your account access key is lost or accidentally placed in an insecure location, your service may become vulnerable. Anyone who has the access key is able to authorize requests against the storage account, and effectively has access to all the data. `DefaultAzureCredential` provides enhanced security features and benefits and is the recommended approach for managing authorization to Azure services.
0 commit comments