For Bloomberg administrators and MCO eComms administrators.
Before you begin
Confirm your organization has a Bloomberg Anywhere subscription.
Confirm Bloomberg has enabled an SFTP site with Daily Delivery File for your organization.
Confirm you can access the Bloomberg Enterprise Console.
Confirm you have an MCO Implementation Manager or MCO Support contact for setup.
Confirm the Bloomberg Mail and Instant Bloomberg users who need to be captured.
Confirm each user’s Bloomberg email address or Instant Bloomberg handle.
Configure Bloomberg SFTP delivery
Bloomberg delivers encrypted communications files to MCO through Secure File Transfer Protocol (SFTP). You configure this delivery in the Bloomberg Enterprise Console.
Contact your MCO Implementation Manager and request a Pretty Good Privacy (PGP) public key.
MCO generates a unique key pair. MCO keeps the private key for decryption and provides the public key for Bloomberg.
WARNING! Do not request or use a passphrase. Bloomberg does not require a passphrase with the PGP key. Providing one can cause setup errors.
Send the MCO PGP public key to Bloomberg Customer Support.
Bloomberg loads the key into your account and uses it to encrypt the communications files that are delivered to the SFTP site each day.
In the Bloomberg Enterprise Console, add the MCO IP address to your account allowlist:
52.213.81.24
Bloomberg accepts SFTP connections only from allowlisted IP addresses. MCO uses this IP address to retrieve your files each day.
Provide your Bloomberg SFTP username to MCO.
Ask your Bloomberg administrator to load the MCO Secure Shell (SSH) public key into your Bloomberg Enterprise Console account.
MCO uses SSH key authentication to connect to Bloomberg SFTP.
Confirm the SSH public key meets Bloomberg requirements:
RequirementValueTypeSSH-RSAStrength4,096-bitFormatOPENSSH, single-line
Confirm with Bloomberg that the SFTP site, PGP encryption, IP allowlist, and SSH key authentication are active.
Operational notes
Topic | Detail |
Bloomberg URLs | Use the Bloomberg Enterprise Console at http://console.bloomberg.com. For China, use http://console.blpprofessional.com. |
File retention | Bloomberg deletes SFTP files on a rolling 7-day basis. If the connection is interrupted for more than 7 days, files may no longer be recoverable from Bloomberg. |
Setup timeline | Bloomberg may deactivate and delete inactive SFTP sites after 6 months of inactivity. Complete configuration steps promptly after the SFTP site is created. |
Enterprise Console access | Bloomberg requires at least 2 active users with access to each connection in the Enterprise Console. Keep these contacts current so Bloomberg notifications are received. |
MCO daily pull window | MCO connects daily to retrieve files. If you notice missing Bloomberg data in MCO eComms, contact your MCO Implementation Manager before the 7-day retention window closes. |
SSH authentication | Bloomberg no longer supports password-based SFTP authentication. SSH key authentication is required. |
SSH key expiry | SSH keys do not expire. |
PGP key expiry | PGP keys expire every 2 years. MCO tracks key expiry and provides a replacement public key before expiration. Forward the replacement key to Bloomberg Support and do not retire the old key until Bloomberg confirms the new key is active. |
Map users to Bloomberg identities
Mapping users to their Bloomberg identities allows MCO eComms to associate captured Bloomberg communications with the correct user profiles.
Without source mappings, captured Bloomberg communications may not be attributed to users and the correct retention and detection policies may not apply.
Sign in to MCO eComms as an administrator.
Go to Settings > Users. The Users page opens.
Locate the user you need to map.
Click Edit. The user profile opens.
Locate the Sources section.
Click Edit in the Sources section. The section enters edit mode.
Click Add Source. A new source mapping row appears.
In Source name, select the following options:
Use Bloomberg for Bloomberg Mail communications. Use Bloomberg IB for Instant Bloomberg communications.
In Unique Identifier, enter the user’s Bloomberg email address or Instant Bloomberg handle.
Click the check icon. The source mapping row is saved in the profile editor.
Add any additional Bloomberg or Instant Bloomberg identities required for the user.
Click Save. MCO eComms saves the user profile.
Bloomberg identity formats
Source type | Unique identifier format | Example |
Bloomberg | Bloomberg email address | |
Bloomberg IB | Instant Bloomberg handle or username |
NOTE: New source mappings apply to newly arriving messages only. They do not retroactively apply retention and detection policies to messages already in MCO eComms. Add mappings before go-live when possible.
Result
Bloomberg delivers encrypted Bloomberg Mail and Instant Bloomberg files to the configured SFTP site each day. MCO eComms retrieves the files, decrypts them, and imports supported communications into the archive.
After users are mapped, newly arriving Bloomberg communications are associated with the correct user profiles. The users’ retention and detection policies apply to future Bloomberg Mail and Instant Bloomberg communications.