Maester 
MP.CLT.ADUA.1022 Active Directory business phone numbers are on the approved list.
Checks that every business phone number (telephoneNumber) set on enabled Active Directory users is one of your approved values. Blank values are not checked here (the presence tests check those).
Where every user shares an office main number, the business phone should be one of those numbers. A value typed slightly differently puts the user outside every group, rule and report built on the approved spelling.
The approved values come from telephoneNumber in CLT.ADUA.AllowedValues under GlobalSettings in maester-config.json, from the file named in CLT.ADUA.AllowedValuesFile, or from this test's own AllowedValues, which replaces the shared list for this test only. When neither CLT.ADUA setting is set, the User Attributes pack's CLT.UA.AllowedValues is used, so one list can serve both packs. Until any are set, this test lists the values it finds and asks you to review them (Investigate) instead of failing.
Remediation action
Review the values listed below and decide which are correct.
Add the approved values to
maester-config.json:{ "GlobalSettings": { "CLT.ADUA.AllowedValues": { "telephoneNumber": ["+14255550100", "+14165550100"] } } }Change the users with a value that is not approved, in Active Directory Users and Computers (the user > General > Telephone number) or with PowerShell:
Set-ADUser -Identity <sAMAccountName> -OfficePhone '+14255550100'.If the value comes from an HR system or a provisioning tool, fix it there, or the next import overwrites your change.
If a value is correct but not listed, add it to the approved values rather than changing the user.
Related links
- Set-ADUser
- Telephone-Number attribute (Active Directory schema)
- Attributes synchronized to Microsoft Entra ID by Microsoft Entra Connect
%TestResult%