Martijn Loeffen

My feedback

  1. 4,509 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    190 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 
  2. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 
  3. 27 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thanks for reporting this!

    I know it was reported quite some time ago, and we do apologize for the delay in responding to this and getting it addressed.

    For now, there are two options to work around this:

    1. Using Azure AD PowerShell, you can disable and then remove the app role. I’ve posted a sample script which does this here on StackOverflow: https://stackoverflow.com/a/47595128/325697

    2. An alternative option is to use the Azure AD Graph Explorer and issue two PATCH requests on the Application object. The first PATCH request should set the app role’s isEnabled attribute to “false”. The second PATCH request can then remove the app role (i.e. include all existing app roles except the disabled one).

    / Philippe Signoret

    Martijn Loeffen supported this idea  · 
  4. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 
  5. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  (General Feedback)  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 
  6. 130 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Azure Cosmos DB » Other  ·  Flag idea as inappropriate…  ·  Admin →
  7. 462 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 
  8. 249 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. We agree, and we’re looking into doing this in the next calendar year.

    In the interim, if credit card limits are a concern, you do have the option to pay by check or wire transfer. Please contact Support to get this set up.

    - Azure billing team

    An error occurred while saving the comment
    Martijn Loeffen commented  · 

    Seeing it was first planned for 2016 and then for 2017, is this still planned for 2017? We really want to move away from creditcard and pay using Direct Debit, just as we currently do with Office365.

  9. 35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Martijn Loeffen supported this idea  · 

Feedback and Knowledge Base