Home

Control what the user can give consent to

%3CLINGO-SUB%20id%3D%22lingo-sub-977476%22%20slang%3D%22en-US%22%3EControl%20what%20the%20user%20can%20give%20consent%20to%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-977476%22%20slang%3D%22en-US%22%3E%3CP%3EO365%20and%20OAuth2%20allows%20users%20to%20give%203rd%20party%20apps%20consent%20to%20access%20data%20on%20behalf%20of%20the%20user.%3CBR%20%2F%3EIs%20there%20any%20way%20we%20can%20limit%20the%20%22scope%22%20of%20consent%20the%20user%20allow%20%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESince%20we%20are%20in%20the%20EU%2C%20and%20thus%20hit%20by%20GDPR%2C%20and%20we%20consider%20e-mails%20as%20containing%20personal%20data%2C%20then%20we%20can%20not%20legally%20allow%203rd%20parties%20access%20to%20users%20e-mail%20without%20a%20data%20processor%20agreement%2C%20risk%20assessment%20etc%20in%20place.%20The%203rd%20party%20would%20process%20data.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20can%20get%20the%20granted%20permissions%20on%20a%20per%20user%20basis%2C%20and%20do%20our%20own%20reporting%20and%20followup.%20But%20it%20would%20be%20better%20to%20say%20users%20can%20NOT%20give%203rd%20party%20apps%20any%20sort%20of%20e-mail%2C%20calendar%20and%20Contacts%20(that%20is%20by%20definition%20personal%20data)%20permission.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20can%20disallow%20all%203rd%20party%20apps%20altogether%2C%20by%20tuning%20integrated%20Apps%20off.%20But%20we%20still%20would%20allow%20the%20user%20to%20grant%20simple%20consent%20like%3A%20%22openid%20profile%20email%22%2C%20%22User.Read%20openid%20email%20profile%20offline_access%22%20or%20%22User.Read%22%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-977476%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuthentication%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIdentity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
povlhp
New Contributor

O365 and OAuth2 allows users to give 3rd party apps consent to access data on behalf of the user.
Is there any way we can limit the "scope" of consent the user allow ?


Since we are in the EU, and thus hit by GDPR, and we consider e-mails as containing personal data, then we can not legally allow 3rd parties access to users e-mail without a data processor agreement, risk assessment etc in place. The 3rd party would process data.


We can get the granted permissions on a per user basis, and do our own reporting and followup. But it would be better to say users can NOT give 3rd party apps any sort of e-mail, calendar and Contacts (that is by definition personal data) permission.


We can disallow all 3rd party apps altogether, by tuning integrated Apps off. But we still would allow the user to grant simple consent like: "openid profile email", "User.Read openid email profile offline_access" or "User.Read"

1 Reply
Highlighted

So one thing you can do currently is enforce app permission policies so that by default apps can only get access to some mailboxes: https://practical365.com/exchange-online/application-access-policies-in-exchange-online/

 

You cannot go more granular on the actual app permissions though, so it's either that or disable them altogether. But they did announce that they are working on a "consent" role for Azure AD, which should eventually be able to allow you to delegate permissions to consent, ideally for specific scopes/permissions only. No ETA on that though.