Christopher Edwards

My feedback

  1. 94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Site Recovery  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christopher Edwards commented  · 

    Backup should be done from DR data, not separately resulting in duplicated management effort, bandwidth, storage and compute.

    Since the customer is paying for the storage why would you limit to 24 hours! Or 5 days. Backup needs to be folded into DR.

    Christopher Edwards supported this idea  · 
  2. 99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Site Recovery  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  ruturajd responded

    Interesting requirements. We are reviewing this. Will reach out to you for more details. Please use the comments to give more examples.

    An error occurred while saving the comment
    Christopher Edwards commented  · 

    Since the data is already in Azure it shouldn't have to sent all over again to a separate backup provider causing wasted bandwidth, duplicated storage and more on prem compute. Verto gives you 30 days which isn't enough. Quite frankly if you integrated 90 days backup into ASR it would result in more storage account billing for MS.

    Christopher Edwards supported this idea  · 
  3. 64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Networking » Bastion  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christopher Edwards commented  · 

    Yes. I can't believe it's £100 per month for a jump box! And it can only serve one vnet. We have DR sites where we can't tolerate this cost and so creating a Bastion is part of the DR plan.

    Christopher Edwards supported this idea  · 
  4. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Azure Backup » MARS  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christopher Edwards commented  · 

    This is so important!!!

    Christopher Edwards supported this idea  · 
  5. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christopher Edwards commented  · 

    Everything should be in the portal.

    Christopher Edwards supported this idea  · 
  6. 740 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    unplanned  ·  29 comments  ·  Azure Backup » Retention and Storage  ·  Flag idea as inappropriate…  ·  Admin →
    Christopher Edwards supported this idea  · 
  7. 995 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Christopher Edwards commented  · 

    October 2015. Come on chaps.

  8. 1,300 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…

    Christopher Edwards supported this idea  · 

Feedback and Knowledge Base