User Attributes

Checks that every postal code set on enabled member users is one of your approved values. Blank values are not checked here (the presence tests check those).

Postal codes route mail and deliveries and place users in location-based groups and reports. A postal code that is not one of your offices usually means a typo or an out-of-date address.

The approved values come from postalCode in CLT.UA.AllowedValues under GlobalSettings in maester-config.json (approved office locations count too), from the file named in CLT.UA.AllowedValuesFile, or from this test's own AllowedValues, which replaces the shared list for this test only. Until any are set, this test lists the values it finds and asks you to review them (Investigate) instead of failing.

Remediation action

1. Review the values listed below and decide which are correct.

2. Add the approved values to maester-config.json:

   { "GlobalSettings": { "CLT.UA.AllowedValues": { "postalCode": ["98052", "10001"] } } }
   

3. Change the users with a value that is not approved, in the Microsoft Entra admin center (Entra ID > Users > the user > Edit properties > Contact info > ZIP or postal code) or with PowerShell: Update-MgUser -UserId <UPN> -PostalCode '98052'.

4. For users synced from Active Directory or provisioned from an HR system, fix the value at the source (postalCode in AD), because changes made in Microsoft Entra ID are overwritten at the next sync.

5. If a value is correct but not listed, add it to the approved values rather than changing the user.

Related links

• Add or update a user's profile information
• Manage rules for dynamic membership groups

%TestResult%