Create an Email Address Policy
Applies to: Exchange Server 2013
For a recipient to receive or send email messages, the recipient must have an email address. Email address policies generate the primary and secondary email addresses for your recipients (which include users, contacts, and groups) so they can receive and send email.
When creating an email address policy, you can use the following email address types:
Precanned SMTP email address. Precanned SMTP email addresses are commonly used email address types that are provided for you.
Custom SMTP email address. If you don't want to use one of the precanned SMTP email addresses, you can specify a custom SMTP email address.
When creating a custom SMTP email address, you can use the variables in the following table to specify alternate values for the local part of the email address.
Given name (first name)
Surname (last name)
Uses the first x letters of the surname. For example, if x = 2, the first two letters of the surname are used.
Uses the first x letters of the given name. For example, if x = 2, the first two letters of the given name are used.
Non-SMTP email address. The following types of non-SMTP email addresses are supported:
EX (Legacy DN Proxy Address Prefix DisplayName)
Exchange Unified Messaging proxy address (EUM proxy address)
In Exchange, all non-SMTP email addresses are considered custom addresses. Exchange doesn't provide unique dialog boxes or property pages for X.400, GroupWise, or Lotus Notes email address types. If you add a non-SMTP custom email address, you must have the appropriate dynamic-link library (DLL) files. If you don't provide the appropriate DLL files, you won't be able to create a customized email address policy. The following error will be logged in Event Viewer: "The email address description object in the Microsoft Exchange directory for the 'SADF' address type on 'i386' machines are missing."
For detailed instructions about how to create an email address policy, see the following topics:
What do you need to know before begin?
Estimated time to complete: 5 minutes.
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Email address policies" entry in the Email addresses and address books topic.
Before an SMTP address domain can be used in an email address policy, you must configure an accepted domain. To learn more, see Accepted domains.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
What do you want to do?
Use the EAC to create an email address policy
Navigate to Mail flow > Email address policies, and then click Add .
In Email Address Policy, complete the following fields:
Email address format
Specify the types of recipients this email address will apply to
Click Add a rule to further restrict the recipients that this policy will apply to. This creates a Boolean And statement.
If you apply too many rules, it’s possible to restrict the email address policy to the point that it doesn’t contain any users.
Click Preview recipients the policy applies to to view the recipients that policy will apply to.
Click Save to save your changes and create the policy.
You’ll get a warning that the email address policy won’t be applied until you update it. After it’s created, select it, and then, in the details pane, click Apply.
Use the Shell to create an email address policy
This example creates an email address policy that includes mailbox users in the Southeast offices who will have email addresses that include their last name combined with the first two letters of their first name.
New-EmailAddressPolicy -Name "southeast offices" -IncludedRecipients MailboxUsers -ConditionalStateorProvince "Georgia","Alabama","Louisiana" -EnabledEmailAddressTemplates "SMTP:%firstname.lastname@example.org"
For detailed syntax and parameter information, see New-EmailAddressPolicy.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.