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

Customer feedback | az network bastion rdp | auth-type has incomplete information #8391

Open
dbradish-microsoft opened this issue Jan 2, 2025 · 5 comments
Assignees
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Network - Bastion Network Service Attention This issue is responsible by Azure service team.

Comments

@dbradish-microsoft
Copy link
Contributor

dbradish-microsoft commented Jan 2, 2025

Describe the bug

This GitHub issue is being created by UUF https://aka.ms/UUFTriageApp?pageviewid=86e82778-95ee-3db8-8574-2d34168fb6f1 and resulting azDO #350886.


The customer is wanting to know the allowed values for the --auth-type parameter. This information is missing from the parameter description, and there is no example to help fill in the gap.

Request to engineering

1 - Please provide the allowed values for the authentication type for az network bastion rdp command
2 - Add an example that uses this parameter

Customer feedback

Repo:

azure-docs-cli

Title:
az network bastion | Microsoft Learn

Verbatim:
--auth-type

What parameters are there? documentation again incomplete!

Verbatim Id:
ce783d11-7db1-ef11-b8e8-00224802bfe1

Triaged By:
[email protected]

Live URL:
https://learn.microsoft.com/en-us/cli/azure/network/bastion

GitHub URL:
https://github.com/MicrosoftDocs/azure-docs-cli/blob/live/latest/docs-ref-autogen/network/bastion.yml

UUF Triage App Feedback URL:
https://aka.ms/UUFTriageApp?pageviewid=86e82778-95ee-3db8-8574-2d34168fb6f1

Related command

az network bastion rdp

Errors

.

Issue script & Debug output

.

Expected behavior

.

Environment Summary

Azure CLI 2.67.0

Additional context

No response

@dbradish-microsoft dbradish-microsoft added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 2, 2025
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 2, 2025

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. Network - Bastion labels Jan 2, 2025
Copy link
Contributor

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

Copy link
Contributor

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

@yonzhan yonzhan added bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 2, 2025
Copy link
Contributor

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

Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Network - Bastion Network Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants