System administrators configure default settings for both the outbound and inbound emails servers used to send system notifications. Systems administrators can create only one of each type of server that appears as the default for all tenants. If tenant administrators do not override these settings before enabling notifications, vRealize Automation uses the globally configured email server.

vRealize Automation sends notification emails over SMTP. These emails include notification of machine creation, expiration, and the notification of approvals received by users. vRealize Automation supports both anonymous connections to the SMTP server and connections using basic authentication. vRealize Automation also supports communication with or without SSL.

You assign a global, inbound email server to handle inbound email notifications, such as approval responses.

The email server provides accounts that you can customize for each user. Each tenant can override these settings. If tenant administrators do not override these settings before enabling notifications, vRealize Automation uses the globally configured email server. vRealize Automation supports both the POP and the IMAP protocols, with or without SSL certificates.

Table 1. Design Decisions on Email Server Configuration for vRealize Automation

Decision ID

Design Decision

Design Justification

Design Implication

SDDC-CMP-026

Configure vRealize Automation to use a global outbound email server to handle outbound email notifications and a global inbound email server to handle inbound email notifications, such as approval responses.

Requirement to integrate vRealize Automation approvals and system notifications through emails.

You must prepare the SMTP/IMAP server and necessary firewall access and create a mailbox for inbound emails (IMAP), and anonymous access can be used with outbound emails.