Skip to content

Latest commit

 

History

History
52 lines (36 loc) · 3.17 KB

File metadata and controls

52 lines (36 loc) · 3.17 KB

Copy Job: Security & Governance

Costa Rica

GitHub brown9804

Last updated: 2025-05-08


Copy Job in Microsoft Fabric is a data movement operation that enables users to transfer data from one location to another within the Fabric ecosystem or from external sources. It supports a wide range of connectors and formats, allowing seamless ingestion into OneLake, Data Warehouses, or Lakehouses. Copy Jobs are ideal for ETL/ELT workflows, data onboarding, and integration scenarios, providing a scalable and efficient way to automate data loading and refresh processes across environments.

List of References (Click to expand)

Note

As now, access to Copy Jobs is controlled entirely through workspace roles (Admin, Member, Contributor, Viewer). There is no support for assigning permissions to individual Copy Jobs or managing them through SQL-like GRANT, REVOKE, or DENY statements.

image

Important

Workspace roles in Microsoft Fabric (Admin, Member, Contributor, Viewer) grant access to all items within the workspace, not just Copy Jobs. This includes Dashboards, Semantic Models, Data Warehouses, Notebooks, Pipelines, and more. There is currently no way to assign permissions to Copy Jobs individually, access is inherited from the user's role in the workspace.

Workspace Role Access to Copy Jobs
Admin Full control: create, edit, delete, monitor, and manage permissions for Copy Jobs.
Member Can create, edit, and run Copy Jobs; can also share them with others.
Contributor Can create and run Copy Jobs, but cannot manage permissions or share them.
Viewer Can view Copy Jobs and their status but cannot create, edit, or run them.
image image image
Total views

Refresh Date: 2025-08-06