An automated process can continue using an account after the employee who created it leaves. The account may belong to a nightly import, an old reporting tool, or a deployment script whose original purpose is no longer documented. Its activity can look routine because it has been running for years.

Give each service account a current owner and a documented purpose. That owner needs to know what will break if its credential changes and when the account can be retired.

An account name is not an ownership record

Microsoft's service-account guidance addresses creation, permissions, ownership, and lifecycle management. It distinguishes automated identities from ordinary user accounts and recommends maintaining the context needed to govern them. The Microsoft guidance describes this operational approach.

For an inventory synchronization job, record the application owner, maintainer, accessed systems, credential location, schedule, and retirement condition. An account named after a former employee does not tell the next administrator who can approve a permission change.

Compare granted access with observed work

List the operations the process performs and compare them with the account's permissions. A job that reads stock levels may not need to change supplier payment information. Observation helps identify unused access, but a short observation window can miss monthly or annual tasks.

Review documented requirements alongside activity records. If the team cannot explain a permission, record that uncertainty and investigate it before making a production change. Removing access without understanding dependencies can interrupt work; leaving it indefinitely without an owner preserves an unreviewed access path.

Plan credential changes as application changes

Changing a service credential can affect several workers, scheduled jobs, and recovery scripts. Identify all consumers and define how they receive the new credential. Where the platform supports managed identities or temporary credentials, evaluate whether those mechanisms fit the workload instead of assuming every process requires a stored password.

In staging, replace the credential and observe the next scheduled cycle. Test the failure path as well: does an authentication error produce an actionable alert, or does the job stop silently while the dashboard continues displaying old data?

Retire the identity with evidence

A controlled retirement can stop the process, disable its access, and monitor for unexpected attempts before final deletion under the organization's retention policy. Record which business outputs were checked and whether any hidden consumer still depended on the account.

Separate accounts confirmed unused from those whose activity is unknown. List missing owners and unexplained permissions, then agree the investigation and retirement order with operations. Keep the business outputs checked during each retirement in the record.

Sources

Microsoft: Govern On-Premises Service Accounts. The synchronization job is illustrative.

Back to the blogExplore Ceron