Aleksander Pawlak

My feedback

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

    We’ll send you updates on this idea

    Aleksander Pawlak supported this idea  · 
  2. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aleksander Pawlak shared this idea  · 
  3. 47 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aleksander Pawlak supported this idea  · 
  4. 26 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aleksander Pawlak supported this idea  · 
  5. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Aleksander Pawlak shared this idea  · 
  6. 365 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  40 comments  ·  Azure Key Vault » Managing application secrets  ·  Flag idea as inappropriate…  ·  Admin →
    Aleksander Pawlak supported this idea  · 
  7. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
  8. 71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » VPN Gateway  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Scott,

    Thanks for the feedback – totally understand the pain points and confusion. There are a couple of constraints on the Azure side and also specifically with VPN. The key issue is this is for packets coming over the Internet which we can only assume total packet size of 1500 bytes max. Azure SDN platform performs additional encapsulation on the packets within our datacenter networks, so it will be subtracted from there.

    1. On the Azure VPN gateways, the recommendation is to set TCP MSS clamping to 1350; or if not possible for your device, then set MTU to 1400 bytes on the IPsec tunnel interface. We had updated/clarified the Azure documentation to call that out.

    2. Changing MTU currently is not possible from the Azure VPN gateways. We will take it into configuration, but it will not be possible in the short term due to the scale…

    Aleksander Pawlak supported this idea  · 
  9. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Search  ·  Flag idea as inappropriate…  ·  Admin →
  10. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  11. 1,528 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Azure Search » Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1,209 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Aleksander Pawlak supported this idea  · 
  13. 112 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
  14. 3,041 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    187 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →

    Quick update,

    We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.

    After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.

    We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.

    Thanks for your continued feedback,

    -Adam (Azure Billing Team)

    Aleksander Pawlak supported this idea  · 
  15. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Aleksander Pawlak shared this idea  · 

Feedback and Knowledge Base