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 settings · Settings > Naming conventions

AdminAccountPatterns (how admin accounts are recognised)

KeyNamingConventions.AdminAccountPatterns
WhereSettings > Naming conventions
TypeList
DefaultAdmin-, x-Admin, g-Admin
FeatureNaming that matches your organization · Community, Pro Business, Pro Enterprise, Pro MSP

What it does

The name starts that identify an admin account. The engine reads admin accounts from your tenant only where the user name starts with one of these, so ordinary users are never in scope. Tokens are allowed; only the part before the first unknown token is used.

When set

When set: on the next engine run every account starting with a listed prefix is treated as an admin account. The engine always ALSO adds the starts of the two admin patterns and the shipped prefixes (Admin-, x-Admin, g-Admin), so you can widen recognition but not narrow it below those. Admin accounts with no row are reported as unmanaged, never disabled. On a managed tenant these prefixes are compared with incoming admins and a mismatch is reported.

When blank or default

When blank: the starts of the two admin patterns plus the shipped prefixes are used. If no prefix can be found at all, the engine refuses to read admins rather than scan every user.

Risk and how to reverse it

A too-broad prefix (e.g. a-) pulls ordinary users into the admin set; the engine then stops the run instead of acting on them. Accounts your rows name are always managed, whatever their name. Reversible: restore the old list; the next run uses it.

Requires

SuperAdmin in PIM Manager. Free (Community). The engine identity needs User.Read.All to read the matching accounts.

Recommended

Leave it at the default unless you have existing admin accounts with another naming; then add their exact prefix, as specific as possible.

Related settings

  • Admin account domain AdminAccountUpnSuffix
  • Prefix by admin type NamingConventions.AdminTypePrefixes
  • Suffix by environment NamingConventions.EnvironmentSuffixes
  • Service names NamingConventions.ServiceNames
  • Admin word NamingConventions.AdminWord
  • Tenant common name NamingConventions.TenantCommonName
  • AdminAccountPattern (admin account name) NamingConventions.AdminAccountPattern
  • AdminAccountPatternHighPriv (high-privilege admin name) NamingConventions.AdminAccountPatternHighPriv
  • AdminAccountDisplayNameSuffix (admin display name) NamingConventions.AdminAccountDisplayNameSuffix
  • AdminTypeDefault NamingConventions.AdminTypeDefault
  • EnvironmentDefault NamingConventions.EnvironmentDefault
  • ResourceGroupPattern (permission group name) NamingConventions.ResourceGroupPattern

Documented for PIM Manager 3.0.70. Written by the PIM Manager team; Invardia publishes it. · All settings · Security review pack

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