In this informative and slightly humorous video, Zane Goodman from Pragmatic Works walks viewers through the process of taking over workloads in Microsoft Fabric when an employee leaves unexpectedly. Through a mock scenario involving a character named “Mr. Bad Man,” Zane highlights the importance of having the right permissions and understanding key features in Fabric to ensure business continuity.
Understanding the Scenario
The video begins with a lighthearted dramatization to highlight a serious issue: what happens when an employee exits the company abruptly without handing over their work? Zane uses this premise to demonstrate how administrators and team members can reclaim ownership of workloads and projects built within Microsoft Fabric.
Step 1: Gain Admin Access
- Before anything else, ensure that you have admin, contributor, or member access to the workspace previously managed by the employee.
- This is necessary to access and modify the items within that workspace.
Step 2: Locate the Workspace
- Navigate to the specific workspace from the Fabric home screen.
- In the example, Zane accesses a workspace humorously renamed “take over Zayn’s sanity.”
Step 3: Understand the Workflow Components
The demo project includes the following components:
- Warehouse: Contains control tables with a last modified date field.
- Stored Procedure: Returns the last modified date to determine update necessity.
- Data Pipeline: Uses the stored procedure result to conditionally trigger a notebook.
- Notebook: Executes a PySpark job to pull new data into a lakehouse if updates are needed.
- Lakehouse: Stores the resulting data.
Step 4: Take Over Individual Items
Zane explains how to transfer ownership of specific Fabric items by following these steps:
- Hover over the item (e.g., warehouse, pipeline, notebook) and select Settings.
- Go to the About tab and click Take Over.
- Confirm the change to begin using your credentials for the item’s data sources.
Step 5: Address Pipeline Nuances
- After taking over a pipeline, update the Last Modified field to reflect your user ID by making a simple change (e.g., adding a letter to the name and removing it).
- Check all references within the pipeline to ensure you have access to data sources like the warehouse or external connectors.
- If you lack access, re-authentication may be required to restore functionality.
Step 6: Don’t Forget Nested Items
Taking over a pipeline does not automatically transfer ownership of items used within it, such as notebooks. These need to be taken over manually using the same method (Settings → About → Take Over).
Other Considerations
- Scheduled runs associated with pipelines remain active after takeover, but it's recommended to double-check them.
- New support in Fabric allows taking over User Data Functions as well.
Learn More with Pragmatic Works
For those interested in deeper learning, Zane recommends the PySpark in Fabric Notebooks course available on Pragmatic Works’ On-Demand Learning Platform. Also, explore the Fabric Analyst in a Day course to further enhance your knowledge and practical skills.
Don't forget to check out the Pragmatic Works' on-demand learning platform for more insightful content and training sessions on Fabric and other Microsoft applications. Be sure to subscribe to the Pragmatic Works YouTube channel to stay up-to-date on the latest tips and tricks.