Following is an example of how CSV file should look like for importing information about Persona and UserLocation static attributes.
MicrosoftId |
Persona |
UserLocation |
b09dd291-c750-58c0-dcb2-2f8958ec5e28 |
Manufacturing |
Austin |
db10c3d2-559c-c180-1997-c01b4830f434 |
Manufacturing |
Zurich |
9f50743a-ff0d-8c8f-d02c-41d5d83e58de |
Manufacturing |
Austin |
b23b70bf-8a34-5158-930a-9aa12eed09d2 |
Manufacturing |
Kiev |
45790ab1-6ccd-cef6-74a5-95ab73cedcbf |
Manufacturing |
New York |
377f9439-0d5e-341f-f52c-190265359578 |
RDD |
Mexico City |
Requirements to the structure of the CSV file:
• The first column needs be named ether MicrosoftId or UserPrincipalName and contain information about user GUID or user principal name as defined in Microsoft Entra (Azure Active Directory).
• Names of the columns should not contain spaces or special characters.
Examples of invalid column names: User Location, R&D
• PowerSuite accepts comma separated CSV file in the Unicode encoding.
TIP
In case and if you need a Static User Attribute name to contain spaces you can create a corresponding Logical Attribute providing the same values as a Static one.