MS Power Automate for additional MS Planner functions - Part 2

[suchona.kani.z]

In the first part of my blog post on recurring Planner tasks, I showed you how to set it up. I used specific connectors. The specific connectors are very user-friendly and intended for a specific purpose.

If the requirements go beyond the intended purpose, it is worth taking a look at the MS Graph API in conjunction with the http connector in Power Automate. This occurs when adding and/or changing categories of a Planner task. The standard connector can set these, but a check expression is required for each of the current 25 categories. In addition, adjustments ecuador consumer email list are required if MS introduces additional categories. The higher setup effort speaks against using the Graph API or the http connector. In addition, adjustments must be made in Azure AD, which can be a challenge in larger organizations. In this respect, one can conclude that the solution is somewhat over-engineered for this use case. However, the Graph API is very powerful and can be used with Power Automate in a similar way, as described below. The solution therefore has high reuse potential. In my opinion, a concrete, comparatively simple use case is also better suited to explaining the interaction of the two components than an abstract and/or more complex use case.

Add categories to tasks
In the Create Task connector, the value True can be set individually for each of the currently 25 categories if the category is to be used for the task. This structure is a homage to the 90s of IT in terms of both data technology and control. To solve this problem efficiently, I use the MS Graph API in conjunction with the http connector. In order to use this, a few requirements must be met:

A new app must be registered in Azure AD and permissions for the required APIs must be granted
An app secret must be created in Azure AD and the data must be saved in the preferred password app when created (there is no longer any access to this data afterwards)
A user account must be created in AD and the user must be entered as the owner in the app registration. The reason for this is that the required Graph API does not currently support the Application permission type, so a user account is required.
To recreate this flow, you can replace the connectors for creating and changing the Planner task with the http connector.