Andy

My feedback

  1. 221 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Networking » Bastion  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  2. 315 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    39 comments  ·  Azure Active Directory » Domain Join  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  3. 15 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  4. 160 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Azure Active Directory » Devices  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback. We are looking into it and evaluating different options for solving the use cases mentioned in this thread. We will update this thread once we have more information to share.

    Andy supported this idea  · 
  5. 935 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    82 comments  ·  Azure Active Directory » Authentication  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback, we’re currently reviewing this capability to see how we can support RADIUS auth on NPS specifically, for AAD Joined Windows 10 devices to authenticate to WiFi access points

    If there are scenarios beyond the above, please provide the details in the comments


    Ravi

    Andy supported this idea  · 
  6. 16 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  System Center Data Protection Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  7. 97 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  8. 60 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks again for the feedback! We currently have a feature in the backlog that allows you to create a VM with an attached disk at the same time. We still need to prioritize it, so there is no ETA at this point of time. If you want to see it sooner, please don’t hesitate to vote this idea!

    An error occurred while saving the comment
    Andy commented  · 

    Hi,

    sorry the word "template" is wrong. For example: I have a self made VM which contains a SharePoint Server. The guys who made this machine had configured a C:\ Drive for OS, a E:\ drive for the application folder and a F:\ drive for SQL database. They do it because they scale performance with that.
    When i put that machine in a DevTestLab, i have to attach the additional drives manually to my VM and copy the data on it, because DevTestLabs machines can only deployed with a single C:\ drive disc.

    Andy shared this idea  · 
  9. 1,307 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Folks,

    Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).

    First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.

    Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this…

    Andy supported this idea  · 

Feedback and Knowledge Base