Core: 'Microsoft Graph PowerShell' asked for scope 'Tasks.ReadWrite.All' that doesn't exist on the resource

[Maar10tech]

Details of the scenario you tried and the problem that is occurring

When trying Update-M365DSCAllowedGraphScopes -All -Type Update -Environment 'Global' I got the error

Connect-MgGraph : AADSTS650053: The application 'Microsoft Graph PowerShell' asked for scope 'Tasks.ReadWrite.All' that doesn't exist on the resource
'00000003-0000-0000-c000-000000000000'. Contact the app vendor.
Trace ID: 23c55fe0-3ccf-4a59-ab41-e13665e73200
Correlation ID: 4638e2c3-2663-466b-90c5-655972d00f9e

Verbose logs showing the problem

Verbose is fine. Last statement is Connecting to MS Graph to update permissions

Suggested solution to the issue

As the MS Doc shows, the Permission with ".all" ending does not exist.
The Permissions without ".All" refer to exchange and not planner applications

I changed the settings of the planner module as follows (in all files):

{
    "name": "NotSupported",
    "_comment": "Tasks.Read.All - Task.Read is Exchange"
}

And add following to the function Get-M365DSCCompiledPermissionList:

# Update permissions
                        foreach ($updatePermission in $resourceSettings.permissions.graph.$PermissionsType.update)
                        {
                            if ($updatePermission.name -eq "NotSupported"){
								Write-Verbose -Message "Update permission {$($updatePermission.name)} not supported"
								if($null -ne $updatePermission._comment){
									Write-Verbose -Message "Comment: {$($updatePermission._comment)}"
								}
							}
                            elseif (-not $results.UpdatePermissions.Contains($updatePermission.name))
                            {
                                Write-Verbose -Message "Found new Update permission {$($updatePermission.name)}"
                                $results.UpdatePermissions += $updatePermission.name
                            }
                            else
                            {
                                Write-Verbose -Message "Update permission {$($updatePermission.name)} was already added"
                            }
                        }

                        # Read permissions
                        foreach ($readPermission in $resourceSettings.permissions.graph.$PermissionsType.read)
                        {
                            if ($readPermission.name -eq "NotSupported"){
								Write-Verbose -Message "Update permission {$($readPermission.name)} not supported"
								if($null -ne $readPermission._comment){
									Write-Verbose -Message "Comment: {$($readPermission._comment)}"
								}
							}
                            elseif (-not $results.ReadPermissions.Contains($readPermission.name))
                            {
                                Write-Verbose -Message "Found new Read permission {$($readPermission.name)}"
                                $results.ReadPermissions += $readPermission.name
                            }
                            else
                            {
                                Write-Verbose -Message "Read permission {$($readPermission.name)} was already added"
                            }
                        }

The DSC configuration that is used to reproduce the issue (as detailed as possible)

as described above

The operating system the target node is running

Not important

Version of the DSC module that was used ('dev' if using current dev branch)

last release (Install Module)

[SebastianGoers]

I am seeing the same issue and would love to see this fixed .

[Maar10tech]

I am seeing the same issue and would love to see this fixed .

WPS Modules.zip

You can use the suggested solution as a fix / workaround.
Just replace attached files.

[NikCharlebois]

No sure I fully understand the problem at hand. I agree that there is a bug in that the permissions Tasks.Read.All and Tasks.ReadWrite.All do not exist. However, replacing those by the Tasks.Read and Tasks.ReadWrite permissions in the settings.json file will take care of the issue. Not sure why we need to add support for unsupported types.

[SebastianGoers]

I agree, fixing the permissions should be enough to close this issue.