Skip to content

Commit 18563b3

Browse files
authored
copy job permissions
1 parent a6843de commit 18563b3

1 file changed

Lines changed: 49 additions & 0 deletions

File tree

Security/CopyJobPermissions.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Copy Job: Security \& Governance
2+
3+
Costa Rica
4+
5+
[![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/)
6+
[brown9804](https://github.com/brown9804)
7+
8+
Last updated: 2025-05-08
9+
10+
------------------------------------------
11+
12+
13+
> `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.
14+
15+
<details>
16+
<summary><b>List of References</b> (Click to expand)</summary>
17+
18+
</details>
19+
20+
> [!NOTE]
21+
> As now, access to Copy Jobs is controlled `entirely through workspace roles (Admin, Member, Contributor, Viewer).`
22+
> `There is no support for assigning permissions to individual Copy Jobs` or managing them through SQL-like GRANT, REVOKE, or DENY statements.
23+
24+
<div align="center">
25+
<img width="700" alt="image" src="https://github.com/user-attachments/assets/6f7d1d11-733a-492f-b63e-0da371908e35" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
26+
</div>
27+
28+
> [!IMPORTANT]
29+
> `Workspace roles in Microsoft Fabric (Admin, Member, Contributor, Viewer) grant access to all items within the workspace, not just Copy Jobs.` This includes Dashboards,
30+
> 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.
31+
32+
| **Workspace Role** | **Access to Copy Jobs** |
33+
|--------------------|------------------------------------------------------------------------------------------|
34+
| **Admin** | Full control: create, edit, delete, monitor, and manage permissions for Copy Jobs. |
35+
| **Member** | Can create, edit, and run Copy Jobs; can also share them with others. |
36+
| **Contributor** | Can create and run Copy Jobs, but cannot manage permissions or share them. |
37+
| **Viewer** | Can view Copy Jobs and their status but cannot create, edit, or run them. |
38+
39+
40+
<img width="700" alt="image" src="https://github.com/user-attachments/assets/93ccd9f1-a650-4663-a631-3b2b20434cae" />
41+
42+
<img width="700" alt="image" src="https://github.com/user-attachments/assets/ce0bcfe1-cce2-45e9-81ee-c58e89a7f089" />
43+
44+
<img width="500" alt="image" src="https://github.com/user-attachments/assets/097cb406-b4c8-4d49-88c2-6d4ea8cf7294" />
45+
46+
<div align="center">
47+
<h3 style="color: #4CAF50;">Total Visitors</h3>
48+
<img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
49+
</div>

0 commit comments

Comments
 (0)