Onedrive and Azure Enterprise Application requested permissions differ depending on method used

What is the problem you are having with rclone?

I am trying to get Onedrive to work with rclone but keep getting the “Admin Privileges Required” problem.

When adding rclone as an Enterprise Application to Azure using

https://login.microsoftonline.com/<tenantid>/adminconsent?client_id=b15665d9-eda6-4092-8539-0eec376afd59

it only adds/requests

Files.Read, Files.Read.All, Files.ReadWrite, Files.ReadWrite.All, User.Read

but if I run the rclone client it adds/requests

Files.Read, Files.ReadWrite, Files.Read.All. Files.ReadWrite.All, Sites.Read.All, offline_access

These are the permissions that are required for Onedrive and rclone to work, but our Azure Admin wishes to use the

https://login.microsoftonline.com/<tenantid>/adminconsent?client_id=b15665d9-eda6-4092-8539-0eec376afd59

way to approve the permissions that need admin approval. They do not want to authenticate using the rclone client.

Do you know what would be causing the difference in requested permissions?

Run the command 'rclone version' and share the full output of the command.

rclone v1.60.1-DEV
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.14.0-33-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.2
- go/linking: dynamic
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Onedrive for Business

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone config

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.


A log from the command that you were trying to run with the -vv flag


welcome to the forum,

that is a many years old, custom compiled, dev version of rclone from an out of date repository..

should rclone selfupdate and test again.
or
uninstall that ancient version and then https://rclone.org/install/#script-installation

I have upgraded to:

rclone v1.71.2
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.14.0-33-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.25.3
- go/linking: static
- go/tags: none

but still have exactly the same issue.

Thanks,

Ian.