Problems with accessing an existing DataShare

@Kerry Glewwe

It sounds like you're encountering issues when trying to update mapped items in an existing DataShare, particularly after adding additional tables. The error message "Could not retrieve shared datasets at the moment. Please try again later." typically suggests a temporary access or synchronization issue with the shared datasets.

Since recreating the DataShare and re-inviting resolved the issue temporarily before, it's possible that similar underlying conditions have reoccurred. To help troubleshoot further, please consider the following steps:

Check Permissions - Ensure you have the appropriate permissions on the Azure Data Share and the underlying data sources. Typically, roles like Contributor or Owner are required, and the sender must ensure that newly added tables are correctly shared with the necessary permissions.

Review Mapping Configuration - Double-check the configuration for the newly added tables. Make sure all mappings are correct, and the datasets are valid and accessible.

Wait and Retry - Sometimes updates, especially after adding new tables, can take a few minutes to propagate. It's worth waiting a bit and then trying again.

Refresh the Portal - Refresh the Azure portal or try signing out and back in, as session-related issues can sometimes affect visibility or access to shared resources.

Validate Linked Services and Resource Availability - Ensure that the linked services (e.g., for Azure Data Explorer or other sources) are active and correctly configured. Also, make sure that the source cluster is running (not paused) and that there are no compatibility issues (e.g., sharing between EngineV2 and EngineV3 clusters is not supported).

For more details refer: Troubleshoot common problems in Azure Data Share

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

@Kerry Glewwe We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Hi Kerry,

Thank you for reaching out and sharing your question on the Q&A portal.

The error message "Could not retrieve shared datasets at the moment. Please try again later" can happen for a few reasons. One common cause is temporary service interruptions, but since you mentioned it happened again after adding more tables, it might be related to permissions or synchronization delays.

First, I’d recommend checking if the sender’s permissions are correctly set up for the new tables. The sender needs Microsoft.Authorization/roleAssignments/write permissions to share data properly, as mentioned in the Microsoft documentation on Azure Data Share roles. Sometimes, adding new tables can reset or require reconfiguration of these permissions.

Another thing to look at is whether the Data Share service is experiencing any regional outages. You can check the Azure Status page to see if there are any ongoing issues. If everything looks good there, try refreshing the share or waiting a bit before retrying—sometimes sync delays can cause this error.

If the problem persists, you might want to review the share’s snapshot schedule or trigger a manual sync.

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment
https://ctrlaltdel.blog/

@Kerry Glewwe - Following up to see if the above suggestions were helpful. And, if you have any further query do let us know.

Hello @Kerry Glewwe,
In genral To allow the Azure Data Share resource’s managed identity to access a database, several permissions and steps are required:

Set yourself as the Azure Active Directory (AAD) Admin.

Once you're the AAD Admin, connect to the Azure SQL Database using SSMS with Azure AD authentication.

Then, grant db_datareader permission to the Azure Data Share’s resource-managed identity.

Make sure you’re assigning the permission to the correct managed identity associated with the Data Share resource.