RappstAir

My feedback

  1. 390 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » Bastion  ·  Flag idea as inappropriate…  ·  Admin →
    RappstAir supported this idea  · 
  2. 70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    RappstAir commented  · 

    How is the status of this improvement?

    "Each NIC attached to a VM must exist in the same location and subscription as the VM. Each NIC must be connected to a VNet that exists in the same Azure location and subscription as the NIC. You can change the subnet a VM is connected to after it's created, but you cannot change the VNet."

    => It would be great for billing purposes as well, if the NIC and VM can be located in different subscriptions than the VNET.

    RappstAir supported this idea  · 
  3. 736 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Azure Analysis Services  ·  Flag idea as inappropriate…  ·  Admin →
    RappstAir commented  · 

    How is the status. Customers are asking about MDX support in Azure PaaS!

    RappstAir supported this idea  · 
  4. 32 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Azure Active Directory » Azure AD Connect  ·  Flag idea as inappropriate…  ·  Admin →
    RappstAir commented  · 

    Any information about the release date?

    RappstAir supported this idea  · 
  5. 130 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  20 comments  ·  Azure Governance » Azure Policy  ·  Flag idea as inappropriate…  ·  Admin →
    RappstAir supported this idea  · 
    RappstAir commented  · 

    Complex naming conventions with RegEx would be great as our customers request it. The current functionality with "match" and "notMatch" is unfortunately not enough. To use "allOf" to apply multiple patterns makes the Azure naming policy more complex and difficult for administration.

Feedback and Knowledge Base