Jan V.

My feedback

  1. 13 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Jan V. shared this idea  · 
  2. 158 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Storage » Managed Disk Storage  ·  Flag idea as inappropriate…  ·  Admin →
    Jan V. supported this idea  · 
  3. 49 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →

    The portal uses cross-origin resource sharing (CORS) to communicate to back-end services directly from the browser. We are working with our partner teams to get a full list of URLs required to manage your resources in the portal. Here are a few known URLs:

    *.azure.com
    *.azure.net
    *.windows.net
    *.azurecomcdn.net
    *.azureedge.net
    *.msecnd.net
    login.microsoftonline.com
    login.live.com

    Third-party services:

    *.sendgrid.com
    *.newrelic.com

    Please let us know if we missed any.

    Jan V. commented  · 

    Hi
    To whitelist, it would be helpful to have information on the URLs used by extensions or azure services (mapping URL to extension/service). In that way, at least we can document and know why they are opened in the first place. Above, grouping in domains preferred over IPs/subnet as well (which regularly change).

Feedback and Knowledge Base