# A Service Account Inventory for Small Teams: Name the Owner Behind Each Automation

<a id="main-content"></a>

Operations &amp; Systems

October 28, 2026  ·  8 min read  ·  Victor Valentine Romo

On this page

1. [Separate the Person From the Identity Doing the Work](<#separate-the-person-from-the-identity-doing-the-work>)
2. [Begin With One Output You Can Trace](<#begin-with-one-output-you-can-trace>)
3. [Copy This Service Account Inventory Template](<#copy-this-service-account-inventory-template>)
4. [Work Through the Fictional Report Exporter](<#work-through-the-fictional-report-exporter>)
5. [Work Through the Scheduled Document Processor](<#work-through-the-scheduled-document-processor>)
6. [Treat an Unknown Consumer as Unfinished Investigation](<#treat-an-unknown-consumer-as-unfinished-investigation>)
7. [Review Ownership on a Deliberate Schedule](<#review-ownership-on-a-deliberate-schedule>)
8. [Transfer the Responsibility With Acceptance Evidence](<#transfer-the-responsibility-with-acceptance-evidence>)
9. [Sources](<#sources>)

The report arrives every morning.

Nobody knows which identity produces it.

The person who configured the job leaves. A permission question lands with the remaining team. The scheduled task keeps running while everyone searches for someone who can explain its access.

Give each [automation](</articles/automation-workflows-b2b-operations/>) identity a record with a responsible person, a bounded purpose, and evidence of the resources it can reach.

This service account inventory template starts with one workflow. It is a proposed working method. Every person, identifier, date, and record below is fictional. The worksheet records findings. It does not authorize account creation, credential rotation, permission changes, or [deletion](</articles/data-deletion-verification-record/>).

<a id="separate-the-person-from-the-identity-doing-the-work"></a>

## Separate the Person From the Identity Doing the Work

In Microsoft Entra terminology, service accounts represent non-human entities. Microsoft distinguishes managed identities, service principals, and user accounts employed as service accounts. A service principal is the local representation of an application object in one Microsoft Entra tenant. A managed identity supplies an identity for Azure resources; it can be system-assigned or user-assigned. [Microsoft's service account introduction](<https://learn.microsoft.com/en-us/entra/architecture/secure-service-accounts>).

A human user is the person participating in the workflow. A user-based service account uses a user account for automated work. Its execution purpose differs from a person's ordinary interactive work. Microsoft recommends managed identities where supported, or service principals, over user accounts used for this purpose. Keep that recommendation within Microsoft's product scope. [Microsoft's identity guidance](<https://learn.microsoft.com/en-us/entra/architecture/secure-service-accounts>).

Record the type observed in the source system. If you cannot establish it, write unknown and assign the investigation. A display name containing “service” does not establish the identity type.

Keep the accountable person in a separate field. The identity runs the process. The owner explains why the process should exist.

An [API-first operations plan](</articles/api-first-business-operations/>) describes connections between systems. This inventory answers a narrower question: which identity executes this connection, and who accepts responsibility for it?

<a id="begin-with-one-output-you-can-trace"></a>

## Begin With One Output You Can Trace

Choose a recurring output that the team recognizes. Name its workflow before collecting accounts.

For this example, the output is [a daily request summary](</articles/reporting-automation-b2b-services/>) saved for an internal reviewer. A fictional exporter reads a request store and writes a report file. A separate document processor reads submitted documents and saves draft summaries.

Do not assume both jobs use the same identity because the same person configured them. Trace each execution path independently.

Ask the technical custodian to identify the configured identity from the job's approved configuration record. Record where that evidence lives and when it was inspected. Keep the source record under its existing access controls.

Use the [business system dependency map](</articles/business-system-dependency-map/>) to locate the workflow's inputs and outputs. Put a reference to that map in the inventory. Avoid copying an entire technical diagram into every identity row.

Declare the first pass's boundary: these two workflows, these observed identities, and these unresolved consumers. An inventory of two jobs cannot establish that the organization has no other automation identities.

<a id="copy-this-service-account-inventory-template"></a>

## Copy This Service Account Inventory Template

Use one identity record with linked consumer rows when several jobs share an identity. Preserve the distinction between the identity and each use.

The fields below are an editorial template. Microsoft also recommends documenting ownership, purpose, permissions, and lifecycle reviews in its [service account governance guidance](<https://learn.microsoft.com/en-us/entra/architecture/govern-service-accounts>).

| Field | What to record |
| --- | --- |
| Inventory reference | Stable local record label |
| Identity | Provider, tenant or environment, object identifier, observed type |
| Display name | Current label and observation date |
| Business owner | Named person accepting the workflow's business purpose |
| Technical custodian | Named person maintaining configuration and evidence |
| Purpose | Output, permitted use, and explicit exclusions |
| Consumers | Job references and evidence connecting each job to the identity |
| Resources | Source, destination, and environment identifiers |
| Permission evidence | Observed assignments, scope, source location, inspection date |
| Credential reference | Controlled storage reference or documented credential-management mechanism |
| Review record | Last review, findings, next review, and responsible person |
| Open investigation | Missing evidence, investigation owner, and response date |

Record identifiers without copying secrets. An object identifier locates the identity; a credential can enable its use. Keep passwords, private keys, tokens, recovery codes, and [credential-bearing links](</articles/expiring-export-download-links/>) outside this document.

For the public example, labels such as `SYN-SP-EXPORT-01` are readable stand-ins. They are not valid tenant identifiers. Your internal record needs the identifier observed in the actual environment.

Separate [the observed permission](</articles/small-team-access-review-evidence/>) from the expected permission. “Should read requests” describes intent. A dated assignment export establishes what the reviewer observed. Keep a discrepancy visible until someone resolves it through the authorized process.

<a id="work-through-the-fictional-report-exporter"></a>

## Work Through the Fictional Report Exporter

The first record describes a synthetic report exporter. These permissions describe an invented application, not standard Entra permission names.

| Inventory field | Fictional entry |
| --- | --- |
| Reference and identity | INV-01; SYN-SP-EXPORT-01; service principal in synthetic environment A |
| Display name | Daily report exporter, observed 2026.10.28 |
| Business owner | Ari, operations lead |
| Technical custodian | Rowan, integration maintainer |
| Purpose | Prepare an internal request summary; no source-record editing |
| Known consumer | JOB-EXPORT-01, linked by configuration evidence CFG-01 |
| Resources | Synthetic request store and report draft folder |
| Permission evidence | PERM-01 records request reading and draft-folder writing, inspected 2026.10.28 |
| Credential reference | Restricted credential catalog entry CRED-01; no credential value included |
| Review | Ari and Rowan review 2026.11.25 |

Rowan checks that CFG-01 names the recorded identity. Ari checks that the summary still serves the stated purpose. They compare the observed assignments with that purpose.

Suppose PERM-01 also records access to an old archive. Add a finding: archive permission has no confirmed current purpose. Assign Rowan to trace its consumer and Ari to resolve the business need.

Do not rewrite the evidence to show only the expected permissions. Preserve what was observed. Record a proposed change separately from the inventory snapshot.

The record now supports a precise conversation: which workflow needs archive access, which owner can explain it, and what evidence should settle the question?

<a id="work-through-the-scheduled-document-processor"></a>

## Work Through the Scheduled Document Processor

The second job produces draft summaries from synthetic intake documents. Its current owner field names someone who has left the fictional team.

| Inventory field | Fictional entry |
| --- | --- |
| Reference and identity | INV-02; SYN-MI-DOC-02; system-assigned managed identity on synthetic Azure resource DOC-02 |
| Display name | Document draft processor, observed 2026.10.28 |
| Business owner | Unresolved; previous owner no longer holds the responsibility |
| Technical custodian | Rowan, pending owner assignment |
| Purpose | Read intake documents and save draft summaries for human review |
| Known consumer | JOB-DOC-02, linked by configuration evidence CFG-02 |
| Resources | Intake document folder and summary draft folder |
| Permission evidence | PERM-02, inspected 2026.10.28; business justification awaiting owner review |
| Credential reference | Managed identity mechanism recorded in CFG-02; no secret value recorded |
| Review | Owner assignment due 2026.10.30; next evidence review 2026.11.06 |

This is an orphaned ownership finding. The machine's continued execution does not assign a replacement owner.

Give the operations sponsor the task of naming someone who can accept the purpose and its boundaries. Rowan preserves technical evidence while that decision remains open. Record the interim escalation contact without pretending the permanent handoff is complete.

Keep configuration changes outside the inventory session. If the finding needs urgent containment, route it through the team's authorized [incident](</articles/incident-postmortem-small-service-team/>) process. The worksheet alone grants no operational authority.

<a id="treat-an-unknown-consumer-as-unfinished-investigation"></a>

## Treat an Unknown Consumer as Unfinished Investigation

Suppose the exporter identity appears in another configuration reference, CFG-03. The record does not establish which workflow uses it.

Add a consumer row marked unknown. Record where the reference appeared, its observation date, and the person investigating it. Do not invent a job name from a folder label.

Use this small finding record:

| Finding field | Fictional entry |
| --- | --- |
| Question | What consumes exporter identity through CFG-03? |
| Confirmed evidence | Configuration reference observed; workflow connection unverified |
| Investigation owner | Rowan |
| Business contact | Ari, pending identification of the consumer owner |
| Next evidence | Approved job configuration and corresponding execution record |
| Review date | 2026.10.30 |
| Change status | No change requested or authorized |

Microsoft's governance guidance calls for dependency checks and investigating active use during deprovisioning. That supports tracing use before proceeding. It does not make this sample a deprovisioning [procedure](</articles/sop-documentation-b2b/>). [Microsoft's lifecycle guidance](<https://learn.microsoft.com/en-us/entra/architecture/govern-service-accounts>).

Follow the dependency until the output and owner are known, or record the search boundary and unresolved result. Absence from one scheduler is evidence about that scheduler. It cannot settle every possible consumer.

Keep three evidence states separate. Confirmed means the record connects the identity to an observed configuration or execution. Proposed means someone describes the connection without supporting evidence. Unknown means the team cannot yet explain the reference.

In this example, JOB-EXPORT-01 is confirmed through CFG-01. A suggestion that CFG-03 belongs to an old reporting experiment remains proposed. The experiment's current output and accountable owner remain unknown.

That distinction gives the next investigator a useful starting point. They can test the proposed explanation without treating it as an established dependency. Record any contradictory evidence beside the finding, including a configuration that points to a different identity.

Close the finding only against a stated question. Identifying CFG-03's workflow resolves the consumer question. The team still needs to decide whether its purpose and permissions remain appropriate. Preserve those as separate review items.

<a id="review-ownership-on-a-deliberate-schedule"></a>

## Review Ownership on a Deliberate Schedule

Choose a review interval suited to the workflow and the team's policy. The dates in this article illustrate records; they prescribe no universal cadence.

At the review, ask the business owner to confirm the output, audience, and ongoing purpose. Ask the custodian to refresh the identity, consumer, and permission evidence. Give each answer its own observation date.

If nothing changed, record which sources were inspected. “No change” needs a boundary. It could mean the owner remains assigned while permission evidence remains stale.

Track unresolved findings alongside the next review date. Do not [reset their age](</articles/work-item-aging-small-service-teams/>) by copying them into a fresh worksheet. A new review can confirm that an old question remains unanswered.

Keep the result specific: INV-01 has a confirmed owner and one unresolved consumer. INV-02 has current configuration evidence and an unassigned business owner. Neither record deserves an unqualified complete label.

<a id="transfer-the-responsibility-with-acceptance-evidence"></a>

## Transfer the Responsibility With Acceptance Evidence

When the sponsor names a replacement for INV-02, record the proposed owner, accepting person, effective date, and scope.

In the fictional handoff, Casey accepts responsibility for the document processor's purpose. Rowan remains the technical custodian. Casey reviews the output boundary, evidence locations, open questions, and escalation route before accepting.

Use the [small-team operations handover](</articles/operations-handover-small-team/>) to structure that transfer. An owner-field edit records an assignment. Acceptance evidence records whether the receiving person understands and accepts it.

Keep the previous owner in the dated change history. Give the new owner a review date. Test access to the inventory and its permitted evidence locations using the receiver's own authorized access.

Finish the first pass with named owners where confirmed, investigation records where unknown, and no secrets in the worksheet.

Leave every running identity with a person who can answer for it.

<a id="sources"></a>

## Sources

- [Microsoft Learn: Securing cloud-based service accounts](<https://learn.microsoft.com/en-us/entra/architecture/secure-service-accounts>). Entra identity terminology and identity selection guidance. Checked 2026.10.28.
- [Microsoft Learn: Governing Microsoft Entra service accounts](<https://learn.microsoft.com/en-us/entra/architecture/govern-service-accounts>). Ownership, permission records, review, and dependency investigation. Checked 2026.10.28.
