Forum Discussion

sunil1234's avatar
sunil1234
New Member
1 month ago
Solved

Fabric Data Agent cross workspace warehouse access

created fabric data agent in one workspace A and workspace B having a warehouse or lakehouse i want add warehouse from workspace b in data gent work space a -- but a getting a popup like failed to validate data source

admin
capacities
data hub
governance
one lake
security
workspaces

4 Replies

  • v-saisrao-msft's avatar
    v-saisrao-msft
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi sunil1234​,

    Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.

    Thank you.

  • v-saisrao-msft's avatar
    v-saisrao-msft
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi sunil1234,

    Verify that the user configuring the Data Agent in Workspace A has the required access to the Warehouse/Lakehouse in Workspace B.
    For a Warehouse, ensure the user has Read permission and ReadData/appropriate SQL permissions for the required tables; for a Lakehouse, ensure the required Read access is available. 
    Also verify the Data Agent prerequisites, including F2+ capacity (or P1+ with Fabric enabled) and the applicable cross-geo processing/storing settings for AI. 
    If permissions were recently granted, allow up to two hours for propagation and sign in again before retrying. 
    Then retry adding the Warehouse/Lakehouse as a data source.

    Create a Fabric data agent - Microsoft Fabric | Microsoft Learn

    Configure Fabric data agent tenant settings - Microsoft Fabric | Microsoft Learn

    Share Your Warehouse and Manage Permissions - Microsoft Fabric | Microsoft Learn



    Thank you.

  • ShivekMaharaj's avatar
    ShivekMaharaj
    Icon for Memorable Member rankMemorable Member
    1 month ago

    Hi sunil1234​,

    The permission checks above are worth doing, but there is one other Data Agent limitation I'd check specifically because your source is in a different workspace.

    Microsoft's Fabric Data Agent documentation states that a Data Agent can't execute queries when the data source workspace capacity is in a different region from the Data Agent's workspace capacity.

    So I would compare the capacity region for Workspace A and Workspace B first. For example, Microsoft explicitly documents that a Lakehouse on North Europe capacity can't be queried by a Data Agent whose workspace capacity is in France Central.

    For permissions, the current Data Agent sharing guidance lists the minimum as Read on the Lakehouse item (plus table access where enforced), or Read/SELECT on the relevant Warehouse tables.

    I wouldn't assume the cross-workspace layout itself is the problem, but if the permissions are correct and the two workspaces are backed by capacities in different regions, that is a documented Data Agent limitation and would be the first thing I'd rule out.

    If both workspaces are in the same capacity region, let us know what permissions the user has on the Warehouse/Lakehouse and whether the source appears normally in the OneLake catalog before the validation error.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.