-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Feature]: For "New-AzVM", please add a parameter which can disable NSG which allows 22/3389. #16890
Comments
Thank you for your feedback. This has been routed to the support team for assistance. |
1 similar comment
Thank you for your feedback. This has been routed to the support team for assistance. |
@kgfly this looks like a feature request so redirecting this to specific team to look into it. Thanks. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv. Issue DetailsDescription of the new featureAbout feature parity of CLI. "az vm create" supports a parameter for disabling NSG which allows 22/3389. https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest -> "--nsg-rule none" For "New-AzVM", please add a parameter which can disable NSG which allows 22/3389. Currently, people have to either
, which is not convenient. Thanks. Proposed implementation details (optional)No response
|
@avirishuv do you mind taking a look at this (Compute-VM label) |
Moving issues assigned to @jaylabell over to @Drewm3. |
Travis will look into this request. |
@kgfly Thanks for your feedback! We are working to implement this for New-AzVM. |
This is pending semester planning. |
Why is this still not fixed? It is incredibly frustrating to deploy VMs with powershell without an NSG. |
Description of the new feature
About feature parity of CLI.
"az vm create" supports a parameter for disabling NSG which allows 22/3389.
https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest ->
"--nsg-rule none"
For "New-AzVM", please add a parameter which can disable NSG which allows 22/3389.
Currently, people have to either
create another high priority NSG which block the port.
Or
Delete the NSG after VM creation,
, which is not convenient.
Thanks.
Proposed implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: