Hi @angie_vetrone,
A comprehensive approach to handling service accounts would be to maintain a delimited file of service accounts with the following application attributes:
User Name:
First Name
Last Name:
Owner:
Inactive:
The naming convention should be as the document prescribed. In this case it would be sAMAccountName for username. The Owner attribute should match the identity attribute of the individual (Identity Attribute from the HR Source) that would be responsible for the service account.
Owner correlation:
Aggregate this delimited application as an authoritative source.
Perform Identity Mappings
Global Settings>Identity Mapping
Display Name : User Name
First Name : First Name
Last Name : Last Name
Manager : Owner
Inactive : Inactive
Type: Under source mappings > Add source > Application Rule > Choose the application > Rule editor > return "Service Accounts";
Run Refresh Task
Now aggregate the service account AD application you have configured prior.
Correlation for AD application
Application Attribute | Identity Attribute
sAMAccountName : Display Name
These are best practices according for service account management. Since you have an owner assigned and the owner correlated to the manager attribute; your access requests, certifications, and policy management all of it would be streamlined.
Hope this helps.