Using Umbrella Multi-org with Cisco Secure Connect

Automated Key Exchange

The provisioning process will link your Umbrella local organizations to Meraki organizations through the exchange of API keys (tokens). An automated key exchange process will streamline the provisioning process by automatically creating and exchanging API keys between Umbrella and the Meraki dashboard. However, this only works if no API keys have been exchanged before. If you meet any of the following conditions, you can take advantage of the automated key exchange process. Otherwise, you will need to follow the manual process:

1. You do not currently have any Meraki organizations.
2. You will be creating new Umbrella local organizations to be used with Secure Connect.
3. The local organizations to be used with Secure Connect do not have APIs created yet.

You can check to see if keys have been exchanged in Umbrella by going to Admin > API Keys and clicking on Legacy Keys. If you see 0 keys for all the following API types, then you can choose the Automated Key Exchange (see the image below).

• Umbrella Network Devices
• Umbrella Reporting
• Umbrella Management

Provisioning Steps

1. After you receive the Secure Connect welcome email for Multi-org customers, please go to the Multi-Org console.  From the home page, go to the "Org Management" page. Click on the "download" icon located on the top right page.  (See the image below.). This will download a CSV file to your device.

2. Open the CSV file with a spreadsheet application such as Microsoft Excel, Google Sheets or Apple Numbers (see the image below). We will need the information below:

• organizationID (column E) - (required) 
• adminEmail (column M) - (required)   
  • Note: There may be more than one email listed.  If so, please only include the email that is, or will be the administrator for the Meraki org.  If there are more than one email addresses in the cell for a given local organization, the first one will be used for the provisioning process.
• Local Admin Name - (recommended)
  • This information is not in the CSV file.  It is recommended that you add the local admin's First Name (given name) and Last Name (family name) in the column to the right of "adminEmail" column.  
• Enable Automated Key Exchange - (recommended)
  • This information is not in the CSV file.  It is recommended that you add this information to the file in a column to the right of "Local Admin Name" if you provided the admin name or "adminEmail" if you did not.  For each local organization:
    • Put a "Y" in the cell if local organization meets the requirements for Automated Key Exchange process.
    • Put an "N" in the cell if:
      1. The organization does not meet the Automated Key Exchange requirements. 
      2. You are unsure if that organization meets the Automated Key Exchange requirements. 
      3. You prefer to use the manual process. (See the "Automated Key Exchange" section above to learn if you are eligible to use Automated Key Exchange process.) If this information is not provide, the manual key exchange process will be enable.

None of the other information is need for the Secure Connect provisioning process.  You may delete the other columns if you wish.

3. Please email the updated CSV file as an attachment with the following text in the subject field, "<your company or organization name> MO provisioning" to sec-con-mo@cisco.com.

4. After Cisco reviews your email, the standard Secure Connect welcome email will be sent to the local admin for each local organization.

3. Follow the instructions on the standard welcome email to setup your account for that local organization. For more information on the account setup, please visit our documentation using the links below.

• For Automated Key Exchange, click here.
• For Manual Key Exhange, click here.