Skip to content
InvardiaInvardia
Why InvardiaProductsFeaturesPricingCommunity
Docs
All documentation
Product documentationPIM ManagerSecurityInsight
SettingsPIM Manager settingsSecurityInsight settingsEntra Policy Suite settings
ScriptsPIM Manager scriptsSecurityInsight scriptsEntra Policy Suite scriptsInvardia scripts
Error codesPIM Manager error codesSecurityInsight error codes
API and MCPPIM Manager APIPIM Manager MCP toolsSecurityInsight APISecurityInsight MCP tools
SecurityPIM Manager security packSecurityInsight security packEntra Policy Suite security pack
Network and designPIM Manager network guidesPIM Manager command wizardNetwork egressDesign your installationCalculate your cost
SupportSetup scriptsRemote support access
Search the docs
SupportAboutContactBook a demoCustomer portalDesign your installationFree Pro trial

PIM Manager docs

1 Why

  • Why PIM Manager

2 Features

  • Features
  • Delegation model
  • Change control
  • Admin accounts
  • Visibility and evidence
  • Integrations
  • Platform and editions

3 How to design

  • How to design
  • Nested groups
  • Role-assignable groups
  • Tiers and levels
  • Naming
  • Migration
  • Workload roles

4 Security design

  • Security design
  • Identities
  • Engine permissions
  • Database
  • Sign-in
  • Approval and audit
  • Support access
  • Updates and license
  • Data
  • Database access (least privilege)

5 Architecture, setup and sizing

  • Architecture
  • Setup
  • Sizing

6 Operate

  • Operate
  • Guards
  • Access reviews
  • PIM Activator
  • Settings

7 Integrate

  • Integrate
  • REST API and ServiceNow
  • MCP server for AI assistants
  • Hybrid Active Directory
  • MSP: managing and managed tenants

8 Knowledge base

  • Knowledge base
  • How to onboard a consultant
  • How to onboard an admin
  • How to delegate a Power BI workspace
  • How to delegate an Azure landing zone or subscription
  • How to delegate Intune roles
  • How to delegate Defender XDR to a helpdesk
  • How to use Discovery and gaps
  • How to handle drift
  • How to undo a commit
  • How to enable access reviews
  • How to approve a held policy change
  • How to add a break-glass account
  • How to install the PIM Activator without Intune
  • How to set up PIM for Active Directory
  • How to read the access map and see who can activate a role
  • How to find the least-privileged role for a task
  • MSP: how to roll a change to one wave
  • How to activate with the PIM Activator
  • How to offboard an admin
  • FAQ
  • Lessons learned

9 Reference

  • Reference
  • Glossary

10 Support

  • Support

On this page

  • What you need
  • How the name is built
  • Step 1: open the wizard
  • Step 2: the person
  • Step 3: purpose and platform
  • Step 4: when the account and the pass start
  • Step 5: lifecycle
  • Step 6: role groups
  • Step 7: review and stage
  • Step 8: commit
  • The Temporary Access Pass
  • Check the result
  • Undo

PIM Manager documentation · Verified against PIM Manager 3.0.23.3 on Nov 3, 2026

How to onboard an admin

An admin who does privileged work from their everyday account exposes that work to every mail and website they open. This guide creates a separate admin account, named by your naming convention, and gets the first sign-in to the person with a Temporary Access Pass (TAP).

For a consultant from another company, follow How to onboard a consultant. It uses the same wizard and adds the employer confirmation.

What you need

  • The Admin role in PIM Manager.
  • The person’s sponsoring department on Reviews & controls > Departments & owners, with at least one owner. The owners approve for the admin and receive its mail.
  • The person’s everyday office mail address. The Temporary Access Pass is sent there.
  • A mail sender for PIM Manager (set up under Get Started). PIM Manager delivers a Temporary Access Pass by mail only and does not show the code on any page.
  • The Temporary Access Pass method switched on in your tenant’s authentication methods policy in Microsoft Entra ID. PIM Manager follows that policy: when it allows one-time passes only, the pass is one-time, and the lifetime is kept within the policy’s minimum and maximum.

How the name is built

The wizard builds the sign-in name from your naming convention and shows it live while you type, under You’ll get – UserName, You’ll get – UserPrincipalName and You’ll get – DisplayName. With the default convention:

The admin is Choose Example name
A day-to-day admin in Entra ID Purpose: Day-2-day admin, Environment: Entra ID admin-jd-id
A day-to-day admin in on-premises AD Environment: Active Directory admin-jd-ad
A dedicated Tier-0 account Purpose: High-priv dedicated admin-jd-l0-t0-id
A consultant with a local account Admin type: Consultant – local account in this tenant x-admin-jd-id

Admin account names are lower case. The admin type sets the prefix and the environment sets the suffix; both come from Settings > Naming & accounts. Read more in Naming.

Step 1: open the wizard

Admin accounts page with the + New admin button above the list of admin accounts (synthetic data)

  1. Open Admin accounts > Admin accounts & TAP and press + New admin. You can also open Access > Create access and choose Create an admin account; it is the same wizard.
  2. The New admin account wizard opens. Its steps are Person, Purpose & platform, Activation, Lifecycle, Role groups and Review. Move between them with Next → and ← Back.

Step 2: the person

  1. Admin type: choose Internal admin for your own employee. The list shows the prefix each type gets.
  2. Start from template: shown only when admin templates exist. A template fills in tier, scheduling, TAP and forwarding; you can change every value afterward.
  3. First name and Last name.
  4. Initials (short code): 2-4 letters used in the sign-in name. It fills in from the name; type your own to override it.
  5. Department (internal): the department that sponsors this admin.
  6. UPN suffix: the domain after the @. It defaults to your tenant’s admin account domain.
  7. Press Next →.

Step 3: purpose and platform

  1. Purpose: keep Day-2-day admin – Admin-INI (default) for an account that holds many delegations over time. Choose High-priv dedicated – Admin-INI-L0-T0 only for a dedicated Tier-0 account; it sets level L0 and tier T0, and the name carries both.
  2. Environment: Entra ID (cloud) for a cloud account, or Active Directory (on-prem) for an account in your on-premises AD (see Hybrid Active Directory).
  3. On a managing tenant, this step also asks how the admin is managed across your managed tenants. Read more in MSP.

Step 4: when the account and the pass start

  1. Create on: keep Now (the next engine run), or choose a preset such as First workday next month, 07:00, or a date. Use a later date when the person’s normal mailbox does not exist yet.
  2. Under Where this admin’s mail goes, keep Forward mail to the owner’s office user? on Yes (recommended) and enter the person’s everyday address in Office user email address. Every mail PIM Manager sends about this admin goes there, including the pass.
  3. Under Temporary Access Pass schedule, set TAP valid from: Immediately (when the account is created), a preset such as First workday next month, 08:00, or a date. PIM Manager creates the pass close to that time, so the code is fresh when the person uses it.
  4. TAP lifetime (hours): from 1 to 720. Blank means 8 hours, capped at your tenant’s maximum.

The New admin account wizard on its Activation step: when the account is created, where its mail goes, and when the Temporary Access Pass becomes valid and for how long

An account in on-premises AD only gets no Temporary Access Pass; a pass is an Entra ID sign-in method.

Step 5: lifecycle

  1. Status: keep Enabled (default – account works normally).
  2. User type (from Admin type) is set by the admin type and cannot be changed here.
  3. Usage location: the country used when licenses are assigned.

Step 6: role groups

  1. Pick the role groups the admin needs. You can skip this and give access later with Give access → on the admin’s row.
  2. Assignment type: keep Eligible (default – must activate via PIM).
  3. Lifetime (days): how long the memberships last before they must be renewed. The default is 365; 0 means permanent and is not recommended.

Step 7: review and stage

  1. On Review, check the sign-in name. If the name is taken, a red line names the account that holds it: go back to Person and change the initials, for example add a third letter.
  2. Press Add to pending changes. Nothing is created yet.

Step 8: commit

Pending changes: the staged edits and queued directory actions in one queue, with Commit all

  1. Open Pending changes > Review & commit queue. The new admin and its role-group memberships are listed.
  2. Press Commit all.
  3. On the next engine run (or on the Create on date), the engine creates the account and adds the eligible memberships. At TAP valid from, it creates the pass and mails it.

The Temporary Access Pass

  • Where it goes. To the office address you entered. Without one, it goes to the owners of the sponsoring department. When neither exists, the engine creates no pass, changes nothing, and Jobs > Engine logs & errors names the reason.
  • What the person does. They sign in with the admin account and the pass, and register their own sign-in methods for the admin account.
  • The risk you accept. Anyone who can read that mailbox can sign in as the admin while the pass is valid. Use the person’s work mailbox, not a private one, keep the lifetime short and start it close to the first sign-in.
  • An expired pass. It is not replaced automatically. Press Reset TAP on the admin’s row; the reset is queued, you commit it under Pending changes, and the engine deletes the old pass and mails a new one.

Check the result

  1. Open Admin accounts > Admin accounts & TAP. The account is listed with Status Enabled and the TAP column says enforced.
  2. Under Temporary Access Pass, press Check on the admin. It reads the live state of the pass; Sends to shows the address it went to.
  3. If the account is missing, open Jobs > Engine logs & errors and open the latest run’s log.

Undo

  • Before you commit: press Cancel and discard in the wizard, or Cancel all pending on Pending changes.
  • After the account exists: use Remove from PIM or Delete account on the admin’s row; see How to offboard an admin.
  • Undoing the commit under Operations > Commit history & undo takes the admin out of PIM Manager’s records, but the account stays in Microsoft Entra ID: the daily reconcile does not remove or disable admin accounts. See How to undo a commit.

Verified against PIM Manager 3.0.23.3 on Nov 3, 2026Download PDF

← How to onboard a consultantHow to delegate a Power BI workspace →

InvardiaInvardia

See the risk. Control the access.

Products

PIM ManagerSecurityInsightEntra Policy SuiteAll featuresPricingFree 60-day Pro trialBook a demoWhy Invardia

Docs

DocumentationSearch the docsPIM Manager settingsSecurityInsight settingsPIM network guidesCommand wizardNetwork egressPIM Manager design configuratorSecurityInsight design configuratorDesign your installationCalculate your cost

Company

AboutContactCustomer portalSupportHow support worksHow updates reach youSupport in numbersSetup scriptsRemote support accessContact: info@invardia.com

Legal

Terms of saleLicence termsData processingPrivacyCookiesCompany information
© 2026 Invardia – a brand of 2LINKIT, founded and owned by Morten Knudsen · Strandvejen 21A, 6000 Kolding, Denmark · VAT DK39208032 · Contact: info@invardia.com