Schmid, Volker

My feedback

  1. 88 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Azure Active Directory » End user experiences  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  2. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  3. 125 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    29 comments  ·  Update Management » Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Update Management » Scheduling  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

    Schmid, Volker supported this idea  · 
  5. 40 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Update Management » Assessments  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  6. 25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Update Management » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Schmid, Volker commented  · 

    I want the patches to be applied after the state of the first cluster node is good again. Let the mechanism talk to the cluster-aware update component.

    Schmid, Volker supported this idea  · 
  7. 85 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  8. 21 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  9. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Update Management » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  10. 74 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  11. 171 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Schmid, Volker supported this idea  · 
  12. 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…

    Schmid, Volker supported this idea  · 

Feedback and Knowledge Base