Before the account is closed, list everything that runs under that person’s name. Move each item to an account that will stay.
You may have inherited the jobs and pipelines, the database, the gateway, and the reports without knowing where the data comes from or what keeps it current. A semantic model, SQL Server Agent job, pipeline, stored file, or saved credential may still depend on the person who ran it.
In the first week, keep everything running, keep access, and write down what you find. A redesign can wait. Work through the checks below with whoever manages your Microsoft accounts, Power BI, servers, and laptops.
What breaks when the account closes
SQL Server Agent jobs, SSIS packages, and scripts
SQL Server Agent jobs may run SSIS packages and scripts. A job can also be owned by an individual login. If that account is disabled or removed, the job may fail with an error saying it is unable to determine whether the owner has server access.
Open each job’s Properties in SQL Server Management Studio and change the owner to a login that does not belong to a person. That may be an approved service account or sa, based on the way your server is managed. Brent Ozar’s check for jobs owned by user accounts shows the error and the ownership change.
Credentials and SQL Server Agent proxies can also be set up with the person’s own login. Job steps that run through such a proxy fail when that login stops working. Check database ownership too. A database created without an explicit owner is owned by the login that created it.
Cláudio Silva’s SQL Server departure checklist uses the free dbatools PowerShell command Find-DbaUserObject to list what a login owns. It also uses Set-DbaAgentJobOwner and Set-DbaDbOwner to reassign jobs and databases.
SSIS packages need a separate check. The default protection level, EncryptSensitiveWithUserKey, encrypts passwords and connection strings with the key of the person who saved the package. When another account runs the package, such as the SQL Server Agent service account, the package loads but cannot decrypt those values. It may fail with Failed to decrypt protected XML node, code 0xC0016016, or Failed to acquire connection.
The available fixes include running the job step through a proxy with the right credential. You can also save the package with a different protection level, such as ServerStorage or EncryptSensitiveWithPassword. Microsoft’s guidance for SSIS packages run by SQL Server Agent covers these options.
Do not wait for month-end to discover which jobs had a personal owner. Review all scheduled jobs during the handover.
Files and connections that live with them
Report files with the .pbix extension, SQL scripts, pipeline notes, and instructions often exist only on the person’s laptop or OneDrive. Copy them to a shared location that the right people can access.
Check saved connections as well. Reports, models, scripts, and scheduled jobs may sign in with the person’s own account. A file can be safely copied while the process behind it still fails because its connection was never changed.
The on-premises data gateway
The on-premises data gateway may be the link between Power BI and data held inside your company network. The immediate risk is losing the recovery key or access to the machine where the gateway was installed.
To take over an existing gateway, run the gateway installer on the new machine. Select Migrate, restore, or takeover an existing gateway, then enter the recovery key created during the original installation. Microsoft does not hold that key and cannot retrieve it. A gateway cluster that has already been removed or deleted cannot be restored. Microsoft documents the gateway takeover process and its recovery key requirement.
Find the recovery key while the departing person can still tell you where it is. Add another gateway administrator as part of the handover.
Semantic models they own
Each Power BI semantic model has one owner. That owner also has one set of credentials for each data source used by the model. If those credentials belong to the departing person, scheduled refreshes may fail when the account is disabled.
Someone with edit rights in the workspace can open the semantic model settings and select Take over. The new owner can then enter credentials that will remain available. Do this for every model, even when the reports still look current.
Refresh failure emails go to the semantic model owner by default. If the old owner remains the only recipient, nobody else may hear about a failed refresh. Other recipients can be added, but they must be in the same Microsoft Entra tenant. These ownership, credential, and notification rules are covered in Microsoft’s guidance on Power BI data refresh.
Reports in their My workspace
Every Power BI user has a My workspace that only they can open in normal use. If a colleague left and you can no longer access reports, ask a Fabric administrator to check that workspace.
A Fabric administrator can use OneLake catalog, then Govern, Workspaces, and Get Access. That access ends automatically after 24 hours, so use the time to identify the content and move it into a shared workspace. Microsoft explains temporary administrator access in its workspace guidance.
Once the user is removed from Microsoft Entra ID, the My workspace appears as Deleted. It is retained for a fixed 30 days. During that period, a tenant administrator can restore it as a normal shared workspace, give it a new name, and assign at least one administrator. After that window, this recovery route is gone. See Microsoft’s workspace retention guidance.
Also look for shared workspaces with no administrator. The admin workspace list shows these as Orphaned. Assign an administrator so access does not depend on the departed user.
The first-week checklist
Work through this list with IT. Record the answer and the person responsible for each action.
-
Keep the account open until the handover is complete. Do not close or delete it as an administrative first step. Preserve access while you find the items tied to it.
-
Change SQL Server Agent job owners. Review every job, not only the ones you recognize. Record the SSIS packages and scripts each job runs. Replace personal owners with an approved service account or
sa. -
Check credentials, proxies, and database owners. List credentials and SQL Server Agent proxies set up with the person’s login. Find every job step that uses them. Check for databases owned by the login. Move each dependency to an approved login or credential that will remain.
-
Check SSIS package protection. List every SSIS package saved by the person and record its protection level. If a package uses
EncryptSensitiveWithUserKey, choose an applicable fix before another account has to run it. Run the step through a proxy with the right credential, or save the package withServerStorageorEncryptSensitiveWithPassword. -
Copy the working files. Put
.pbixfiles, SQL scripts, pipeline files, notes, and instructions in a shared location. Open the folders with the people who will need them and confirm they have access. -
Protect the gateway. Add a second gateway administrator. Find the recovery key and store it in the secure place your company uses for access information. Record the machine where the gateway is installed.
-
List every Power BI workspace and semantic model. Record whether each workspace is shared or personal. For every model, write down its current owner and the reports that depend on it. Assign an administrator to any workspace marked Orphaned.
-
Take over the semantic models. Someone with edit rights in the workspace should select Take over in each model’s settings. Replace personal data source credentials with approved credentials that will remain available.
-
Send failure emails somewhere monitored. Add a shared mailbox in the same Microsoft Entra tenant as a refresh notification recipient. Keep a named owner too, but do not leave alerts going to one person’s inbox.
-
Move content out of My workspace. Use the Fabric administrator’s 24-hour access period to inspect and move reports and models into a shared workspace. If the account has already been removed, ask a tenant administrator to restore it as a shared workspace within the 30 days.
-
Write down what runs and who responds. For every refresh, job, or pipeline, record what it does, when it runs, which account it uses, and who is told when it fails. Keep the first version simple enough for an owner or finance lead to read.
Who looks after it next
Hiring a replacement gives you someone with direct responsibility for the whole stack. This can fit when the work needs regular attention and there is enough ongoing work for a dedicated role. Recruitment and handover take time, so you still need an interim owner.
Training someone inside keeps knowledge close to the business. It can work well when that person has time, technical support, and a named backup. Make the responsibility part of the job rather than an informal task added to finance or operations.
An outside team can suit a stable system that needs monthly care, fixes, documentation, and a controlled amount of change. With our Take over and run it service, we take over the existing stack, wherever it runs, and keep the jobs, pipelines, semantic models, and reports running. We fix breaks and document the setup so nobody depends on one person. We also make one agreed change each month for a fixed monthly amount, with the hours cap written down.
Frequently asked questions
What should we do if the person who ran our data left?
Keep the account open while you make an inventory. Check SQL Server Agent job owners, SSIS packages and scripts, personal credentials, files stored on the person’s laptop or OneDrive, gateway access, semantic model ownership, and My workspace content. Move each dependency to an account, workspace, or location that will remain.
How do we transfer ownership of reports and the model behind them?
First find the workspace that contains the reports and the semantic model behind them. If the content is in the person’s My workspace, ask a Fabric administrator to get temporary access and move it into a shared workspace. For the semantic model, someone with edit rights in the workspace selects Take over in its settings and updates the data source credentials.
What if a SQL Server Agent job owner left?
Open the job’s Properties in SQL Server Management Studio and check the owner. If it is the departed person’s login, change it to an approved service account or sa. Review the other jobs at the same time because more than one may use that login.
How we checked this: every rule on this page was checked against Microsoft Learn and the sources linked above on 10 November 2026.
Send your report list or a screenshot of the workspace list through our free first read. We will send one page back within five business days showing what is there and what is at risk. It is free, and nothing is changed in your systems.
