How to manually edit an existing transport rule to add or remove users receiving email signatures
You have configured the connectors for your Microsoft 365 tenant for use with CodeTwo Email Signatures for Office 365. You would like to manually change the scope of users whose messages get signatures by adding or removing specific groups or users.
Changing the scope of users controls whose emails are processed by the CodeTwo Email Azure Service, therefore it also affects which users need licenses. Read this article to learn more about licensing in CodeTwo Email Signatures for Office 365.
It is possible to edit the CodeTwo Exchange transport rule manually and add or remove groups and users whose emails receive signatures. Follow the links below to learn how to:
- Open the transport rule for editing
- Limit the scope of users receiving signatures
- Expand the scope of users receiving signatures
- Add a user to a group in Microsoft 365
Follow these steps to access the transport rule and edit it:
- Open the Exchange admin center.
- Go to mail flow > rules.
- Select the CodeTwo Exchange transport rule and click the Edit button (Fig. 1.).
In the example below, the CodeTwo Exchange transport rule is configured to redirect all emails originating inside the organization to the outbound connector (Fig. 2.). No limit is set, all users receive sigantures.
If you would like to limit the scope of users whose emails receive signatures to a specific group, follow the steps below:
- Open the transport rule as shown here.
- Click the add condition button and select The sender > is a member of this group.
- In the Select Members window choose a group, click add and confirm by pressing OK (Fig. 3.). It is possible to select more than one group of users using this method.
- Click Save to submit changes made to the transport rule.
If some of your groups are not displayed in the picker, you need to add them manually by typing their email address(es) in the text field next to the Check names button and then clicking Check names.
In this case, the CodeTwo Exchange transport rule is configured to only redirect emails originating from a specific group of users inside the organization to the outbound connector (Fig. 4.). Only members of the specified group receive signatures.
There are two ways to allow more users to receive signatures by editing the transport rule:
- Remove the condition limiting the scope of senders to a specific group. This will cause all emails to be processed by CodeTwo Email Azure Service.
- Add further groups to the existing scope of senders.
Make the following changes to the transport rule to remove the condition limiting the scope of senders to a specific group. As a result, signatures will be added to messages sent by all users inside your organization.
- Open the transport rule.
- Find the condition The senderis a member of and remove it by clicking the Remove button (Fig. 5.).
- Submit changes by clicking Save.
Edit the transport rule as shown below to add another group of users to the scope of senders who receive email signatures:
- Open the transport rule as shown above.
- Find the condition The senderis a member of and click on the name of the group name listed next to it e.g. Marketing (Fig. 6.).
- In the Select Members window, choose another group, click add and confirm by pressing OK (Fig. 7.).
- Apply the changes to the transport rule by clicking Save.
In this example, the CodeTwo Exchange transport rule is configured so that emails originating from a specific group of users receive signatures (Fig. 8.).
To add a single user to the group of users already receiving signatures, follow the steps below:
- Open the Microsoft 365 admin center.
- Expand the Groups section in the menu and select Groups.
- Open the group to which you want to add a new user (Fig. 9.).
- Go to the Members tab and click View all and manage members (Fig. 10.).
- Click the Add members to open the user list (Fig. 11).
- Select the user you want to add from the list or use the Search function. Click Save to confirm changes and close the group window (Fig. 12.).