Anonymous

My feedback

  1. 328 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    Anonymous commented  · 

    The size of the 128 kb is ridiculously small. Due to this our entire move to the cloud for an active/paying customer has been on halt. In the meanwhile, if Microsoft support members can simply help the existing Azure customers by updating these parameter value in our WAF instance (within our subscription) then atleast we could go live and continue moving to Azure.

  2. 1,219 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…

    Anonymous supported this idea  · 

Feedback and Knowledge Base