Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Ben Hatton

My feedback

  1. 101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  2. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  3. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  4. 3,300 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    198 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →

    Quick update,

    We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.

    After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.

    We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.

    Thanks for your continued feedback,

    -Adam (Azure Billing Team)

    Ben Hatton supported this idea  · 
  5. 43 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Ben Hatton commented  · 

    FYI there is an export function in the portal that does exactly this, can be run at the subscription level and select to include all child resources. Doesn't work at Management Group though.

    Ben Hatton supported this idea  · 
  6. 133 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton supported this idea  · 
    An error occurred while saving the comment
    Ben Hatton commented  · 

    There are some significant omissions from the ADMSPrivilegedRole commandlets that affect deprovisioning, I hope this can be fed into the development:

    a) There is no remove- commandlet
    b) Limiting resource query to 200 is a potential show stopper - PIM is most useful assigned at resource group level, not subscription level
    c) There is no way to query all eligible assignments for a specific user without a grand iteration through everything

    The best workflow currently possible is to run the export for each subscription through the portal and then manually deprovision each assignment in portal.

    Maybe the microsoft.graph module is a better way to go... Is AzureAD module going to continue to be developed?

  7. 577 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    55 comments  ·  Azure Backup » PaaS Backup  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  8. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  9. 36 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ben Hatton shared this idea  · 
  10. 2,689 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    523 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

    An error occurred while saving the comment
    Ben Hatton commented  · 

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

    Ben Hatton supported this idea  · 
  11. 34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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  · 
  12. 632 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 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  · 
  13. 176 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  8 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  14. 62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  2 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  15. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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  · 
  16. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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  · 
  17. 101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  18. 286 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  7 comments  ·  Networking » Azure Front Door Service  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  19. 275 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  API Management » Defining APIs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Hatton supported this idea  · 
  20. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    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  · 
    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/

← Previous 1 3 4

Feedback and Knowledge Base