Ben Hatton
My feedback
-
544 votes
Update: We have initiated the work on enabling backup for blob storage and is underway, ETA: End of Q3CY20.
For more details, please reach out to AskAzureBackupTeam@microsoft.com
Ben Hatton
supported this idea
·
-
2 votes0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
shared this idea
·
-
13 votesstarted · 0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
shared this idea
·
-
1 vote0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
shared this idea
·
-
1,904 votes
We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.
Use case A: nested group in a cloud security group inherits apps assignment
Use case B: nested group in a cloud security group inherits license assignment
Use case C: nesting groups under Office 365 groupsAn error occurred while saving the comment Ben Hatton
supported this idea
·
-
21 votesBen Hatton
supported this idea
·
-
293 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Ben Hatton
supported this idea
·
-
96 votestriaged · 3 comments · Networking » Azure Front Door Service · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
24 votesBen Hatton
supported this idea
·
-
10 votesBen Hatton
supported this idea
·
-
6 votesBen Hatton
shared this idea
·
-
79 votesBen Hatton
supported this idea
·
-
255 votesstarted · 7 comments · Networking » Azure Front Door Service · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
227 votesstarted · 19 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
219 votes
Please consider using OData-to-OpenAPI converters like this one https://github.com/oasis-tcs/odata-openapi. Additional converters can be found on https://openapi.tools.
Ben Hatton
supported this idea
·
-
3 votesBen Hatton
supported this idea
·
An error occurred while saving the comment Ben Hatton
commented
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/
-
1 voteBen Hatton
shared this idea
·
-
1 vote0 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
shared this idea
·
-
108 votesstarted · 7 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
-
105 votesstarted · 11 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Ben Hatton
supported this idea
·
CAB provided that C means Teams membership supports nested security groups as members.