Forum Discussion
credential management best practices?
Hi GQ00 ,
Some connections that use the previous item owner's credentials might stop working if the new item owner doesn't have access to the connection. In such cases, you might see a warning message.
In this scenario, the new item owner can fix connections by going into the item and replacing the connection with a new or existing connection.
For Dataflows please consider editing the data source credentials by following this article:
Data source management - Microsoft Fabric | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Thank youHi,
Tried using a dedicated service account,it didnt work for all connections.
Also if the consultants account has been deactivated for months, how come the pipeline was still working? Somehow the token expired only 60 days after last log in, and to my knowledge, I have no way to knowing this... what a way to be blindsighted on a monday morning.
Anyway, we ended up creating a dedicated user account, to own the connections and also allow it to own the assets (DF, PL, NB) while still editing them if needed.
It all seems to be working now, but yet another additional license just to keep things running...
Hi GQ00 ,
This behavior usually happens because connections were originally created under a personal/consultant account, so when that identity expired, dependent pipelines and dataflows lost their authentication context. Restoring the consultant’s login temporarily revalidated those credentials, which is why things started working again.
Best practice is to avoid personal accounts for production connections. Instead, create a dedicated service account (Entra ID user or managed identity) that owns and maintains all Fabric connections. That way, pipelines, dataflows, and notebooks remain stable even if individual users leave the organization. It also centralizes credential management and reduces the risk of random failures.
Thanks,
Sai Teja
Hi,
Tried using a dedicated service account,it didnt work for all connections.
Also if the consultants account has been deactivated for months, how come the pipeline was still working? Somehow the token expired only 60 days after last log in, and to my knowledge, I have no way to knowing this... what a way to be blindsighted on a monday morning.
Anyway, we ended up creating a dedicated user account, to own the connections and also allow it to own the assets (DF, PL, NB) while still editing them if needed.
It all seems to be working now, but yet another additional license just to keep things running...