Ben Hatton

My feedback

  1. 494 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    44 comments  ·  Azure Backup » PaaS Backup  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  5. 1,557 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    328 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →

    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 groups

    Ben Hatton commented  · 

    CAB provided that C means Teams membership supports nested security groups as members.

    Ben Hatton supported this idea  · 
  6. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  7. 151 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →

    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  · 
  8. 54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  1 comment  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  9. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  1 comment  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  10. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  11. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton shared this idea  · 
  12. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  13. 224 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  6 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  14. 334 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  12 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  15. 156 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton supported this idea  · 
  16. 207 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  API Management » Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  17. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Active Directory » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
    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/

  18. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton shared this idea  · 
  19. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  20. 86 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton supported this idea  · 
← Previous 1 3 4 5

Feedback and Knowledge Base