|
| 1 | +# Event Stream: Security \& Governance |
| 2 | + |
| 3 | +Costa Rica |
| 4 | + |
| 5 | +[](https://github.com/) |
| 6 | +[brown9804](https://github.com/brown9804) |
| 7 | + |
| 8 | +Last updated: 2025-05-08 |
| 9 | + |
| 10 | +------------------------------------------ |
| 11 | + |
| 12 | +> `Event Stream` in Microsoft Fabric is a `real-time data ingestion and processing service` that enables users to capture, transform, and route streaming data from various sources. It supports inputs like `Event Hubs`, `IoT devices`, and `custom applications`, and allows routing data to destinations such as `OneLake`, `Data Warehouses`, or `Lakehouses`. Event Streams are ideal for `real-time analytics, monitoring, and alerting scenarios`, providing a scalable and low-latency pipeline for continuously processing and reacting to incoming data events. |
| 13 | +
|
| 14 | +<details> |
| 15 | +<summary><b>List of References</b> (Click to expand)</summary> |
| 16 | + |
| 17 | +- [Fabric Eventstream - overview](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/overview?tabs=enhancedcapabilities) |
| 18 | +- [Manage an eventstream in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/manage-eventstream) |
| 19 | + |
| 20 | +</details> |
| 21 | + |
| 22 | +> [!NOTE] |
| 23 | +> As now, access to Event Stream is controlled `entirely through workspace roles (Admin, Member, Contributor, Viewer).` |
| 24 | +> `There is no support for assigning permissions to individual Event Stream` or managing them through SQL-like GRANT, REVOKE, or DENY statements. |
| 25 | +
|
| 26 | +<div align="center"> |
| 27 | + <img width="700" alt="image" src="https://github.com/user-attachments/assets/66b7a6ec-12fb-4f22-af45-fd481caa3f30" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/> |
| 28 | +</div> |
| 29 | + |
| 30 | +<div align="center"> |
| 31 | + <img width="700" alt="image" src="https://github.com/user-attachments/assets/1f88430b-8caa-438a-88d8-9675ae461af7" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/> |
| 32 | +</div> |
| 33 | + |
| 34 | +> [!IMPORTANT] |
| 35 | +> `Workspace roles in Microsoft Fabric (Admin, Member, Contributor, Viewer) grant access to all items within the workspace, not just Event Stream.` This includes Dashboards, |
| 36 | +> Semantic Models, Data Warehouses, Notebooks, Pipelines, and more. There is currently no way to assign permissions to Event Stream individually, access is inherited from the user's role in the workspace. |
| 37 | +
|
| 38 | +| **Workspace Role** | **Access to Event Stream** | |
| 39 | +|--------------------|------------------------------------------------------------------------------------------| |
| 40 | +| **Admin** | Full control: create, edit, delete, monitor, and manage permissions for Event Stream. | |
| 41 | +| **Member** | Can create, edit, and run Event Stream; can also share them with others. | |
| 42 | +| **Contributor** | Can create and run Event Stream, but cannot manage permissions or share them. | |
| 43 | +| **Viewer** | Can view Event Stream and their status but cannot create, edit, or run them. | |
| 44 | + |
| 45 | +<img width="700" alt="image" src="https://github.com/user-attachments/assets/93ccd9f1-a650-4663-a631-3b2b20434cae" /> |
| 46 | + |
| 47 | +<img width="700" alt="image" src="https://github.com/user-attachments/assets/ce0bcfe1-cce2-45e9-81ee-c58e89a7f089" /> |
| 48 | + |
| 49 | +<img width="500" alt="image" src="https://github.com/user-attachments/assets/097cb406-b4c8-4d49-88c2-6d4ea8cf7294" /> |
| 50 | + |
| 51 | +<div align="center"> |
| 52 | + <h3 style="color: #4CAF50;">Total Visitors</h3> |
| 53 | + <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/> |
| 54 | +</div> |
0 commit comments