StorageSharedKeyCredential are required when creating serviceClient #34
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.
The Referenced article https://docs.microsoft.com/en-us/azure/storage/blobs/storage-secure-access-application highlights that the access should be Private-Access only.
However, when the ServiceClient in the StorageHelper.GetThumbNailUrls() tries to access the ServiceClient/Container Name, the Exists() call fails with ResourceNotFound errors.
The StorageSharedKeyCredential are required when creating the BLOBServiceURI based ServiceClient in case the Container has Private Access Only enabled.
Submitting the fixes for the problem experienced when enabling SASToken based authentication in the Thumbnail URLs.