Why is that.? It appears the generated access_token is defined by the email account you are logged in with, and not by the AppID/ClientSecret/UserID you supply? What can I do to change it? Obviously I can't use Email A from every customer machine I run my application from.there must be a way to make machine B (and any other machine) that runs the application to generate 'the right access_ token' for accessing Drive A on which the application was registered in the Azure Portal? In addition, When I try to use Graph-Explorer from machine B (with the same USERID of OneDrive A I used earlier), this time supplying the access-token I got from machine B application run to verify the results - I again get the dir-list of machine B.įrom the other hand, if I modify the request-headers 'Authorization: Brearer' to be the access token A that I received earlier in machine A, I do get the right dir-list (of Drive A) from machine B.

However, I now go to machine B, login with email B (Which is connected to a different OneDrive B), run my application and get another access-token, this results in a different dir-list than before (Of OneDrive B, and not OneDrive A which I expected to get since that what the application AppId and ClientSecret and USERID I supplied are supposed to be connected to.) I can also verify this using Microsoft Graph-Explorer: using URL: if I set the request headers to 'Authorization: Bearer MY ACCESS TOKEN A', I get Drive A dir-list under my application folder as requested - which is good. I now use machine A, login with Email A, run my application and get a valid access-token, with which I can get a legal dir-list of OneDrive A. I defined an application in my Azure Portal that belongs to OneDrive A (With AppID, Client-Secret, API Permissions.) Say I have two personal OneDrives - OneDrive A (which is connected to Email A on machine A) and OneDrive B (which is connected to Email B on machine B).

Onedrive enterprise download