Best Practices: Ensuring Successful Email Delivery from CloudHealth

Products

• CloudHealth

Issue/Introduction

When using CloudHealth, automated alerts, cost optimization reports, and system notifications are sent from [e-mail]. Due to the data-heavy nature of these emails, corporate firewalls and aggressive spam filters may occasionally flag, delay, or block them from reaching your users' inboxes.

To ensure continuous and reliable delivery of these critical operational insights, your organization's IT or mail administrator should implement the mail server best practices outlined below.

Resolution

To prevent CloudHealth emails from being misidentified as spam, apply the following configurations to your organization's mail server or secure email gateway (such as Microsoft 365, Google Workspace, or Mimecast):

1. Configure Domain Whitelisting

While whitelisting the specific email address ([e-mail]) is a great start, it is best practice to whitelist the entire sender domain.

• Add cloudhealthtech.com to your organization's global inbound Safe Senders or Allowed Domains list. This ensures any other automated or system-generated aliases from the platform are also permitted.

2. Allow the Sending IP Address

If your organization utilizes network-level firewalls or connection filtering that restricts inbound traffic based on source IP addresses, you must explicitly allow CloudHealth's designated outbound mail server IP.

• Add 167.89.104.57 to your mail gateway's connection filtering "Allow" list.

3. Create a Mail Flow / Transport Rule

Automated reports often contain heavy technical data, tables, and links that can inadvertently trigger standard spam keywords. Creating a dedicated rule ensures these emails bypass deep content scanning.

• Set up an organization-wide mail flow rule that identifies incoming mail where the sender domain is cloudhealthtech.com.

• Configure the action of the rule to Bypass Spam Filtering (or set the Spam Confidence Level [SCL] to -1).