Ben Hatton
My feedback
-
3 votesBen Hatton
supported this idea
·
-
1 voteBen Hatton
shared this idea
·
-
1,357 votes
We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
Ben Hatton
supported this idea
·
-
1 vote0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
shared this idea
·
-
67 votesplanned · 6 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
78 votesstarted · 8 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
118 votesunder review · 11 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
15 votes1 comment · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
17 votesunder review · 1 comment · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
24 votes6 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
24 votes0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →
We are working with the exchange team to address this. You are correct, the expectation is you are activated immediately.
Ben Hatton
supported this idea
·
-
24 votes1 comment · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
47 votesunder review · 8 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
8 votes
Thank you. We’re working on this.
Ben Hatton
supported this idea
·
-
216 votes
We plan to start work on this in the next 6 months. Please note we don’t have timing on when it would be available for customers.
Ben Hatton
supported this idea
·
-
11 votesBen Hatton
supported this idea
·
-
4 votesBen Hatton
supported this idea
·
-
3 votesBen Hatton
shared this idea
·
-
125 votes
valid suggestion subject to upvote
Ben Hatton
supported this idea
·
-
3 votesBen Hatton
shared this idea
·
This integration is problematic to say the least.
a) consent mechanism by-passes the normal 3rd Party AAD user consent security control;
b) consent UI does not provide full disclosure of what those permission grants mean;
c) permissions granted to linkedin exposes wildly inappropriate sensitive data and takes consent from a person who does not own that data;
d) linkedin branding inside the corporate boundary
e) freely exchanges data between a service designed to protect your information and one that is designed to sell your information
f) on by default (at least in some tenant types?)
For those who haven't looked closely, these are the grants:
People.Read Read users' relevant people lists Allows the app to read a ranked list of relevant people of the signed-in user. The list includes local contacts, contacts from social networking, your organization's directory, and people from recent communications (such as email and Skype).
Calendars.Read Read user calendars Allows the app to read events in user calendars .
So basically Linkedin will have the permissions to find out who you've been meeting and communicating with, and why. And don't forget that they have permission to read any attachments to your calendar events too.
Providing ability to control access to data by third parties is fundamental to OAuth and AAD and this 'functionality' makes AAD a joke. This seriously damages the trust that Microsoft seemed to have been building with Azure and O365 - I wouldn't be surprised to see a run of public Data Breach notifications coming out of companies using O365.
Remove it entirely. This fails all 6 Microsoft Privacy Principals https://privacy.microsoft.com/en-GB/