Allow Access to Planner using Client Credentials Flow
Planner tasks, buckets and plans are apparently not accessible using client credentials flow (app only).
I can access them using code flow authentication, but that's not my requirement (internal web service).
Everything else seems to work - it's just the planner stuff that doesn't (401 unauthorized).
Is there a workaround that doesn't require a user to log in?
What kinds of things are you trying to do that involves Client Credentials?
In one of the comments below, someone mentioned wanting to provide managers an overview of the work in their organization.
For that scenario, did you try using a service account?
Contributing to this. We have a backend API application that should be able to create tasks in multiple customer's planners based on activity in a consumer product.
To handle this case it would now require us to contact hundreds of our clients and guide them through the process of making a user on their AD and then on behalf of which we can add tasks to planner in their environment. This is too heavy process. Being able to create tasks with graph API via Application (client credentials) auth would solve this problem. Thanks
I have created a daily workflow in a server application that creates( and manages ) a sequence of planner tasks. At the moment, I have to start the process manually every day to log in with a client credential whereas I would like to schedule the process to start automatically. Any news on this feature, as it would be greatly appreciated.
Thanks in advance,
Tre`Von McKay commented
We want to connect Azure DevOps to Planner using Client Credentials. Our executive leadership uses planner to track various projects in the business. Rather than disrupt their workflow and force them to learn another tool to track updates we'd like updates on work items in DevOps to push into Planner tasks.
Simply creating a plan can't be done using client credentials.
A service account is possible but I'd rather use this as a workaround rather than a solution - not a fan of giving my app an additional identity to manage.
At some point, it must be expected that a daemon would want to interact with Planner to perform certain tasks (e.g. create plan/update/list plans) and it seems very old school to have to resort to a service account to perform these actions.
Jeff McKay commented
I'm not entirely sure if a "planner" task is the same as an Outlook task, but I have the same problem reading them. I really need to do it via Application authentication, not Delegate authentication (i.e. where the user is required to log in and supply a password). It seems bizarre that Application auth works for other data (email, calendar, contacts) but not tasks. Please upgrade the priority on this.
Frederik Holse commented
Any update on where this lies in the backlog?
Steven Verbeek commented
Any update? Ran into this issue :(
Yeah we need this to support managers overview of tasks across multiple plans, this should be elementary thing from the beginning.
Melissa Guzmán commented
Wender Batista commented
Any Updates, Please?
Krystian Niepsuj commented
Any Updates, Please?
is there any update on this ?
It's the same like this https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/17721166-app-only-support-for-task-api
Please provide an update on this.
Any update on this?
Jimmy Bway commented
Hi, Is there any news on this matter ?
Vlad Kiselev commented
There is no workarounds. It is a fatal problem :-(
Support app-only authentication for the graph api beta version planner tasks