Forum Discussion
How did LinkedIn get the permission to access my AAD profile?
Today I noticed that LinkedIn has been granted permission to share my “profile and connection data” on my AAD profile page. I don’t remember having authorized LinkedIn to do so. I c...
Hi All, I've just come across this thread.
We identified a bug in the profile user interface that incorrectly displayed a settings control for a feature that is not available. No permissions were granted. The option is not functional and there is no effect if you attempted to take action. We've rolled back the UI changes and removed the button.
I see it too. I also see it for Azure AD accounts in my demo tenant that have no LinkedIn presence at all.
Interestingly I do not see a reciprocal permission in my LinkedIn privacy settings (i.e. I haven't explicitly allowed LinkedIn to share information with Microsoft/Office 365).
The wording suggests that it's Microsoft using LinkedIn profile info, not LinkedIn gaining access to Azure AD/Office 365 info, but still, it's an unwelcome surprise.
I added some more thoughts here.
https://practical365.com/blog/linkedin-data-sharing-microsoft/
The wording is odd. I don't know why the permission appears in Azure AD when it seems to be saying that LinkedIn will be allowed to share data with Microsoft, not vice versa.
That said, in my blog post above I found a couple of snippets from the LinkedIn privacy policy that arguably provide consent for the sharing of our LinkedIn data with Microsoft, or at the very least that they have legitimate access to it as part of their acquisition of LinkedIn.
Hi All, I've just come across this thread.
We identified a bug in the profile user interface that incorrectly displayed a settings control for a feature that is not available. No permissions were granted. The option is not functional and there is no effect if you attempted to take action. We've rolled back the UI changes and removed the button.
I've updated my blog post with that info. Still, nobody developed that UI element, wrote the text for it, and shipped code, for a non-existent feature. Obviously something is being developed. I hope when it resurfaces there will be a lot more transparency.