How to set up Azure storage container for a 3rd party vendor using external Azure ID

Question

1. We set up an Azure storage container
2. Added 3rd party user to an active directory group: Invitation status: accepted. Active state: enabled
3. Provided the active directory group blob reader and contributor access to the container.

But still the 3rd party user is unable to see the container on his side.

Kindly assist

Answer 1

@Galagali, Piyusha

If you've set up an Azure storage container, added a 3rd party user to an Active Directory group with accepted invitation status and enabled active state, and provided the Active Directory group with Storage blob data reader and Storage blob data contributor access to the container, but the 3rd party user is still unable to see the container,

there could be below several reasons for this issue. Here are some troubleshooting steps to assist you:

1. Check Permissions: Verify that the permissions have been correctly applied to the Azure storage container. Ensure that the Active Directory group you added the 3rd party user to indeed has the necessary access (blob reader and contributor) to the container. Double-check the permissions at both the Storage level and container level.
2. User's Role in Azure: Confirm that the 3rd party user has the correct role assignments in Azure. They should be a member of the Active Directory group that was granted permissions to the Storage account and container. Also, make sure that there are no conflicting permissions that might deny access.
3. Token and Authentication: Ensure that the 3rd party user is using the correct authentication method to access the container. If the user is using a shared access signature (SAS), verify that the SAS token is valid and has the required permissions. If they are using Azure AD authentication, check that their authentication token is valid and hasn't expired.
4. Network or Firewall Issues: Check if there are any network or firewall restrictions that might be blocking the user's access to Azure services. Ensure that the user's network allows outbound traffic to Azure services.
5. Browser Cache: If the user is accessing Azure resources through a web browser, suggest clearing their browser cache and trying again. Sometimes, cached data can cause issues.
6. Error Messages: Ask the 3rd party user to provide any error messages or details they encounter when attempting to access the container. These error messages can often provide clues about the issue.

By following these troubleshooting steps and ensuring that permissions, authentication, and network configurations are correct, you should be able to resolve the issue and allow the 3rd party user to access the Azure storage container.

Kindly let us know if the above helps or if you still have issues, please let us we would be happy to assist you.