https://github.com/tools4everbv/helloid-task-sa-target-activedirectory-accountdelete
Active Directory - User account delete
https://github.com/tools4everbv/helloid-task-sa-target-activedirectory-accountdelete
active-directory delegated-form powershell product service-automation task
Last synced: 8 months ago
JSON representation
Active Directory - User account delete
- Host: GitHub
- URL: https://github.com/tools4everbv/helloid-task-sa-target-activedirectory-accountdelete
- Owner: Tools4everBV
- Created: 2023-02-28T13:28:18.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-01-09T15:10:49.000Z (over 2 years ago)
- Last Synced: 2025-01-08T10:45:41.339Z (over 1 year ago)
- Topics: active-directory, delegated-form, powershell, product, service-automation, task
- Language: PowerShell
- Homepage:
- Size: 26.4 KB
- Stars: 0
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# HelloID-Task-SA-Target-ActiveDirectory-AccountDelete
## Prerequisites
- [ ] The HelloID SA on-premises agent installed
- [ ] The ActiveDirectory module is installed on the server where the HelloID SA on-premises agent is running.
## Description
This code snippet will delete a user from Active Directory and executes the following tasks:
1. Define a hash table `$formObject`. The keys of the hash table represent the properties of the `Get-ADUser` cmdlet, while the values represent the values entered in the form.
> To view an example of a form output, please refer to the JSON code pasted below.
```json
{
"UserPrincipalName": "testuser@mydomain.local"
}
```
> :exclamation: It is important to note that the names of your form fields might differ. Ensure that the `$formObject` hashtable is appropriately adjusted to match your form fields.
2. Imports the ActiveDirectory module.
3. Verifies that the account that must be deleted exists based on the `userPrincipalName` using the `Get-ADUser` cmdlet.
4. If the user does exist, the account is removed using the `Remove-ADObject` cmdlet, otherwise an warning is generated.
Note, it uses the `Remove-ADObject` rather than the `Remove-ADUser` because the latter one does not have a recursive option, and fails when the user object contains child objects.