Lifecycle & Access Governance
Rename User
Rename a person on their directory account and Avatier identity record, with your naming rules filling in the rest.
Completes when the directory account and the Avatier identity record change: after approval, or at once when a workflow admin skips workflow.
https://mcp.avatier.com/mcp
Ask in Plain Language
Run Rename User from the AI Assistant You Already Use
Your Lifecycle Management approval workflow decides who approves, with identity verification first in Avabot and MCP. One completed rename = one Secure Outcome; failed attempts are never billed.
You: Rename Jordan Smith to Jordan Rivera. Justification: legal name change. Avatier: verify: passed · new name: Jordan Rivera · naming rules: applied · request: submitted, may need approval
Why it matters
A Name Change Touches More Than the Display Name.
Display name, sign-in name, email and mailbox fields all have to agree, and follow your naming convention.
What a rename needs
The new first and last name, with your tenant's auto-naming rules composing the other values, and a justification on the request path.
What goes wrong by hand
Renaming by hand means editing each field in each place and keeping to the naming convention, with no request or approval on the record.
What Rename User does
It shows current and proposed values side by side, fills the proposed ones from your naming rules as you type, and allows one rename per person in progress at a time.
What per-seat pricing charges
Per-seat IAM charges for every licensed seat, whether anyone is renamed this month or not. Pay Per Identity Action™ charges only for completed renames.
The Action
How Rename User Runs
On the web, Rename User walks through these screens. In Avabot and MCP you verify, name the person or yourself, give the new first and last name, and the naming rules compose the rest.
Verify in Avabot or MCP
Avabot and MCP only. Rename User starts with identity verification in the conversation, with the methods your policy already allows, such as security questions, authenticator codes, PingID push or the Identity Challenge Card. On the web there is no extra check beyond your sign-in. By default, Rename User does not need a fresh verification.
Identity Verification (Avabot and MCP)
Select the User
Pick the system and search for the person: yourself, someone you're authorized to request for, or anyone if you are a workflow admin. Okta accounts aren't offered. Workflow admins are then asked "Would you like to use workflow?"
Give a Justification
Enter a Justification. A workflow admin who skips workflow goes straight to the name fields, with no justification.
Edit the Names
Edit the proposed values next to the current ones: Display Name, First Name and Last Name, plus, depending on the directory, Middle Initials, Email, Logon Name, Full Name, Pre 2000 Name, Exchange Alias and Exchange Display Name, or for Entra ID the Principal Name and UPN Domain. Your auto-naming rules fill these in as you type, and a field that had a value can't be left blank.
Check the Summary
Review the current and new values side by side.
Confirm
Confirm to submit. The rename is recorded in Request History with a Request ID and goes through your Lifecycle Management approval workflow. A workflow admin who skips workflow applies it right away, and it is still recorded as a Rename User request that skipped approval.
Approval point
Available on Web, Mobile, Teams, Avabot chat and MCP.
Avabot chat and MCP require the current (.NET 10) Avatier server.
In Avabot chat and MCP, you give the new first and last name, with an optional middle name, and your naming rules compose the other values; you can edit them on the web.
Secure Outcome
What Counts as Done
A Secure Outcome is a completed, verified, policy-compliant identity action. A rename completes when the directory account and the Avatier identity record change, after approval or at once when a workflow admin skips workflow. Either way it is recorded as a Rename User request. Avabot's reply says whether the rename was submitted or applied, and gives the new sign-in name when it changes. One completed rename = one Secure Outcome.
Evidence
- A Request ID in Request History (filter Rename User, exportable)
- An activity-log entry
- Avabot's reply, with the new sign-in name when it changes
Guardrails
Your Assistant Asks. Avatier Decides.
Verified First
Avatier verifies the person before sensitive changes, with the methods your policy already allows.
Acts as the Signed-In User
OAuth sign-in to your own tenant. No shared service account, no API key to manage.
Never Makes Up Values
The connector only sends what the person actually said, and asks when something is missing.
Every Request Recorded
Requests land in Request History, ready to review and export.
Pay Per Identity Action™
Pay per Completed Rename
Pay per completed rename. Failed attempts are never billed.
| Compared | Manual or Per-Seat IAM | Rename User, Pay Per Identity Action™ |
|---|---|---|
| What you pay for | Every licensed seat, whether it acts or not | Completed renames only |
| Failed attempts | No line between an attempt and a result | Attempts, failures and retries are never billed |
| The work | Manual intervention or tickets | Once approved, the directory account and the Avatier identity record carry the new name |
| Evidence | Silent failures and missing audit trails | A Request ID in Request History and an activity-log entry, including renames an admin applies at once |
Pay Per Identity Action™ is in invitation-only preview. Pricing is shared with qualified organizations.
Works with the Systems Rename User Touches
Rename User changes the person's account on Active Directory, directly or through the on-premises agent, or on Entra ID, plus their Avatier identity record. Okta accounts are not offered, and LDAP connectors don't support rename.
- Microsoft
- Active Directory accounts, directly or through the on-premises agent, including the Exchange alias and display name when a mailbox exists, and Entra ID accounts.
- Avatier
- The person's Avatier identity record changes with the directory account.
Avatier MCP
New to Avatier MCP?
The Model Context Protocol is an open standard, stewarded by the Linux Foundation, that lets AI assistants call real systems through connectors instead of custom integrations.
Up and Running in Under a Minute
One URL works in every MCP client. Pick yours, copy, paste, sign in.
Microsoft Copilot Studio
Claude Code
OpenAI Codex
Cursor
Frequently Asked Questions
Does Rename User change the sign-in name or only the display name?
It can change both. Besides the display, first and last name, it updates other name, email and sign-in fields depending on the directory, so the person's sign-in name can change too.
Does it follow our naming convention?
Yes. Proposed logon, display and email values are generated from the new name parts using your tenant's auto-naming rules, and can be edited on the web.
Why was my second rename refused?
Only one rename per person can be in progress at a time. Wait for the pending one to finish.
Can a rename be scheduled?
No. A rename takes effect when it is approved.
Does Avatier provide AI-driven compliance reporting?
Yes. Avatier turns continuous identity and access data into audit-ready reports on demand, using AI to assemble who has access to what, what changed, and who approved it, mapped to the controls auditors expect. Instead of a manual evidence scramble before each audit, you generate plain-language, exportable reports covering SOC 2 Type II and ISO 27001, plus the evidence needs associated with NIST, SOX, HIPAA, and GDPR.
What is AI-driven configuration?
Avatier's AI-driven config turns plain-language intent into working policy. Rather than hand-coding rules, connectors, and roles, administrators describe what they need and Avatier recommends and sets up provisioning rules, role mappings, and workflows, then validates them before they go live. It shortens deployment from months to days and keeps configuration consistent, auditable, and free of custom scripting.
What is Pay Per Identity Action™?
Pay Per Identity Action™ is Avatier's pricing mechanic. Customers pay only for completed, verified, policy-compliant identity actions, called Secure Outcomes.
Is it the same as pay-per-action advertising?
No. Pay per action (PPA) is performance-marketing vocabulary for paying when an ad converts. Pay Per Identity Action™ charges for completed identity work.
How do I get started?
Getting started is free, deployment services are included, and a 45-day money-back guarantee applies. Contact Avatier for pricing for your organization.
What is MCP?
The Model Context Protocol is an open standard, stewarded by the Linux Foundation, that lets AI assistants call real systems through connectors instead of custom integrations.
How is it billed?
Pay Per Identity Action™ is in invitation-only preview: each completed, verified action is one Secure Outcome, and attempts, failures and retries are never billed.
Rename User
You've Automated the System. Now Secure the Lifecycle.
Give the new name, let your naming rules compose the rest, and the rename is recorded in Request History with a Request ID.