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.

Eric Barnard

My feedback

  1. 1,344 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

    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…

    Eric Barnard supported this idea  · 
  2. 1,163 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

    76 comments  ·  Azure Portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →

    Hey Folks,

    We have made some great progress on this idea and most of our services today do support move resources across groups.

    We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.

    Please file individual asks on each service category present in uservoice and vote for it.

    Thanks,
    Azure Portal Team

    Eric Barnard supported this idea  · 
  3. 245 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  10 comments  ·  Scheduler » Features  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Eric Barnard commented  · 

    I appreciate the clarity on the UTC timing - that makes sense. As far as your questions:

    1) If it's a daily/weekly/monthly job, then I would expect it to be ran at 2:30 am - as a daily job, I expect it to be ran at least once in that interval. If it's a job ran at minute intervals (e.g. every 15 mins), then do as the world does for DST and ignore the intervals going from 1am to 2am by just continuing to execute every 15 mins.

    2) If its a daily job, I would NOT want my job to be called 2x in a 23-hour period ... if I have a 12:30am job and it just executed successfully 1 hour ago - DO NOT EXECUTE it again. I would think one of the most common scenarios for use of the scheduler is not necessarily 'clean up jobs' - but things more like automated email sends and other tasks that would cause my end users confusion. Again though, if the job is on a minute interval, just continue calling on that interval and ignore the fact that it might be the same time all over again.

    I think my point is that jobs that execute on a Daily/Weekly/Monthly type of schedule are very different in their goal from jobs that execute at minute/second level intervals.

    Eric Barnard supported this idea  · 

Feedback and Knowledge Base