Using Microsoft Planner with CodeTwo software
This article explains how to use Microsoft Planner with CodeTwo Email Signatures for Office 365.
- A short introduction to Microsoft Planner
- Does CodeTwo Email Signatures for Office 365 support Microsoft Planner?
- How to add dedicated signatures to Microsoft Planner messages
- How to turn off email signatures in Microsoft Planner comments and notifications
Microsoft Planner is a Microsoft 365 web app that helps you manage your workflow by creating plans with tasks and assigning people/teams to collaborate on them. You can set task deadlines and conveniently review the work progress inside each of your plans. The app can be accessed from the app launcher in the Microsoft 365 portal.
When you create a plan, a new associated Microsoft 365 group is created. If you add users to this plan, they are also added to the connected Microsoft 365 group.
Microsoft Planner can send email notifications whenever you create or modify a task in a plan, for example when you add a new comment. Each notification is sent to the email address of the Microsoft 365 group assigned to this plan (and, depending on the case, also to other people in the plan/task), with the person who created/modified the task as the email sender. To enable task-related notifications for a plan, you need to open it, click the ellipsis (...) button and go to Plan settings. A new window opens, where you can turn on email notifications, as shown in Fig. 1.
Yes. Signatures can be added to:
- email notifications sent to the Microsoft 365 group when a plan member creates/modifies a task (if this has been enabled in the task settings in Planner),
- email notifications sent to plan members when a comment is added to a task,
- comments displayed in the tasks in Microsoft Planner.
Such emails and comments sent automatically from a user mailbox will include a signature if the conditions of a signature rule defined in our program are met.
Microsoft Planner does not support images added to comments. If you want to use a signature, make sure it does not contain any graphic elements. Every image will be replaced by a box with X as shown in Fig. 2.
It is possible to use a dedicated signature template for use in Planner. When set up, this signature will be applied to Planner comments and to notifications sent to users’ mailboxes. Make sure to keep it simple and concise. If a signature is too complex, it can make following conversations in Planner more difficult. Adding a dedicated signature for Planner messages requires taking the following two steps:
- Configure a transport rule in the Exchange admin center
- Configure a signature rule in CodeTwo Email Signatures for Office 365
Additionally, you can create a client-side signature rule for messages sent to Planner from the Outlook desktop app:
The following steps will allow you to start using Planner-specific signatures in Planner comments and notifications. However, if a user answers a Planner comment or notification by sending a message directly from their email client, it will receive the default signature of this user, not the Planner-specific one. This happens because Exchange Online processes such messages as normal emails, not as Microsoft Planner messages and the new transport rule will not apply to them.
To create a transport rule for processing messages from Microsoft Planner:
- Open the Exchange admin center.
- Go to Mail flow > Rules.
- Click the New (+) button and select Create a new rule from the drop-down list, as shown in Fig. 3.
- In the new rule window, enter the name of your rule.
- Under the Apply this rule if heading select The sender is located and choose Inside the organization in the select sender location window and confirm (Fig. 4.).
- Click More options > add condition and select A message header > includes any of these words.
- Enter the header X-MS-TrafficTypeDiagnostic and the phrase PlannerComment as shown in Fig. 5. and save.
- Under the Do the following heading select Apply a disclaimer to the message > append a disclaimer.
- Enter a phrase that will be used by the CodeTwo signature rule to identify messages sent from Planner e.g. This message was sent from Planner and select Ignore from the specify fallback action list as shown in Fig. 6.
- Click Save to create the new rule.
- Move the newly created transport rule up the rules list, so that it is processed before the CodeTwo Exchange transport rule (Fig. 7.).
Create a signature rule for adding signatures to Microsoft Planner comments and notifications by following the steps below:
- Log in to app.codetwo.com.
- Click the Add a new email signature rule button () and select Add server-side signature rule from the list.
- Name the rule accordingly in the Overview tab.
- Go to the Senders tab and select Add > All Senders (or configure a group of senders, depending on the configuration of your environment).
- Go to the Recipients tab and click Add > All Recipients.
- In the Keywords tab, click Add (Fig. 8., item 1) to open the Add phrase window.
- Enter the same phrase you used while creating the transport rule in the Exchange admin center e.g. This message was sent from Planner (Fig. 8., item 2).
- Select Email body from the Search in list.
- Select Remove this phrase from email subject and body. Click OK to confirm.
- Go to the Design tab and click Edit signature. In the editor, create your signature template for Microsoft Planner. See this article for more details on how to use the signature template editor.
- Back in the signature management app, use the arrow buttons to move the new signature rule up the list and place it above the more general signature rules (Fig 9.). This way, it will be processed before them.
- Click () to save and submit changes to CodeTwo Azure service.
If everything is set up correctly, you should see the same Planner-specific signature in the messages in your email client as well as in Planner itself as shown in Fig. 10.
If your organization is using CodeTwo Email Signatures for Office 365 in combo-mode, you can create a Planner message signature for Outlook desktop app users. This way, they will have the option to manually add a signature that is suitable for use in Planner when answering comments from their email client.
To learn how to create a client-side signature, read this article.
In this case, we recommend using the same template for client-side and server-side messages as shown in Fig. 11. To learn how to copy templates between signature modes, read this article.
Remember, that if this signature is not set as the default signature in Outlook, the user will have to manually select it every time when replying to a Planner comment or notification using the email client.
If you use CodeTwo Email Signatures for Office 365 and you don't want the software to add signatures to comments and email notifications in Microsoft Planner, follow the steps presented in this article.
I receive a non-delivery report for notifications sent by Microsoft Planner when I create/modify a task
Let us say that one of your users, Adele V., receives a non-delivery report (NDR) in OWA when she creates a task in the Planner group - private 2 plan (Fig. 12.).
This problem is probably caused by incorrect settings of the Microsoft 365 group connected with the Planner group - private 2 plan.
To verify if your group is configured properly, try sending a normal email from the affected user account to the Microsoft 365 group connected with your plan. If you receive a non-delivery report again, this means that the problem is not related to Microsoft Planner. You need to check the delivery management settings of your group:
- Sign in as an admin to your Exchange admin center.
- Go to recipients > groups, select the Microsoft 365 group connected to your plan and double-click it (or use the pencil button) to edit it.
- Select delivery management and check the Reject messages from list (Fig. 13.). If the list contains the user that receives NDRs (see Fig. 13.) or any other users that are members of this group, you should remove them. Otherwise, these users will receive NDRs whenever they send email to this group or create/modify a task in the associated plan in Microsoft Planner.