File format
You can synchronize data to the cloud portal from a file source. The table below shows the required format of data in input files for mail, groups, and users. Each field must be separated by a comma, and each mail address, group, or user must start on a new line.
| Fields | Syntax | Type | Other | |
|---|---|---|---|---|
| Mail fields | ||||
| Email address | rfc822 mailbox format Example: joe.smith@acme.com | Text | 
                 Optional Globally unique  | 
            |
| Group fields | ||||
| Group DN | 
                 DN Example: DN=CN=Telesales,OU=Lo ndon,DC=acme,DC=com  | 
              Text | 
                 Mandatory Unique in account  | 
            |
| ,, | Blank | 
                 Two commas, no space between ,, (This field is not used in Groups, but commas must be included.)  | 
              Text | Mandatory | 
| GUID | 
                 Hex string Example: 746B8515-C8FF-C940- 9D905F053CB22D25  | 
              Hex 16 bytes | 
                 Mandatory Unique in account  | 
            |
| Name | 
                 String GroupName (for example, Sales)  | 
              Text | 
                 Mandatory Unique in account  | 
            |
| Group Parents (MemberOf) | 
                 DN Example: CN=Sales,OU=London,DC =acme,DC=com  | 
              Text | 
                 Optional - can be many Unique in account  | 
            |
| Users fields | ||||
| Username DN | 
                 DN Example: DN=CN=JSmith,OU=Lond on,DC=acme,DC=com  | 
              Text | 
                 Mandatory Unique in account  | 
            |
| Extra attribute (use ,, if not required) | Mailalias or ,, | 
                 Mailalias=<email> Can be used for any mail attributes by defining the attribute in the string itself: Proxyaddress=JSmith@acm e.com,joe.smith@acme.com  | 
              Text | 
                 Optional Globally unique  | 
            
| GUID | 
                 Hex string Example: 746B8515-C8FF-C940- 9D905F053CB22D25  | 
              Hex 16 bytes | 
                 Mandatory Unique in account  | 
            |
| NTLM ID | Domain\username Example: Sales\JSmith | Text | 
                 Optional Globally unique  | 
            |
| Primary email | Valid email address Example: joe.smith@acme.co.uk | Text | 
                 Mandatory Globally unique  | 
            |
| Group Parents (MemberOf) | 
                 DN Example: CN=Sales,OU=London,DC =acme,DC=com  | 
              Text | 
                 Optional - can be many Unique in account  | 
            |
A single line in an input file for users would look like this:
<usernameDN>,,<GUID>,<NTLMID>,<Primary email>,<Memberof Group1>,<Memberof
          Group2>,<Memberof Groupn>
Within each field, any backslashes or further commas must be escaped, using hexadecimal code \0x002c for a comma, and \0x005c for a backslash. For example:
dn=CN=Joe.Smith\0x002cOU=Salesoffice\0x002cDC=acme\0x002cDC= com, ,
746B8515-C8FF-C940-9D905F053CB22D25,acmenet\0x005cjsmith,smith@acme.com, 
CN=Sales\0x002cOU=salesoffice\0x002cDC=acme\0x002cDC=com, 
CN=USemployees \0x002cDC=acme\0x002cDC=comIf you use the mailalias option, any commas in the alias list must be “double escaped,” with the escape character escaped itself. For example:
mailalias=JSmith@acme.com,J.Smith@acme.co.ukmust be written:
mailalias=JSmith@acme.com\0x005c0x002cJ.Smith@acme.co.ukThe full line in the input file would look like this:
dn=CN=Joe.Smith\0x002cOU=Salesoffice\0x002cDC=acme\0x002cDC= com, 
mailalias=JSmith@acme.com\0x005c0x002cJ.Smith@acme.co.uk,
746 B8515-C8FFC940-9D905F053CB22D25,acmenet\0x005cjsmith,smith@acme.com, 
CN=Sales\0x002cOU=salesoffice\0x002cDC=acme\0x002cDC=com, 
CN=USemployees \0x002cDC=acme\0x002cDC=com