Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Compute] Add the hint to suggest users use the standard public IP when creating VM #15574

Closed
brianlehr opened this issue Jul 28, 2021 · 7 comments
Assignees
Labels
Compute - VM feature-request This issue requires a new behavior in the product in order be resolved. Service Attention This issue is responsible by Azure service team.

Comments

@brianlehr
Copy link
Member

Description

In the latest profile and the profiles that use the same api-version as latest profile, the default public IP used for VM creation will be expected to be changed from Basic to Standard in ~2-3 years. In order to avoid breaking change which has a big impact on users, we use the hint to guide users to use Standard public IP to create VM in the first stage.

Specific Feature Request

When user runs New-AzVM without specifying a -PublicIPAddressName AND -AllocationMethod Standard, we should add the message "It is recommended to use parameter "-AllocationMethod Standard" to create new VM with Standard public IP. Please note that it will become the default behavior for VM creation in the future.”

This is the equivalent of this request in CLI, which has already been implemented: Azure/azure-cli#18662.

@brianlehr brianlehr added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jul 28, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jul 28, 2021
@dingmeng-xue dingmeng-xue added Compute - VM Service Attention This issue is responsible by Azure service team. labels Jul 29, 2021
@ghost
Copy link

ghost commented Jul 29, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv.

Issue Details

Description

In the latest profile and the profiles that use the same api-version as latest profile, the default public IP used for VM creation will be expected to be changed from Basic to Standard in ~2-3 years. In order to avoid breaking change which has a big impact on users, we use the hint to guide users to use Standard public IP to create VM in the first stage.

Specific Feature Request

When user runs New-AzVM without specifying a -PublicIPAddressName AND -AllocationMethod Standard, we should add the message "It is recommended to use parameter "-AllocationMethod Standard" to create new VM with Standard public IP. Please note that it will become the default behavior for VM creation in the future.”

This is the equivalent of this request in CLI, which has already been implemented: Azure/azure-cli#18662.

Author: brianlehr
Assignees: -
Labels:

Compute - VM, Service Attention, feature-request

Milestone: -

@axayjo
Copy link

axayjo commented Aug 3, 2021

@avirishuv can you take a look at this?

@brianlehr
Copy link
Member Author

Hi team, any questions about this request? It has been implemented in CLI for a couple months already.

@jaylabell
Copy link

Working to update this issue

@brianlehr
Copy link
Member Author

Hello again, it's been quite a few months. @jaylabell - what is eta for this? it seems like a very straightforward and simple change, it's just adding text notification at time of VM creation.

@thisisanniefang
Copy link

@jaylabell Hi Jayla, any updates here? We are trying to move forward towards making Standard the default and need this as a prerequisite.

@jaylabell
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compute - VM feature-request This issue requires a new behavior in the product in order be resolved. Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

6 participants