# Create and manage AD Service Account in IdentityNow

**URL:** <https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170>\
**Category:** SHF Discussion and Questions\
**Created:** [May 11, 2022, 3:50am UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170 "2022-05-11T03:50:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xiaofangc](https://avatars.discourse-cdn.com/v4/letter/x/8baadc/32.png) [@xiaofangc](https://developer.sailpoint.com/discuss/u/xiaofangc)\
**Post date:** [May 11, 2022, 3:50am UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170/1 "2022-05-11T03:50:42Z")

</div>

We have a requirement to provision AD Service Account after user submits a self-service request in ServiceNow (or IdentityNow if possible) and fills in the details of the Service Account (description, owner etc.).

Is it possible to implement the provisioning through IdentityNow? The options we could think of are as follows.

- CreateAccount API  
The API doesn’t create account in target systems, so this approach won’t work.

- Lifecycle event through AD Connector  
Could we provision the service account and link it to the owner’s identity? If yes, how is this done in IdentityNow? If not, should we create new Identity for the Service Account (i.e. Each Service Account has its own identity)?

Please advice, thanks much!

---

<div class="post-metadata">

**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\
**Post date:** [May 11, 2022, 2:44pm UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170/2 "2022-05-11T14:44:23Z")

</div>

We were in this same situation and ended up creating the account in AD directly and letting IDN aggregate it.

---

<div class="post-metadata">

**Author:** ![nico24](https://avatars.discourse-cdn.com/v4/letter/n/9d8465/32.png) [@nico24](https://developer.sailpoint.com/discuss/u/nico24)\
**Post date:** [May 16, 2022, 6:05pm UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170/3 "2022-05-16T18:05:07Z")

</div>

Jup we are going to build automation to handle all service accounts. They just don’t seem to be a good fit for IdentityNow.

---

<div class="post-metadata">

**Author:** ![cpatel](https://avatars.discourse-cdn.com/v4/letter/c/48db29/32.png) [@cpatel](https://developer.sailpoint.com/discuss/u/cpatel)\
**Post date:** [May 17, 2022, 5:30am UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170/4 "2022-05-17T05:30:28Z")

</div>

> [@nico24](#):
>
> build automation to handle all service accounts. They just don’t seem to be a good fit for IdentityNow.

You can probably use NELM to request new identity(for each service account), assign owner as the manager and then initiate provisioning to AD from IdentityNow.

Just assumption but things might vary based on your requirement.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [July 19, 2023, 2:23pm UTC](https://developer.sailpoint.com/discuss/t/create-and-manage-ad-service-account-in-identitynow/4170/5 "2023-07-19T14:23:02Z")

</div>

Closed on July 19, 2023, 2:23pm UTC