What causes WorkspaceNotFound?

An incorrect or stale workspace object ID (GUID) hardcoded in API calls, scripts, or pipeline configurations. The target workspace was deleted or moved after the ID was recorded. The calling service principal or user account does not have access to the workspace, causing it to appear nonexistent. Workspace ID copied from a URL or UI element that referenced a different environment (e.g., dev vs. prod tenant)

How do I fix WorkspaceNotFound?

Step 1: Retrieve the correct workspace object ID by navigating to the workspace in the Fabric portal and copying the GUID from the URL, or by calling the List Workspaces API (/v1/workspaces) with a valid authenticated identity.. Step 2: Verify the workspace still exists in the Fabric portal under the correct tenant — confirm it has not been deleted or moved to a different capacity.. Step 3: Check that the identity making the API call (user or service principal) has at least Member or Contributor access to the workspace; lack of permissions causes a 404 rather than a 403 in some Fabric API contexts.. Step 4: Update all hardcoded workspace IDs in pipeline configurations, notebooks, or application settings to the verified correct value.. Step 5: If operating across multiple tenants or environments, confirm the API call is being made against the correct Fabric tenant endpoint and that the workspace exists in that specific tenant.

High severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
WorkspaceNotFound

What does this error mean?

A Fabric REST API call returned a 404 Not Found response because the specified workspace object ID does not exist or is not accessible to the calling identity. The workspace may have been deleted, renamed, or the ID may be incorrect.

Common causes

1An incorrect or stale workspace object ID (GUID) hardcoded in API calls, scripts, or pipeline configurations
2The target workspace was deleted or moved after the ID was recorded
3The calling service principal or user account does not have access to the workspace, causing it to appear nonexistent
4Workspace ID copied from a URL or UI element that referenced a different environment (e.g., dev vs. prod tenant)

How to fix it

1Step 1: Retrieve the correct workspace object ID by navigating to the workspace in the Fabric portal and copying the GUID from the URL, or by calling the List Workspaces API (/v1/workspaces) with a valid authenticated identity.
2Step 2: Verify the workspace still exists in the Fabric portal under the correct tenant — confirm it has not been deleted or moved to a different capacity.
3Step 3: Check that the identity making the API call (user or service principal) has at least Member or Contributor access to the workspace; lack of permissions causes a 404 rather than a 403 in some Fabric API contexts.
4Step 4: Update all hardcoded workspace IDs in pipeline configurations, notebooks, or application settings to the verified correct value.
5Step 5: If operating across multiple tenants or environments, confirm the API call is being made against the correct Fabric tenant endpoint and that the workspace exists in that specific tenant.

Frequently asked questions

Why does Fabric return 404 instead of 403 when I don't have access to a workspace?

This is a deliberate security behavior — the API does not reveal whether a resource exists to callers who lack access, returning 404 to prevent enumeration of workspace IDs. If you suspect a permissions issue rather than a missing workspace, confirm access in the Fabric portal while logged in as the relevant identity.

How do I find all workspace IDs in my tenant programmatically?

Call the GET /v1/workspaces endpoint with a tenant admin token or a service principal that has been granted tenant-wide workspace access. This returns a paginated list of all workspaces and their object IDs that the calling identity can see.