Common Microsoft Planner Integration Errors

This article lists and describes common errors that may occur with the Microsoft Planner integration.

Insufficient privileges to complete the operation

This error indicates that permissions are missing from the Entra Application used to connect to Planner.

The approved application permissions must be verified.

If you are using the default application, then look up App ID: 1d5c336b-c056-4d77-87c2-cdd4428b1a68 in Microsoft Entra.

Correct permissions:

Lifetime validation failed, the token is expired

This error indicates that the token of the user logged into OnePlan expired. Log out of Office 365 and log back again.

If that does not help, please clear your cookies after you log out and log back in again.

AADSTS900144: The request body must contain the following parameter: 'username'

This error indicates that you checked the "Use integration credentials to connect to Planner" checkbox, but you did not enter the username and password for the service account. Fill out the missing configuration.

Invalid value specified for property 'mailNickname' of resource 'Group'...The mailNickname should be between 1 and 64 characters

This error indicates that the plan name is past the character limit of 64 characters. If the plan name is too large, Planner will prevent this item from being created. Please rename the plan in OnePlan to a value that is less than 64 characters long and try again. 

Owner not found. Please make sure a valid owner is set on the plan in OnePlan

This can happen when the owner for the plan in OnePlan is a generic user, or a team (i.e., a resource that does not have an email). The integration will attempt to bring the first owner it finds in OnePlan (as there can be more than one owner to a plan) and bring that resource to Planner (which can only have a single owner). 

If all of the owners for a plan have an email associated to them and the message still appears, please verify that all of the owners have a valid Microsoft Planner license.