Authentication of OneDrive not working in Microsoft 365 organization

[AleixMT]

Hello everyone,

I have been working happily with OneDrive for Linux for some time. Recently, a new coworker joined our team and he needed to use OneDrive for Linux too. We are finding the authentication impossible in his workstation. Our sys admin has access to the Microsoft administration board and has tried many ways to accept the authentication of OneDrive for Linux from the Linux desktop of my team mate, but those ways were unsuccessful.

When accessing the URL displayed by OneDrive for Linux when doing an authorization, we get this screen:

My team mate is using Ubuntu 24.4.01 and using the latest version (2.5.9). He is trying to connect OneDrive for Linux to a Sharepoint unit. The package he is using is from Docker, particularly he is using the same image as me: driveone/onedrive:latest. The account type is Business / Office 365. The file system that the OneDrive for Linux is using is Local.

We have been in this situation for months and we can not fix it. We think that the problem comes from the security policies of my organization, but we would like some instructions on how to change them or which one to change in order to get the authentication that my team mate needs.

If someone knows about how to authorize OneDrive for Linux in our situation please give us some hints.

[AleixMT]

@MARIO31XD

[abraunegg]

@AleixMT , @MARIO31XD

Please get your Azure administrator to raise a Microsoft support request to assist you. This is your best avenue of support for Microsoft Authentication issues.

Most probable scenarios:

1. User consent is disabled and admin consent wasn’t granted

   • In Entra ID, “Users can consent to apps” is disabled, so users can’t approve multi-tenant apps like the OneDrive Linux client.
   • If your admin hasn’t explicitly granted admin consent for the app ID you use, they’ll see an error or “needs admin approval” style page.

2. Conditional Access or app restriction

   • Some orgs only allow certain “approved” apps or require that apps be assigned to specific users/groups.
   • If you’re in an allowed group and your coworker isn’t, they get blocked even though it works for you.

What your Microsoft 365 / Entra admin should check

1. User consent settings

   • Go to: Entra ID → Enterprise applications → User settings / Consent and permissions.
   • If “Users can consent to apps accessing company data on their behalf” is disabled, then your coworker cannot approve the OneDrive Linux client themselves.
   • In that case, the admin must either:
     • Temporarily allow user consent, or
     • Keep user consent disabled but explicitly grant admin consent for the app (see next point).

2. Enterprise application entry for the OneDrive Linux client

   • Under Entra ID → Enterprise applications → All applications, search for the app that corresponds to the OneDrive Linux client (using its Application ID / name, as documented).
   • Once found, the admin should:
     • Check Status (not disabled).
     • Check whether “User assignment required” is enabled; if so, ensure your coworker’s user account or a group they are in is assigned to the app.
     • Under Permissions, grant admin consent for the requested permissions to the organisation.

3. Conditional Access policies

   • In Entra ID → Protection → Conditional Access, look for policies that:
     • Block sign-in from Linux / non-compliant devices, or
     • Restrict sign-in to a set of “approved” applications.
   • Check whether these policies apply to your coworker but not to you. That would explain why it works on your account but not on theirs.

If your admin refuses to allow the default multi-tenant app, the alternative is to:

• Register a dedicated application in your own tenant, granting it the appropriate Graph permissions, and
• Configure the client with your own application_id (and, if needed, azure_tenant_id) as described in the documentation.

However, that is extra work on their side and is only necessary if your Azure Admin does not want to use the standard registration

[AleixMT]

Dear Abraunegg, thank you so much for your support and the time to write this answer, we will work on this issue and get back to you as soon as we fix this.

[AleixMT]

Dear @abraunegg, our system administrator has fixed the issue. The problem was on his side.

Microsoft support was not helpful at all, they just said that they do not support your application...

I do not know what our system administrators did. I asked them so that I can get back to you and give you this information, so that other users do not suffer from the same system administration bug, but the explanation did not identify the problem or explain how to implement a solution.

I am sorry for not being able to give any more information on the issue.

Since the issue is fixed, I am going to close this discussion.

Thank you so much again for your help and your time for implementing and maintainaing this wonderful software.